https://whynothugo.nl/tags/irc/Recent content in Irc on WhyNotHugoHugo -- gohugo.ioenWed, 13 Mar 2024 17:48:37 +0100https://whynothugo.nl/journal/2024/01/12/setting-up-an-irc-bouncer-soju-on-openbsd/Fri, 12 Jan 2024 16:13:26 +0100https://whynothugo.nl/journal/2024/01/12/setting-up-an-irc-bouncer-soju-on-openbsd/Given the outage at sourcehut right now1, I need an alternative bouncer to use IRC without leaving a client running 24/7. Running my own seems like a simple enough choice. I opted to run soju (mirror) on my personal server running OpenBSD. soju is what powers chat.sr.ht. It is well tested, I know it fits my needs, and has support for connecting to multiple networks. Its bouncer/network support integrates nicely with senpai, a modern irc terminal client.https://whynothugo.nl/journal/2023/07/05/senpai-a-modern-irc-terminal-client/Wed, 05 Jul 2023 00:00:00 +0000https://whynothugo.nl/journal/2023/07/05/senpai-a-modern-irc-terminal-client/I’ve been writing some IRC-related experiments using a bouncer lately. I don’t have anything useful yet. My code so far connects to a bouncer, enumerates bouncer networks, opens a second connection to the bouncer (you need an additional connection per upstream network), and then crashes. While trying to find some details on the AUTHENTICATE command using SASL (do I know what I’m doing at this point?), I ended up falling down a rabbit hole where I came across a particular IRC client I that had somehow slipped under my radar:https://whynothugo.nl/journal/2023/01/20/setting-up-irc-redirects/Fri, 20 Jan 2023 11:39:00 +0100https://whynothugo.nl/journal/2023/01/20/setting-up-irc-redirects/Updated 2023-10-23: The +i mode was added. See below for details. A few weeks ago I wanted to set up a few redirects on IRC. Mainly, I wanted to redirect #vdirsyncer, #khal and #todoman to the #pimutils channel (given that pimutils is the umbrella project for both of these). These are the commands I had to run after authenticating: /msg ChanServ register #todoman /msg ChanServ set #todoman mlock +if #pimutils /msg ChanServ set #todoman guard on /msg ChanServ register #vdirsyncer /msg ChanServ set #vdirsyncer mlock +if #pimutils /msg ChanServ set #vdirsyncer guard on /msg ChanServ register #khal /msg ChanServ set #khal mlock +if #pimutils /msg ChanServ set #khal guard on Reference[permalink] mlock locks the mode to the specified one guard will retain the channel even if everyone leaves.