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.
Dunno whether that was a bug nor how likely it's to happen again, but here's what happened.
I was chatting with my bro yesterday (or a day before) via FB (purple). It was a 1:1 conversation. And one of the messages I sent to him came to me as a new conversation, i.e. a new pidgin tab opened, there was a message I sent and the sender was my own FB account. I kind of had a chat with myself :) However anything I wrote in that new chat was not echoed back.
P.S. my brother received the message as well (on FB messenger)
Not sure whether this happened due to FB's fault or there was something overlooked in purple's code. I just felt I should report it.
The text was updated successfully, but these errors were encountered:
Hello. This happens to me also. It has something to do with disconnection and unread messages. I don't have a stable connection, so sometimes connection is broken and then, after reconnecting to FB servers, unread messages appears in correct "windows" and sometimes new window with myself appears. (in Finch, messages are marked as read after switching to a conversation window - if it's already opened, messages are not marked as read so after reconnecting they are loaded again)
Dunno whether that was a bug nor how likely it's to happen again, but here's what happened.
I was chatting with my bro yesterday (or a day before) via FB (purple). It was a 1:1 conversation. And one of the messages I sent to him came to me as a new conversation, i.e. a new pidgin tab opened, there was a message I sent and the sender was my own FB account. I kind of had a chat with myself :) However anything I wrote in that new chat was not echoed back.
P.S. my brother received the message as well (on FB messenger)
Not sure whether this happened due to FB's fault or there was something overlooked in purple's code. I just felt I should report it.
The text was updated successfully, but these errors were encountered: