pull down to refresh

0 sats \ 3 replies \ @398ja 14 May \ on: GitHub - eddieoz/openxrypt: Secure Direct Messaging for Social Media privacy
It seems this relies on sender and receiver to both have the chrome plug-in installed?
write
preview
0 sats \ 2 replies \ @eddieoz OP 14 May
Yes, and both should exchange their public keys between them. This is because the plugin manages to encrypt the messages and decrypt the messages they identify.
Since there is no connection to APIs or the backend, imagine Twitter as the backend infrastructure for the messaging and the plugin as a layer over Twitter that handles the e2ee encryption.
reply
0 sats \ 1 reply \ @398ja 14 May
That's what I thought. The extra step of exchanging public keys can be challenging, and is inconvenient, just like with pgp. But nevertheless, it's a good thing to have for those few who really need it.
reply
0 sats \ 0 replies \ @eddieoz OP 15 May
Unfortunately yes. PGP has issues with usability, but it is safe.
The idea was to create something fast, reliable, simple, easy to verify, and trustworthy. This is the first version, and a lot can change.
For our community, I think it is better to release something safe and discuss what to change in usability than the opposite.
With the core working properly, the goal is to develop UX even if it means changing algos, etc. :)
reply