Conversation

Replying to and
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
Replying to and
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
Replying to and
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
Replying to and
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
Replying to and
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.
2
Replying to and
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
5
Replying to and
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
Replying to and
It has a persistent message history for the channel and I have to scroll through it manually clicking on each gore picture or racist comment and then pressing remove in the context menu, followed by waiting for the server delay and often having the action fail a few times.
1
Replying to and
So yeah, not very fun having to manually go through 100 messages spamming the n word and then still having 100 lines saying messages were deleted with the name + profile picture of the person who spammed there unable to be removed AFAICT. Really frustrated with this right now.
1
1