Matrix moderation, Element
Here are some things that Element could have done years ago to mitigate the abuse issues, but didn't:
- Move invites to a queue that is not visible or attention-grabbing by default
- Homeserver-level support for subscribing to shared ACLs
- Protocol-level support for synchronizing ACLs across rooms in a space
- Track associations between media files and the messages they are referenced from, so that they can be automatically removed alongside their messages
- Automatically hide images from newly-joined users behind a spoiler tag
All of these are viable from a technical perspective, most of them were suggested years ago already, and this list is not exhaustive either.
Think about this next time you see Element talking about how much work they've been doing on safety and how there's just not many things left that they can do.
re: Matrix moderation, Element
@Ember It's not, nope. It's just a big bucket of media files keyed by ID and no association is stored (it *can't* even really be stored with the way the endpoints are currently designed). So the only automated removal option is time-based expiry...
Matrix moderation, Element
@joepie91@social.pixie.town I would like to see separate power levels for different types of m.room.messages as well.
re: Matrix moderation, Element
@joepie91 media isn't associated to the message that sent it??? what the hell, how even does that sort of a basic oversight get into a protocol/major implementation(s)