Open gabrc52 opened 1 year ago
Also bridges
Write and submit a proposal: https://github.com/matrix-org/matrix-spec-proposals
Maybe even roles with custom events that could eventually be upstreamed. Matrix isn’t quite ready to be a Discord replacement because the paradigm of channels into categories with access control using certain roles isn’t as straightforward to implement — or maybe it’s a matter of making the equivalent of a role bot. As far as I’ve seen there’s only roles like admin, moderator, etc but not specific roles like on Discord. Plus Discord roles show up on your profile too.
Ohhh intresting, because spaces are room sthemselves and consist of rooms, they can nest!
So if you make a space and you make all the subspaces mandatory, they could act as categories. Maybe a new room type for Discord-like server could be created. This makes it easier to hack clients to do that.
if room.is_space and all(subroom.is_space and all(not r.is_space for r in subroom) for subroom in room.subrooms):
# room can act as Discord-like server
Note that this is pseudocode lol.
Discord is used a lot at MIT, and if people are to use Matrix instead of Discord for the same use cases, we'd need Discord stuff on Matrix. This is one of the hardest issues, but would be useful for the overall Matrix community, because it would require extending the Matrix spec itself (make an MSC) and/or Matrix clients themselves.
strikethrough. This is already supported in Matrix itself, but is hard to do on Element. It works perfectly on Cinny which is one of the reasons I'm considering serving Cinny instead of Element, apart from the overall neatness of the app. This could also be done server-side for non-encrypted channels.Example of how permissions compare: