Conversation
tcpipuk
changed the title
tcpipuk
force-pushed
the
user-reporting
branch
from
a0f12c7 to
b5bdc5e
Compare
tcpipuk
force-pushed
the
user-reporting
branch
from
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. |
tulir
added
proposal
There was a problem hiding this comment.
Implementation requirements:
- Client
(as this MSC depends on #3843, a server implementation is only needed for that MSC and not this one)
tcpipuk
changed the title
| - **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.
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.
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?
4 participants
Rendered
Signed-off-by: Tom Foster tom@tcpip.uk
Known Implementations: