search

matrix-org / matrix-spec

The Matrix protocol specification
Apache License 2.0
188 stars 94 forks source link

Ability to ACL based on event type (SPEC-227) #100

Open matrixbot opened 9 years ago

matrixbot commented 9 years ago

Submitted by @​matthew:matrix.org We already have scenarios where we want to give particular users or groups of users permission to send some types of events but not others... or perhaps be allowed to read some types of events but not others. We also need a way to somehow define default permissions for rooms so that users can't create new rooms without these restrictions - the use case for this is that there may be a AS subscribing to said new rooms, which may start picking up events that users inject in virgin rooms

(Imported from https://matrix.org/jira/browse/SPEC-227)

matrixbot commented 9 years ago

Links exported from Jira:

relates to https://github.com/matrix-org/matrix-doc/issues/543

matrixbot commented 9 years ago

By @​matthew:matrix.org: Another way of doing this might be to enforce filters on clients at a per-HS level. However, this breaks badly in the face of federation. Mind you, so do default permissions on rooms (unless they're applied by a chanserv-style bot... ugh...)

-- NEB (Bot)