Upcoming IRCv3 extension: https://github.com/ircv3/ircv3-specifications/pull/393
msgidcriteria (depends on #72)
It could be used by downstream clients to request history from the bouncer and by the bouncer to request history from the upstream servers (eiither when relaying clients' requests or when the bouncer has had downtime).
Though implementing CHATHISTORY is a lot of work, and it requires support for
batch. For the moment, no known software has support for that command.
For the moment, I suggest only implementing the
chathistorybatch type, already defined by IRCv3: https://ircv3.net/specs/extensions/batch/chathistory-3.3. It would allow clients to properly display the history when connecting. With
server-time, I think you can have pretty good UX already.
chathistorybatch type is now implemented. Keeping this issue open for CHATHISTORY command support.
Though implementing CHATHISTORY is a lot of work, and it requires support for message-tags, server-time and batch. For the moment, no known software has support for that command.
Oragono supports it now. testnet.oragono.io can be used to test upstream CHATHISTORY support.
Implemented so far: support for messages like
CHATHISTORY BEFORE nickOR#channel timestamp=... 42
Still to do:
*criteria (explanation in #70, seems to be the hardest item in this list)