Advanced administration features for rooms - Githubissues

matrix-org / matrix-spec

The Matrix protocol specification

Apache License 2.0

193 stars 96 forks source link

Advanced administration features for rooms #316

Open homebeach opened 6 years ago

homebeach commented 6 years ago

When creating a room admins would be able to:

Set answerable questions for users who request to join
Limit how many messages users can send in a row
Limit how many stickers or media files users can send in a row or within defined period of time
Ban sending of certain media files or all the media files
Create customized right sets for people. Right sets could be saved in some kind of right set pack like sticker pack. There could be for example type 1 users: are able to do everything and have admin rights, type 2 users: can send everything but no admin rights, type 3 users: can only send text messages.

t3chguy commented 6 years ago

5 is already possible with how the permissions system works.

t3chguy commented 6 years ago

points 2, 3, 4 are not compatible with E2EE

homebeach commented 6 years ago

I would say that there is plenty of demand for 2,3 and 4 to prevent spamming in public rooms. One of the problems of Telegram in bigger chat groups is sticker spam and there are no efficient tools to limit it.

t3chguy commented 6 years ago

2,3,4 would require changes to the s-s federation consensus protocol also so are major changes

homebeach commented 6 years ago

Also if folder sharing is going to be implemented administrators would be able to set limit how much data people need to share to enter the room.

t3chguy commented 6 years ago

I feel like

how much data people need to share to enter the room.

is infeasible. What's to stop me running a client which claims I'm willing to share 20TB of data, but when someone asks for it I pretend to be unavailable?

homebeach commented 6 years ago

Admins can check what people share by investigating the folder that they share. They can try to download some files from people and check if their size is the claimed size.

t3chguy commented 6 years ago

So at that point there is no point it being part of the spec as if they want to be sure they have to manually check it

homebeach commented 6 years ago

But there could be some kind of check that if client claims to share x amount of data, it needs to have folder actually shared.

t3chguy commented 6 years ago

Right but that check is technically impossible, I could share 20TB of utter crap, like Lorem Ipsum or RNG images or whatever

turt2live commented 6 years ago

A lot of this is supported by other parts of the API, or by particular homeservers. For instance, if you're concerned about spam then your homeserver (and therefore your users) can be protected by an anti-spam solution - a function of synapse you can plug in yourself.

As for custom sticker packs for particular users, that'd be a role for the integrations manager. Although it isn't a first class citizen yet (#1286), it would be the thing that would manage that sort of stuff.

If this is asking for spam control at the federation level, then that's a whole other thing (which is technically possible, but enforcement would be difficult).