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
Currently, there is no way to automatically create a portal room in a guild's space on Matrix on-demand, the closest thing to that is setting the bridging mode to on-message-create and sending a message.
Proposal
Add a create-portal command that takes a channel ID as an argument and creates the portal as if the bridging mode was on-message-create and a message has been sent. This would also be a good place to specify a one-off backfill request for that room only, though that would be a separate issue.
Usecase
A user joins a guild on Discord with a lot of channels, but they only want a few of those bridged to Matrix. If they bridged all rooms, they'd have to spend extra time deleting unwanted rooms and waste server resources. If they bridged rooms when new messages came, they'd have to send a message in every channel they'd want to bridge (keep in mind that a user cannot sometimes speak in a channel).
Considerations
A user could create the room themselves, invite the bridge bot to it and set it as the portal room for a specific channel, but that would be a longer process than executing one command and could lead to inconsistencies across different rooms and mildly annoy people like me.
Notes
I am starting to look at the codebase since I use this bridge daily, but it will take some time for me to understand it since I mainly write Rust code.
The text was updated successfully, but these errors were encountered:
Problem
Currently, there is no way to automatically create a portal room in a guild's space on Matrix on-demand, the closest thing to that is setting the bridging mode to
on-message-create
and sending a message.Proposal
Add a
create-portal
command that takes a channel ID as an argument and creates the portal as if the bridging mode wason-message-create
and a message has been sent. This would also be a good place to specify a one-off backfill request for that room only, though that would be a separate issue.Usecase
A user joins a guild on Discord with a lot of channels, but they only want a few of those bridged to Matrix. If they bridged all rooms, they'd have to spend extra time deleting unwanted rooms and waste server resources. If they bridged rooms when new messages came, they'd have to send a message in every channel they'd want to bridge (keep in mind that a user cannot sometimes speak in a channel).
Considerations
A user could create the room themselves, invite the bridge bot to it and set it as the portal room for a specific channel, but that would be a longer process than executing one command and could lead to inconsistencies across different rooms and mildly annoy people like me.
Notes
I am starting to look at the codebase since I use this bridge daily, but it will take some time for me to understand it since I mainly write Rust code.
The text was updated successfully, but these errors were encountered: