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

users actively reading messages should not be kicked for being idle #1194

Closed
thestinger opened this issue Nov 23, 2020 · 13 comments
Closed

users actively reading messages should not be kicked for being idle #1194

thestinger opened this issue Nov 23, 2020 · 13 comments
Labels
matrix.org-support Matrix.org specific problem possibly unrelated to the bridge

Comments

@thestinger
Copy link

Users that are logging into their accounts and reading the messages should not be kicked for idling. Matrix has read receipts and those provide a way to detect that users are actively lurking rather than joining the channel and not reading it. It may not currently be possible for the bridge to take advantage of this, in which case the necessary plumbing should be developed to make it possible. This is a serious usability issue and makes the IRC bridge implementation very hostile to users. For our channels, this regularly creates conflict and deters future participation in the community.

As a temporary workaround, the IRC bridge could notify users a week before they're kicked and give them a way to stop themselves from being kicked without publicly posting to the channel. At the moment, users are happily reading the channel and then suddenly get kicked with no warning. This will also make it much clearer to users why they got kicked. The kick message should also make it clearer that it was an automated action by the bridge, not the channel moderators.

A substantial portion of the users on the GrapheneOS channels (#grapheneos:matrix.org and #grapheneos-offtopic:matrix.org) primarily lurk in the channel. Some of these users will occasionally post to the channel despite lurking for long periods of time. Some of the channel regulars take breaks from active participation and then end up coming back to the channel later on. It's common for users to get upset after being kicked and they often think that the channel moderators were responsible. It's not clear to users that this was done automatically and that we don't have a way to disable it as the channel moderators.

We chose to make these bridged channels because the core community was originally on IRC, many people still prefer IRC and we didn't want to split the community based on preferred chat clients / protocols.

It's sad seeing bulk purges of users from the channel including people we know are still actively using it and interested in it. Some of them come back, but many don't. Due to a few serious technical issues like this one, we're considering moving away from Matrix by no longer listing it on our sites. We're looking into bridges with other platforms like Telegram to keep the channel more accessible than IRC. This issue prevents Matrix from serving that role.

@Half-Shot
Copy link
Contributor

This is actually implemented in #1152, it's just waiting to be deployed on matrix.org.

@Half-Shot Half-Shot added the matrix.org-support Matrix.org specific problem possibly unrelated to the bridge label Nov 23, 2020
@TimFW
Copy link

TimFW commented Dec 8, 2020

Is there any expected date for this to be deployed?

Sad its not getting more attention. Everythings done just spinning waiting to go live.............

@Half-Shot
Copy link
Contributor

We're working on it. This was deployed to OFTC as a test, but we've encountered some impl issues over at matrix-org/synapse#8903

@thestinger
Copy link
Author

Is the server load created by this going to block deploying it? It's sad seeing round after round of active users kicked from our channel for not sending messages. Maybe we need to make our own server and a new Matrix room where we control the bridge and can disable this.

@losuler
Copy link

losuler commented May 5, 2021

As a temporary workaround, the IRC bridge could notify users a week before they're kicked and give them a way to stop themselves from being kicked without publicly posting to the channel.

Could this be a feasible interim solution?

@Half-Shot
Copy link
Contributor

We've now deployed this as a test on libera.chat's bridge. So far it seems positive, but we'll need to see.

@pacien
Copy link

pacien commented Jul 19, 2021

Note that relying on the read markers as indicators of activity is probably
going to break after MSC2285 gets implemented. I expect most users coming
from the IRC world to be willing to disable read receipts the moment it becomes
possible.

@Half-Shot
Copy link
Contributor

I should have pointed out that it's been on libera for ages with no issues.

@Half-Shot
Copy link
Contributor

Note that relying on the read markers as indicators of activity is probably
going to break after MSC2285 gets implemented. I expect most users coming
from the IRC world to be willing to disable read receipts the moment it becomes
possible.

Yeah, it's unfortunate. It's basically impossible for us to figure out if a user is active if they disable all means of us checking. I hold out some hope that one day you can direct presence to the users you want to know about your presence, rather than broadcasting it to everyone. That would solve this problem nicely.

@thestinger
Copy link
Author

thestinger commented Nov 10, 2021

Could have the bot warn people 7 days before they get kicked from a network with a command to mark themselves as active on that network.

Note: going to unsubscrib from the thread since we're now using matterbridge and only have 40 users on the IRC side instead of 350+ since we strongly encouraged everyone to migrate to Matrix.

@Half-Shot
Copy link
Contributor

I'm going to close this as I don't think we are still missing any active users from our idle tracker.

@JigmeDatse
Copy link

I just got kicked from a Libera.chat bridged room unexpectedly. I had read up to a few days ago, and it was shortly after (like hours after) I think 3 messages for the first time in a while. This was the Tenacity room. To me and the admin, it seems to be "unexpected behaviour".

@Half-Shot
Copy link
Contributor

@JigmeDatse Do you have a rough idea when you read the room and your userID. We can investigate if the bridge is missing read events.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
matrix.org-support Matrix.org specific problem possibly unrelated to the bridge
Projects
None yet
Development

No branches or pull requests

6 participants