The latest news on this are:
https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches/27103

---
 ops/availability.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/ops/availability.md b/ops/availability.md
index 324df99927a2..492bffef1833 100644
--- a/ops/availability.md
+++ b/ops/availability.md
@@ -66,3 +66,17 @@ server from the mail host to the lists host (duh), and then just set up multiple
 MX records. Zero-downtime migrations can be accomplished by removing an MX
 record, letting the mail flush, and then doing whatever maintenance is
 necessary.
+
+# IRC bouncer
[message trimmed]

---
 chat.sr.ht/ircops.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/chat.sr.ht/ircops.md b/chat.sr.ht/ircops.md
index a04578570dfc..a4736ed2f918 100644
--- a/chat.sr.ht/ircops.md
+++ b/chat.sr.ht/ircops.md
@@ -4,7 +4,7 @@ chat.sr.ht is a hosted IRC bouncer which provides service to sourcehut users. It
 also provides a pass-through service which essentially acts like a webchat for
 anonymous users.
 
-We use the `173.195.146.128/25` and `2604:BF00:710::/64` subnets for bouncer
+We use the `173.195.146.128/25` and `2604:BF00:561:2000::/56` subnets for bouncer
[message trimmed]

Looks good to me!

Can you send a patch?

It definitely should.

gamja will keep track of received/seen messages in localStorage. Make sure your
web browser is configured not to nuke localStorage when closed.

Until recently, senpai didn't fetch history correctly on launch. There are
still some rough edges but it should work now. Make sure you're using the
latest senpai commit. Ref [1] and [2].

soju will send the backlog to clients which don't support the chathistory IRC
extension, like WeeChat or Revolution IRC. Make sure to add a "@<client>"
suffix to your username on these clients.

[1]: https://git.sr.ht/~taiite/senpai/commit/6014ba12270933c74018f2914713ec6fb2ed4a77

For future reference: this is fixed with a senpai patch [1].

[1]: https://lists.sr.ht/~taiite/public-inbox/patches/27015

Ah, missed the backticks. Sorry for the noise!

This is broken by design, to show that Markdown-style links aren't welcome
when writing messages on IRC.

Some servers might adjust their sasl cap at runtime, e.g.

    CAP NEW sasl=PLAIN,EXTERNAL
    […]
    CAP NEW sasl=PLAIN

In this case, we don't really want to `CAP REQ sasl` again, because
this will make us re-authenticate a second time.

Avoid requesting caps which have already been ACKed.
---
 irc/session.go | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
[message trimmed]