You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 22, 2024. It is now read-only.
Since threads are intended to be used as temporary channels and Revolt doesn't have an equivalent, I don't think there's much value im adding support to bridge to threads, especially because I'd have to change the way bridge configuration is stored, since threads are associated with a parent channel but have their own channel ID. If/when Revolt gets threads it would probably be possible to sync threads between both platforms though.
Of course, if you have a use case for bridged threads I'd be interested to hear it!
basically, threads are intended for temporary conversations, but i've often seen them appear like this: in a channel like #modding you have each user create a thread for each individual modding project. these threads can usually take weeks if not months of conversation since some projects are large-scale. this prevents having to make tens of channels for all the projects, and then needing to archive em when each is done.
i understand this is a huge undertaking though, and this is (while still somewhat common from what i've seen) not the most intended use case. so i'm not gonna be pushy or anything, just showing that there is a use case and interest for this feature
thank you for your time!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Steps to replicate
/bridge link
in a Revolt channel/bridge confirm
in a discord threadExpected behaviour
Thread is linked like a normal text channel.
Observed behaviour
The bridge is not set up.
The text was updated successfully, but these errors were encountered: