dgw

Why are we talking about generating our own IDs? https://ircv3.net/specs/extensions/message-ids.html

IDs depend on the `message-tags` capability, which I don't think Sopel requests.

And there's the message ID (`msgid` tag). As I thought, if Sopel asks for the right CAP, it'll get the IDs sent to it without kludging in its own ID-ish...

Dug a bit more into this. Unreal [checks](https://github.com/unrealircd/unrealircd/blob/a8c191b291ec635fef0a683c10d5b4dce4263fa0/src/modules/history_backend_mem.c#L307) if the client "requesting" history (scare quotes because there's no way for Sopel to say "don't send me history") supports `batch`, and...

Following up on this as someone asked about it on IRC today: On InspIRCd, usermode +B _can_ disable history playback for bots, but the relevant setting's default value ignores it,...

User mode `+N` only works on InspIRCd 3.9.0+ _and_ needs to be enabled by the network. It's a fine workaround for anyone using Sopel on a server that supports it,...

"4 minutes" is clearly server-dependent (testing this just now on a network that doesn't advertise the `sasl` CAP, it went to `ERROR :Closing Link: ww.xx.yy.zz (Registration timed out)` after only...

I think this is mitigated Enough™ by periodic WHO updates (see #1664) that we can leave it for 7.1.

ISUPPORT parameters are now available thanks to #1758. That was the minimum requirement for starting on this, so we're set for beginning early 7.1.

Sopel has requested `multi-prefix` support for about 5 years already. In fact, all three of those points should already work, as the `RPL_NAMREPLY` handler checks for all privilege prefixes (from...