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
I was shocked to note that TL still "just eats the message" if I initiate a /msg to some other user without first opening a window with /query othernick. The first time it happened, I wasn't even sure my message had been sent until the other user woke up (I assume) and replied.
If logging is turned on, it should be impossible for any message to just bypass the logs and never get saved. Users will distrust TL's logging features if they demonstrate unreliability.
The message was sent; the recipient replied some hours later.
On this network (Rizon), the lobby status messages include Enabled capabilities: away-notify, chghost, invite-notify, multi-prefix, sasl, userhost-in-names. Seems you're correct about this being a network without echo-message.
I was shocked to note that TL still "just eats the message" if I initiate a
/msg
to some other user without first opening a window with/query othernick
. The first time it happened, I wasn't even sure my message had been sent until the other user woke up (I assume) and replied.If logging is turned on, it should be impossible for any message to just bypass the logs and never get saved. Users will distrust TL's logging features if they demonstrate unreliability.
Original comment by me in #590 (comment)
The text was updated successfully, but these errors were encountered: