Provide a way to stop double bridging for a given room?

matrix-org / issues-bridging

Issue tracker for work being done on Matrix bridges for New Vector. Better than a google doc.

0 stars 1 forks source link

Provide a way to stop double bridging for a given room? #1

Closed Half-Shot closed 5 years ago

Half-Shot commented 6 years ago

Spec proposal: https://docs.google.com/document/d/1uBxekDnl9WBPWA989W1_QeOWA560TZI27g-Xju9Uk3w/edit?usp=sharing

Half-Shot commented 6 years ago

Need to decide the rules (if any) for double bridging (size of rooms?):

Espernet and Snoonet do not want anyone to ever double bridge into their network. Never add more than 100 users in a plumbing operation at a time (and if Travis doesn’t like that due to netsechacks or whoever, then we tackle it later by somehow identifying the source users by protocol and enforce it on our end rather than expecting him to play nice)

Half-Shot commented 6 years ago

Need to make damn sure that NickServs and similar don’t get stuck in a wooting loop (currently fixed by shutting down their DM rooms when it happens (bleurgh))

https://github.com/matrix-org/matrix-appservice-irc/pull/669

This PR isn’t quite the right thing in that we aren’t using state events, however we are checking against userids and rejecting provisioning requests based on those.

Awaiting Travis’s blessing, who is otherwise occupied.

Half-Shot commented 5 years ago

This got done, like, ages ago. Closing