Proposeal to change the title of the Encryption case

Phoenix Case Discussions
, , , ,
1

Talking about Terms of Service; Didn't Read - Phoenix

I would like to propose to change the title to

This service claims User-generated content is encrypted, and this service cannot decrypt it

Current title

User-generated content is encrypted, and this service cannot decrypt it

As we don’t verify the source code (which in some cases is also impossible). Neither do we verify the strength of their encryption.

x.com for example has been criticized for only securing E2EE messages with a six digit pin, which would be trivial to brute force for a malicious server. [1]

Additionally we should think about how we handle services that only encrypt some user generated content like X or Telegram.

  1. https://mjg59.dreamwidth.org/71646.html ↩︎

2

Not to mention we have (or had) that WhatsApp lawsuit to pay attention to…

3

Fully agree. Also, we ought to edit the description.

My proposal

According to the service, user-generated content is supposed to be end-to-end encrypted. This would mean that it can’t be accessed or decrypted by unauthorized parties, including the service.

Old description

Content generated by the users is end-to-end encrypted, in a way that it can’t be accessed by anyone unauthorised, and even the service has no technical means to decrypt it.

4

Hmmm, am not satisfied.

Will think about it

5

While the description is being discussed, I’ll change the case title to your proposed title as no objections have been manifested.

Actually, shouldn’t we avoid “The/This service”?

6

i coudlnt word it any better ;D

7

Well, let’s settle for now and see to it later. I’m editing the case name then.

8

Funny timing A Secure Chat App’s Encryption Is So Bad It Is ‘Meaningless’

9

I’m crying out of laughter.

10

the double “it” is weird, maybe like this?

This service claims User-generated content is encrypted, and it can not decrypt it

This service claims User-generated content is encrypted, and they can not decrypt it

11

The service claims that user-generated content is end-to-end encrypted, meaning only intended recipients can access or decrypt it. As a result, no unauthorized parties, including the service itself, can view the content.

This does not necessarily cover meta data, such as the date of creation or sender and recipient information.

12

Sounds better. Took the liberty to fix it.