The matrix.org server eventually stopped federating with some of the openly, officially racist servers and took away matrix.org aliases named after a bunch of open source projects since they've made channels for a hundred projects and reserved aliases.
Conversation
Channels still exist and they still have the aliases across most servers. Users on matrix.org who joined those channels thinking they were the right one for the project (and perhaps assuming it was official) are still in those channels. Took a long time to get...
2
Replying to
I think with the way Matrix works, a channel (room) isn't really associated with a specific server. You can give them aliases on different servers. You can claim a whole bunch of aliases for a channel, so a channel can have many different identifiers across many servers.
1
If we wanted, we could grab #grapheneos on a bunch of different servers by making accounts there and adding a local alias... in fact it seems like random users in the channel can freely add local aliases on their servers including in abusive ways. A lot of it is messed up.
1
1
On matrix.org, there are bridged channels mapping to every channel on freenode, oftc, etc. and if you have op on the IRC side it gives you mod privileges on the Matrix side. A bridge bot owns the room and many moderation tools are not available to you in those rooms.
1
We decided to use this existing bridged room as our Matrix room so that the canonical room is officially the Freenode #grapheneos channel. However, this means we don't fully control the Matrix side. Have mods in it but can't do stuff like disabling anyone being able to invite.
1
We had the option of creating a Matrix room that we would actually own and setting up a bridge to the IRC channel, but the matrix.org bridged room would still exist. It'd get confusing where some Matrix users would be in our room with our bridge and some in that one.
1
So for example, since we have people acting as spies in the channel, if I set the Matrix room to invite only, they can just start chain inviting spammers into the channel. I cannot disable non-mod invites because the IRC service bot owns the bridged rooms for oftc, freenode, etc.
1
So I don't even have a way of temporarily not letting more people into the Matrix side of the channel. Also, for some reason these people aren't appearing on the IRC side (the bridge is not bridging them) so IRC moderators are unable to see it happening and ban them from it.
1
It's *supposed* to give the owners of the IRC channel control over it but it only has a concept of mapping IRC op to a semi-privileged Matrix moderator and has no concept of the channel owner. It doesn't know about NickServ/ChanServ or anything either. Just gives mod based on op.
So if I give a Matrix user +o temporarily on IRC, they get moderation privileges on the Matrix side equal to my own. If they leave the channel and rejoin, they won't have +o on IRC but they'll still be a mod on Matrix. The whole thing is just really janky and messed up.
1
4
5
Hard to explain all that's wrong with it. Not to mention that Matrix has insane lag / delays and it can make it really hard to talk on it especially when people are arguing since they often can't see each other's messages for 30 seconds to a minute which makes things a lot worse.
1
Show replies
I once proposed to the matrix people that they adjust their bridge to actually operate as a linked server in the IRC networks they want to bridge. that would have solved a lot of these issues, but they complained that it would be difficult to do so.
1