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

State events from blocked users should not be shown to clients #2025

Open
everypizza1 opened this issue Dec 5, 2024 · 3 comments
Open

State events from blocked users should not be shown to clients #2025

everypizza1 opened this issue Dec 5, 2024 · 3 comments
Labels
improvement An idea/future MSC for the spec

Comments

@everypizza1
Copy link

Suggestion
In the client-server API, this is said:

Servers must still send state events sent by ignored users to clients.

Ignoring a user should imply that you won't see anything from said user, including joins, leaves, display name changes, avatar changes, etc.

@everypizza1 everypizza1 added the improvement An idea/future MSC for the spec label Dec 5, 2024
@KitsuneRal
Copy link
Member

This is problematic in case the user gets un-ignored at some later point. If state events are not sent, I as the ignoring/un-ignoring side have no idea whether that user is gone, if their display name is current etc. Clients are expected to hide all events from ignored users, but they have to keep track of what is happening to those users.

@everypizza1
Copy link
Author

Clients are expected to hide all events from ignored users, but they have to keep track of what is happening to those users.

I haven't seen this in the spec at all, and multiple clients I've tried (gomuks, fluffychat, even element x) don't hide state events from blocked users. I also wasn't able to block users at all until conduwuit implemented it server-side in any of those clients.

@clokep
Copy link
Member

clokep commented Dec 9, 2024

but they have to keep track of what is happening to those users.

An option could be to always redact the state events of blocked users? I think that would allow the "room state" to maintain intact while blocking potentially abusive content from them. This would work well for joins, topics, etc.

This probably breaks down with some events though (e.g. power levels).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement An idea/future MSC for the spec
Projects
None yet
Development

No branches or pull requests

3 participants