matrix-org / matrix-org/matrix-spec
Parental control
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
We should define a way to define some access controls in the protocol so that inappropriate rooms and content cannot be viewed.
The public room directory(`/publicRooms`) could be filtered and `/join` could check that conditions are right before joining a room.
I have no idea how to implement that in the protocol but this will allow to create safe matrix clients for <17+.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue identifies the protocol entry points /publicRooms and /join, but no repository files or tests. Start by reading how those endpoints are specified and determine the access-control conditions needed for filtering rooms and checking joins; done means the protocol defines a workable approach for safe clients.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100