matrix-appservice-twitter
matrix-appservice-twitter copied to clipboard
Popular hastags can cause the bridge to crumble
There doesn't seem to be a reported issue for this already.
When people join popular rooms the bridge immediately falls victim to not being able to process tweets from other users. Instead of a global queue, it may make more sense to have a per-room queue. That would cause individual rooms to fall behind, but not affect everyone else using the bridge.
Another solution would be to outright drop messages over a certain frequency. A quick message to the room (pinned event?) to say that the room is really popular could help alleviate any concern. Ideally, this would mean that the room could be rate limited to 10 tweets/second (or whatever) to prevent larger issues.