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
{{ message }}
This repository has been archived by the owner on Feb 10, 2024. It is now read-only.
Sorry for having necromanced #1430 first; I didn't remember I had already mentioned it in #1797.
I still chat on FreeNode where multiple encodings are used. While I like the idea of supporting a fallback encoding, it has the major problem that we'd need to know the possible encodings in advance.
Could someone add an option to log raw original server transmissions, so I can try and detect the appropriate encoding retrospectively?
That would help a lot in recovering conversations after they turned out to have been interesting.
The text was updated successfully, but these errors were encountered:
I couldn't find another issue about logging the raw transmissions. All that I found were about trying to decode the transmissions in better ways inside hexchat, for varying definitions of "better". #1430 is about plugins, which might be one way of implementing the logging.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sorry for having necromanced #1430 first; I didn't remember I had already mentioned it in #1797.
I still chat on FreeNode where multiple encodings are used. While I like the idea of supporting a fallback encoding, it has the major problem that we'd need to know the possible encodings in advance.
Could someone add an option to log raw original server transmissions, so I can try and detect the appropriate encoding retrospectively?
That would help a lot in recovering conversations after they turned out to have been interesting.
The text was updated successfully, but these errors were encountered: