James Wheare

If you only apply this rule to new/draft CAPs, there's no need for a version bump to LS. If you want to retroactively use this on existing ones, then you...

At the moment we (irccloud) already prevent auto reconnect when certain strings are matched (kline, banned, etc) and it's an unexpected disconnect. But, these often get triggered by networks by...

Also from the looks of exec.py, it looks like there are on_finished events you may be able to hook into now.

The only concern I have is do we want to prohibit multi level replies. I would favour doing so, but if not then we might need another tag to indicate...

Unclear if you're talking about chathistory batch or chathistory request. But either way that's just normal behaviour. For a request, you get all messages you request, presumably since the last...

Just change it to: ```Servers MAY send `REDACT` commands in [`chathistory` batches](https://ircv3.net/specs/batches/chathistory) sent to clients on joining a channel``` (link in the footer if you wish) I believe the original...

Changes look good. No need to force push updates, makes it a bit harder to review. I squash commits on merge anyway.

Just specifying an ISUPPORT command that can work pre-reg works for me. Regarding batch, I feel like this was already discussed, but what use case does batch enable? My implementation...

Ok so maybe define the ISUPPORT command to require use of a batch if the cap is enabled? But leave the existing automatic isupport sent post reg unbatched. Would that...

Fine to merge this as is, but would the non draft cap name be more self explanatory as prereg-isupport? The format is not being extended by this afaict.