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 from contacts that have end-to-end encryption enabled don't show up.
Sending them a message with /msg crashes the connection and bitlbee reconnects.
The text was updated successfully, but these errors were encountered:
Yea and new conversations don't get opened in bitlbee.
I've been having a look at this and Facebook is forcing upgrades to end-to-end encrypted conversations. You can't downgrade the conversation without deleting the existing one, and there's no option in the parameters to disable it.
Seems like the beginning of the end for bitlbee-facebook, unless someone takes over the maintainer role and codes end-to-end encryption in bitlbee (if even possible)
I'm working on the Pidgin Facebook plugin, we're in the same position as Bitlbee now with End to End Encryption.
From what I've read it's straightforward to implement the encryption. We need to start by identifying the chats which should be encrypted in the client, then we can look at implementing the encryption. The documentation I've found describing the encryption looks good enough to implement a client with. But I need to understand the JSON/MQTT components.
Message from contacts that have end-to-end encryption enabled don't show up.
Sending them a message with
/msg
crashes the connection and bitlbee reconnects.The text was updated successfully, but these errors were encountered: