That would also tank the stock price though.

Ctrl+r in any terminal will open up a search mode for your history.

Soon they may come with cellular capacity. Cars and e-bikes already do.

You gotta Faraday cage it!

I prefer quotes to be as close to the original as possible. Hurtful as it is. That’s kind of the point here.

Censoring the bad shit that happened before is a sure way to repeat it. See holocaust denial for the extreme. Don’t deny talking about the past just because it hurts.

No but then the argument above falls flat, doesn’t it?

You are obviously not interested in listening to a word I’m saying. Goodbye.

Alternatively, we need to stop saying E2EE is safe at all, for any type of data, because or the arbitrary usage.

You probably didn’t understand me. I’m saying that a company can just arbitrarily decide (like you did) that the server is the “end” recipient (which I disagree with). That can be done for chat messages too.

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. This fully fits your definition for the cloud storage example.

By changing the recipient “end”, we can arbitrarily decode the message then.

I would argue that the cloud provider is not the recipient of files uploaded there. In the same way a chat message meant for someone else is not meant for the server to read, even if it happens to be stored there.

Uhh yes, sorry. I had it the other way around. Perhaps a native american then raped/had child with a caucasian, who kept the child?

The third paragraph contradicts your other point. You define E2EE in two wildly different ways.

The chat messages are most likely stored on an intermediary server, which would qualify for the same loophole you pointed out in the cloud storage example.

No, the other ancestors are all native American. Obviously the child stayed in the native to community.

/s/dataisugly

There may be several reasons for this. If I had to guess, they found a critical flaw and had to shut it down for security reasons.

Just to be the devil’s advocate here: There are way more settings now than back then. That interface wouldn’t cut it either.