this post was submitted on 18 Aug 2023
1344 points (89.8% liked)

Memes

45635 readers
1237 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago
MODERATORS
gary_host_laptop@lemmy.ml
sexy_peach@feddit.de
cyclohexane@lemmy.ml
cypherpunks@lemmy.ml
1344
its even more outdated (lemmy.dbzer0.com)
submitted 1 year ago by covert_czar@lemmy.dbzer0.com to c/memes@lemmy.ml
402 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] alvanrahimli@lemmy.ml 1 points 1 year ago (4 children)

e2e encryption makes it difficult to provide fully cross-platform messaging experience, this is probably why they are not looking at it

[–] McCainRBGcreampie@hexbear.net 4 points 1 year ago* (last edited 1 year ago)

They aren't implementing e2e by default because that would limit the amount of data they collect and sell to intelligence agencies.

[–] Pyroglyph@lemmy.world 3 points 1 year ago

e2e encryption makes it difficult to provide fully cross-platform messaging experience

Why?
I can easily encrypt a message on my x86_64 Windows desktop, send it to my x86_64 Linux laptop, and also my ARM64 Android phone, and be able to decrypt it perfectly.

If I can do it then a development team can too.

[–] obinice@lemmy.world 2 points 1 year ago

Why would it be difficult? Encryption isn't difficult (any more than adding any essential feature would be) and is platform independent. It doesn't matter what device you're using, encryption and decryption are commonly used.

[–] linearchaos@lemmy.world 2 points 1 year ago

You can easily implement AES 256 in JavaScript. So you can tap the web framework on any device and run your app on just about any platform.

The problem is, They no longer get signal intelligence from it and can no longer monetize it.