I realize a lot of people will not feel that way, for nostalgic reasons or because they want to make IRCv3 into their vision of what should be the future of chatting on the Internet and other reasons I'm sure. What do you think about the co-existence of IRC & Matrix?
Conversation
Replying to
Matrix requires you use a bot to ban all users on the kiwifarms matrix server. It does this by kickbanning them as they join, one at a time. Serious downgrade over IRC tbh.
2
3
I think you're getting two things mixed up, as that's not necessary; you can just add the entire kiwifarms server to the ACL and that's it. Maybe you're thinking of applying bans *across rooms*? That's what a bot like Mjolnir is typically used for.
1
1
oh i was under the impression that you can’t blanket ban an entire homeserver from joining your rooms. but i’m not convinced that the DAG design is actually safe in that regard anyway, an evil node can just ignore the ACL and forward on what it sees, no?
1
2
In a literal sense, sure. But other servers will still ignore things originating from the ACLed homeserver, regardless of who it comes from; and in terms of disclosing room contents to the ACLed server, that's no different than with any protocol where a malicious server can log.
2
my desire though is to make it so that homeserver is 100% not possible to read a channel. in IRC that can be done, since it’s centralized.
2
1
ACLs do prevent it from reading it from any servers respecting the ACLs. You would need to fork it to change it. It would be straightforward enough to identify other servers not respecting the ACLs and ban those too.
You can also make an allow list with the ACLs instead of deny.
1
This is a no-op ACL state event (send as m.room.server_acl):
{
"allow": [
"*"
],
"allow_ip_literals": true,
"deny": [
]
}
You would start by setting allow_ip_literals to false to only allow servers with actual domain names for them.
1
If you didn't include * in the allow list, it would brick the room. It checks deny, then allow, and then falls back to the default of deny everything. There's nothing stopping you from making a room and setting a server ACL only permitting servers you want to allow to federate.
1
So, basically, if you want to try it, make a public room with Element, open up developer tools and send that as a custom event with the m.room.server_acl type and toggle it from event to state event. Can replace * with an allow list, or use a deny list instead.
1
Main issue with this feature is that there isn't a client UI. It's so easy to thoroughly screw up the room with it and really needs a UI stopping you from blocking the server you send it from. UI preventing that would prevent bricking rooms unless you remove your own admin there.