-
Notifications
You must be signed in to change notification settings - Fork 399
MSC4205: Hashed moderation policy entities #4205
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
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 sending hashes
- Client using hashes
``` | ||
|
||
In this example, when a moderation tool encounters a new user, or a | ||
new policy, the tool will calculate the base64 encoded sha256 |
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.
Many places in matrix use url-safe and/or unpadded base64, so if this is standard, it should probably be mentioned explicitly
Currently the content schema for `m.policy.rule.user` requires the | ||
`entity` field. In order for the `entity` field to be omitted when a | ||
hash has been provided, the entity field will have to become optional. |
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.
I think these events should have a distinct event type. Otherwise parsing the event is dependent on the recommendation, which both excludes ban recommendations from being hashed as well as makes parsing of events harder and technically is a backwards incompatible change. Something like m.hashed_policy.rule.user
or similar could work for example.
Rendered
Implementations:
org.matrix.msc4204.takedown
recommendation in Synapse the-draupnir-project/Draupnir#761Signed-off-by: Gnuxie [email protected]