Simon Ser

One value-add from this spec is when a client needs to figure out on JOIN whether a user is an operator or not. Right now the only way is to...

Ref https://bugs.unrealircd.org/view.php?id=5991 for the new (inconsistent) extban names.

@progval Would this be enough to address your concern? "Servers MUST support matching exact account names. Servers MAY support matching account masks and other server-specific extensions." I don't think we...

> I'd rather we did. Unreal 6 will transform short extbans to long extbans, so clients need to know the long form in order to display it. Hm. This is...

> It would also be useful to have this supported by a server implementation that currently buffers history for autoreplay on channel join: requesting the chathistory cap would suppress the...

IMHO it makes sense to add the prefix, it makes it clearer that the cap belongs to chathistory. Maybe we'll have another spec in the future where "event playback" could...

gamja already uses `CHATHISTORY TARGETS` instead of requesting history on JOIN: https://git.sr.ht/~emersion/gamja/commit/91208a6d47d4ca5d60cad21a41018763585a2209

Ah, but if you JOIN a channel then switch to its tab, gamja will try to request history for it to populate the scrollback. `CHATHISTORY TARGETS` won't help here.

> deal gracefully with any error conditions Right. But I wonder what "deal gracefully" means with the existing spec. `INVALID_TARGET` can be a "real" error as well as a "history...

Something else that came up again is: how should clients figure out that they've reached the end of the chat history (ie, there are no more messages to fetch)? Some...