James Wheare

The rationale for changing the events is that the original one doesn’t match the base name. It’s not chat-playback. draft stage means we can change stuff to be better before...

There was a small discussion on this in the draft PR: Starts here https://github.com/ircv3/ircv3-specifications/pull/393#issuecomment-721265459 > Is there scope for a way to indicate that you've reached the end of history...

How so? It's the same thing, just per message instead of persistent.

Message sent on the oratestnet side viewed from the freenode side in IRCCloud (no display-name tag)  Message sent on the freenode side viewed from the oratestnet side in IRCCloud...

Here's a further implementation example that strips the prefix, renders the actual nick specially when the draft/bot tag is present, and uses the display name to choose the nick colour:...

I'm going to try reworking the fallback stuff to be a bit more normative, with SHOULDs and mention things like formatting and zwsp anti-highlight bytes. @syzop I'm not against some...

If we disallow control codes, do we disallow the unicode U+007F to U+009F range as well? https://www.fileformat.info/info/unicode/category/Cc/list.htm (reminder, tag values are utf8) For reference, these are various byte lengths. All...

As this is a client tag spec, an 005 token would not be appropriate. We can specify a limit but it would be up to clients to police it at...

Thanks for the comments. Fully agree about the scope of this spec, it's by design and isn't trying to solve all bridging issues.

We could also note that 908 can be used to advertise a change of mechlist