Skip to content

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

tcpipuk
Copy link
Contributor

@tcpipuk tcpipuk commented Sep 26, 2024

Rendered

Signed-off-by: Tom Foster tom@tcpip.uk


Known Implementations:

  • Clients:
  • Servers:

@tcpipuk tcpipuk changed the title Reporting User Profiles over Federation MSC4202: Reporting User Profiles over Federation Sep 26, 2024
@tcpipuk
Copy link
Contributor Author

tcpipuk commented Sep 26, 2024

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.

@tulir tulir added proposal A matrix spec change proposal s2s Server-to-Server API (federation) kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Sep 26, 2024
Copy link
Member

@tulir tulir Sep 26, 2024

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)

@tcpipuk tcpipuk changed the title MSC4202: Reporting User Profiles over Federation MSC4202: Reporting User Profiles Sep 30, 2024
- **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
Copy link
Contributor

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.

Copy link
Contributor Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal s2s Server-to-Server API (federation)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants