Make irc server better

[m@…]

#39 is *almost* done.

So let's make it better

Some tasks:

• [ ] expose a (non-signinable) web frontend at irc.devhack.net. kiwiirc looks too modern these days. maybe irc-cgi or qwebirc. auto-join to uhh. #hello? #lobby?
• [ ] Expose it to the outside internet safely. port 6667 & 6697 would be nice. (do we need unencrypted sockets to the outside? maybe would be nice). irc.devhack.net would be nice too. Definitely need rate limiting or some sort of admin control
• [ ] ensure ip addresses from the outside make their way to the irc daemon. PROXY protocol?
• [ ] administer specific channels so that only logged in users can join. like #General. Maybe even not accessible from the outside no matter what.
• [ ] set up services. probably anope
• [ ] kubernetes operator to spool up redundant federating servers (with auto-provisioning credentials?)
• [ ] fix / create a new irc bridge that interfaces with the irc daemons as a federating server
• [ ] provision some non-on-site federated servers to use in case our network shits the bed
• [ ] connect to connection museum's irc servers?
• [ ] ldap login (to finn's chagrin)

[m@…]

Set up / reprogram the matrix bridge bot *to not message users constantly*

[m@…]

A problem we're running in to is bouncer-less clients. we're probably going to have to create a class of IRC channel restrictions that are basically "if you're connecting from our known bouncer, have a specific class of user agents specifying you're connecting from a bouncher (idk if this is possible), or have contacted an admin to confirm you've set up a bouncer, then you get perms to join this channel". Maybe only general is a channel with this restriction. idk

see also: ​https://github.com/matrix-org/matrix-static/issues/101

The irc bridge can also be configured to persist users after they leave but that's ehhh

see also: ​https://github.com/matrix-org/matrix-appservice-irc/issues/443

[cursedsilicon@…]

Would there be interest in linking/federating with the Dial-Up ISP once that is operational? Likely similar to the Connections Museum

It may be worth joining the retro channel on matrix to hash out details for it also

[cursedsilicon@…]

Briefly discussed the idea further in the #infrastructure channel

Splitpixl with connections museum is vaguely interested in 'federating' with the retro ISP

Connecting all three IRC servers to one single "bridge" would allow them to federate but also operate independently in case of downtime

I can't embed images into Trac so here's an example diagram for the visual folks

​https://cursedsilicon.net/IRC.png

[m@…]

Some other silly things the bridge does:

• add every user in a bridged matrix room to a private DM with the bot to tell them status of the bridge & their irc nick or whatever
• doesn't change irc nick to match matrix nick.