Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal for Rich Bridging #1410

Half-Shot opened this issue Jul 12, 2018 · 2 comments


Copy link

commented Jul 12, 2018


This comment has been minimized.

Copy link

commented Aug 2, 2018

We really need this. I'm currently staring at a log as thousands of Telegram users are invited by ChanServ into a room, which the Telegram bridge says "you can't do that" and then leaves. Instead, the IRC bridge could see that those users are bridged users and not bother inviting them, or the Telegram bridge could happily ignore the rooms - both of which reduce server load.


This comment has been minimized.

Copy link
Contributor Author

commented Aug 2, 2018

I'm considering splitting out the double bridging portion to it's own regular event, that then allows other ASes to interject and say "NO, STOP THAT". It's a little racey but better n nothing.

@richvdh richvdh removed the proposal-wip label Nov 7, 2018

@turt2live turt2live added T-Core and removed T-Core labels Dec 24, 2018

@anoadragon453 anoadragon453 removed the T-Core label Jan 4, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
4 participants
You can’t perform that action at this time.