matrix-appservice-twitter
matrix-appservice-twitter copied to clipboard
Limiting # of ghost users.
Busy rooms could quickly stack up members which might cause clients some problems after that get's large. #wtf is a good example of why you need to be careful.
A few methods we could try:
- Just remove people who haven't tweeted after X time.
- As above, but also have a threshold to reach first.
Some clients (whether correctly or not) are struggling as is with the IRC bridge due to the number of member events, this would be useful to lighten the load.
The issue referenced above pushes some of the responsibility to the bridge to make stale users leave. This should be doable by doing a DB request for last message sent into room_id
for each twitter user.