You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some networks allow receiving historic conversation content. Such message dumps may include a (in)complete OTR transcript, from query tag to end-of-session. In case a client is aware that this concerns historic chat messages, we may want to advise skipping processing of these messages altogether - or special treatment.
For example, IRCv3's chat history extension describes how one could receive a batch that is a complete conversation. XMPP seems to have something similar, although I'm not fully aware of XMPP features.
Consider the following issues:
processing historic messages will result in failing OTR sessions, hence not desirable.
not processing messages at all, will result in OTR-encoded "message spam" in the client chat window.
The text was updated successfully, but these errors were encountered:
cobratbq
changed the title
Advise to skip processing chat history
Advice on processing chat history containing OTR transcript
Mar 9, 2019
Some networks allow receiving historic conversation content. Such message dumps may include a (in)complete OTR transcript, from query tag to end-of-session. In case a client is aware that this concerns historic chat messages, we may want to advise skipping processing of these messages altogether - or special treatment.
For example, IRCv3's chat history extension describes how one could receive a batch that is a complete conversation. XMPP seems to have something similar, although I'm not fully aware of XMPP features.
Consider the following issues:
The text was updated successfully, but these errors were encountered: