matrix-org / matrix-org/matrix-spec
Controlled accounts
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
Hi,
I've been looking for a way for my kid to communicate with their classmates/friends in a responsible way (both privacy and security) but my pursuit ended with the sad conclusion that there currently is no such thing.
I'm not going to introduce my kids to the pests like FB and others. Or rather, I would at least like to keep them away from those platforms for as long as I can since I realize that the social pressure to use them will only grow as kids age.
So before going into much more detail: this idea is targeting a set of features to support communication for children _younger_ than 13 years old. This is a very sensitive subject so if the age target is out of the question due to law restrictions or whatnot, feel free to say so and there's no need to continue reading my ramblings.
So the idea is to create a walled garden for younger children to freely communicate without their parents having to actively setup a communication line using the currently existing platforms (which are all targeted towards adults or >13y) each time that the kid wants to talk (chat/video call/doodle/whatever) with one or more friends, classmates, family members, ...
Child accounts should be restricted in many ways:
- must be created by an existing account (parent account) and cannot be created on their own.
- multiple accounts can be assigned as parent accounts, but each parent account should be notified about other parent account actions concerning the child account.
- all child account communication should be end-to-end encrypted (somewhat, see following point)
- ~~**(controversial)** all parent accounts ~~should~~ (may) be able to access end-to-end encrypted communication (this might be a bit tricky because if all parent accounts are automatically joined in every room, the children will get the feeling of being continuously watched which is not what I want to achieve)~~
- all child account actions are constrained to non-public spaces. (not sure if that's a thing, I should read up on the current spaces spec)
- can't join spaces without parental approval.
- can't accept invites without parental approval (unless specifically allowed in a Space).
- can't join rooms without parental approval (unless specifically allowed in a Space).
There are probably other things that I can't come up with right now, so I might add some later on.
This featureset could also be used to provide safe spaces for elementary schools (class rooms, playground rooms, club rooms), sports clubs and other organizations revolving about children where you want your children to communicate with their peers without fearing harassment by external parties.
Contributor guide
Research direction
Start by reviewing the current Spaces specification, as the issue specifically questions whether its access rules support this proposal. Read the discussion for decisions about child accounts, parental approval, and encryption. Done would require a defined, legally viable feature scope and agreed behavior for account creation, invitations, rooms, and spaces.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100