Encrypt-Keeper

I make only slightly less than that in American dollars and I’m not at all close to running a company. I’m very solidly lower middle class I will also not be buying a hour for another 5-6 years.

That is a very modest amount of money for his role.

It kinda seems like you don’t understand the actual technology.

You’re talking about things that you don’t understand on a fundamental level. Maybe stick things you do understand?

Tech bro is practically a slur and doesn’t refer to “dudes that just work in tech”

We don’t need to stop saying E2EE is safe, because it is. There is no arbitrary usage. Either it’s E2EE. If a company lies to you and tells you it’s E2EE and it’s not E2EE that’s not arbitrary usage, it’s just a lie.

I’m saying that a company can just arbitrarily decide (like you did) that the server is the “end” recipient (which I disagree with).

They cannot. Thats not how E2EE works. If they can arbitrarily decide that, then it isn’t E2EE.

That can be done for chat messages too.

It cannot, if you’re using E2EE.

You send the message “E2EE” to the server, to be stored there (like a file, unencrypted), so that the recipient(s) can - sometime in the future - fetch the message, which would be encrypted again, only during transport.

That’s not how E2EE works. What you are describing is encryption that is not end-to-end. E2EE was designed the solve the issue you’re describing.

This fully fits your definition for the cloud storage example.

It does not. Cloud storage is a product you’d use to store your data for your own use at your own discretion.

I would argue that the cloud provider is not the recipient of files uploaded there

It is if you uploaded files to it, like on purpose.

You’re confusing E2EE and non E2EE encryption.

No it doesn’t, and I defined E2EE exactly one way. E2EE stands for “End to end encryption”, which means it’s encrypted at one end, decrypted at the other end, and not in the middle.

It doesn’t matter if they store a copy of your message on an intermediary server, the keyword there is intermediary. They are not the recipient, so they should not have the ability to decrypt the content of the message, only the recipient should. If they are able to decrypt your message, despite not being the recipient, it’s not E2EE.

A cloud drive is an entirely different case because the cloud drive is not an intermediary. They literally are the second E in E2EE. A cloud drive can have the ability to decrypt your data and still be E2EE because they are the recipient. You both seem to be under the impression that a cloud drive is an “intermediary” between your devices but it’s not. It’s a destination.

To explain it a bit simpler, imagine we’re in elementary school sitting at our desks and you’re sitting two desks away from me with one person between us:

E2EE = I encrypt my note with a simple cipher that I shared with you and only you before class. I pass my note to the kid between us to pass to you. He can’t read the note, and if he writes down a copy of my note before passing it to you it doesn’t matter because he still won’t be able to read it because he’s doesn’t have the cipher because he’s not the recipient, you are. He passes you the note and you can do whatever you want with it, including decrypting it, because you know the cipher. All the E2EE has done is ensured the kid in the middle can’t read the note. It has nothing to do with whether or not you can read the note.

Zero Access Encryption = I encrypt my note with a cipher that only I know. The kid in the middle can’t read this note, and neither can you. Then I use E2EE to encrypt that with a different cipher, the one that you do know, and hand the note to the kid in the middle to hand to you. The kid in the middle can’t read the note, and neither can you.

It’s not that I disagree with you on principle, I think you’re just kinda mixing up scenarios here, and the purpose of E2EE. E2EE refers to in transit data specifically. #1 should never be where your mind goes because E2EE does not imply your data will be encrypted at rest at the destination, that’s not what it’s for. E2EE is a critical factor when the untrusted facilitator party is between you and your intended recipient, not the recipient themselves.

Like in your scenario of a “cloud drive”, E2EE would not be a selling point of that service. The term you’re looking for in that scenario is “zero access encryption”.

Like you’re correct that E2EE does not imply that data stored in the cloud is encrypted at rest, but that’s because it isn’t meant to. Like this isn’t a dirty marketing trick. E2EE just needs to do what it says on the tin, which this X chat does not because they in order for it to be E2EE, it needs to be the case that only the recipient can decrypt it.

I mean TLS is also encryption in transit, it’s in the name. And it would sorta be end to end if you’re terminating TLS at the end you’re trying to talk to.

I mean they’re encrypted in transit. They’re just not end to end encrypted.

I’m using UnRAID for storage and getting another Linux machine to mount a share on boot has been an exercise in futility so I get it.

Not if you use a vpn. Being that this is Selfhosted, the best idea is to just host your own Recursive DNS server.

IRC and forums as well to a lesser extent.

Jellyfin is still not up to snuff with where Plex was pre-enshittification, but Plex is enshittified. For everyone in between, there’s Emby, which I have been very happy with.