-
Notifications
You must be signed in to change notification settings - Fork 397
MSC4202: Reporting User Profiles #4202
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
base: main
Are you sure you want to change the base?
Conversation
a0f12c7
to
b5bdc5e
Compare
b5bdc5e
to
bedd16c
Compare
This MSC is dependent on #3843 to allow users to report inappropriate users (e.g. offensive MXID, or inappropriate user profile content) rather than a specific event. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementation requirements:
- Client
(as this MSC depends on #3843, a server implementation is only needed for that MSC and not this one)
- **Privacy**: Reporting an `m.room.member` event includes the profile information set by the user | ||
in that room. Servers SHOULD handle this data appropriately and respect user privacy. | ||
|
||
## Potential Issues |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One to add is that this might (as like with most moderation things on server level) have the issue that server and room rules may differ. A profile might be considered ok by the server admin, while it isn't ok for the room where the user is in. So this proposal only adds server level moderation but still no full room level moderation imho. It solves parts of the issues, but not all of them, imho.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed, do you know if there's an MSC for reporting events to room admins so I could perhaps add that as a dependency here too?
Rendered
Signed-off-by: Tom Foster tom@tcpip.uk
Known Implementations: