Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to chat with contacts that have end-to-end encryption enabled #222

Open
svennidal opened this issue Apr 17, 2024 · 2 comments
Open

Comments

@svennidal
Copy link

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.

@Perdu
Copy link

Perdu commented Jun 6, 2024

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)

@DMJC
Copy link

DMJC commented Sep 15, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants