[WIP] MSC4152: Room labeling and filtering #4152
Conversation
turt2live
added
proposal
| The `m.room.labels` event is used to share labels on a room between servers, and is set by the room's | ||
| participants (typically moderators and admins only). Each entry under `labels` is bound by the | ||
| [Common Namespaced Identifier Grammar](https://spec.matrix.org/v1.10/appendices/#common-namespaced-identifier-grammar). |
There was a problem hiding this comment.
So, what is the intention behind using namespaced labels?
I can assume that it is to make labels more consistent for client developers and consumers of the data that are going to build fancy room directories, maybe. But it doesn't really help those who will want to freetext the labels and write whatever they like, people are likely going to do that regardless (and may or may not namespace them, which will cause more fragmentation).
And yes, freetext labels can also be used to advertise abusive content, but that's likely going to happen even with namespaced labels unless the main clients gatekeep the available labels somehow (and even then, the gatekeeping can probably be circumvented just by using element web's /devtools). Though that could be considered good enough?
Servers could also getekeep the supported labels for their own room directory, I guess.
There was a problem hiding this comment.
Using identifiers allows for translations on the label values, and a more consistent experience for client developers. The IDs themselves should never be shown to the user verbatim.
This MSC is also a work in progress, and this is an undefined area.
Rendered
In line with matrix-org/matrix-spec#1700, the following disclosure applies:
I am Director of Standards Development at The Matrix.org Foundation C.I.C., Matrix Spec Core Team (SCT) member, employed by Element, and operate the t2bot.io service. This proposal is written and published as a Trust & Safety team member allocated in full to the Foundation.