Skip to content

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

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

Conversation

Gnuxie
Copy link
Contributor

@Gnuxie Gnuxie commented Oct 2, 2024

@Gnuxie Gnuxie changed the title MSC0000 Hashed moderation policy entities MSC0000: Hashed moderation policy entities Oct 2, 2024
@Gnuxie Gnuxie changed the title MSC0000: Hashed moderation policy entities MSC4205: Hashed moderation policy entities Oct 2, 2024
@Gnuxie Gnuxie marked this pull request as ready for review October 2, 2024 13:49
@turt2live turt2live added proposal A matrix spec change proposal client-server Client-Server API 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 Oct 2, 2024
Copy link
Member

@turt2live turt2live Oct 2, 2024

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
Copy link
Member

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

@tulir tulir removed the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Mar 13, 2025
Comment on lines +56 to +58
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.
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client-server Client-Server API hacktoberfest-accepted kind:feature MSC for not-core and not-maintenance stuff proposal A matrix spec change proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants