The coming war on end-to-end encryption

> The conclusion I came to is that a lot of people complain about the impending end of E2EE but very few people are actually willing to do anything about it except whine.

The connection between E2EE and privacy is to ephemeral to make that kind of judgment. If you live in the united states or similar country with a strong rule of law, the idea of paying for or using a specific E2EE app is functionally like asking somone to pay for free speech.

And even if it was more clear, privacy is like free speech in that you cant really measure enthusiasm for it in that way. Free speech and privacy are fundimental values that people dont want to pay for (for good reason!). But that does not mean they dont care.

People really do care about these things. And many many people will change how they vote and how they engage in civic action based on these principals. But asking someone to change how they live/communicate with others requires more then an intelectual "which party / candidate should I vote for?" kind of thing. For most people you need emotional investment for someone to overcome switching costs based on nothing but ethical / political principal.

As long as the harm to losing these core rights remains abstract you wont be to measure how much they care with metrics like that. Its a value that is too ephemeral and disconnected from day-to-day life to measure with a stick like "who will use this app".

But people can and do donate to groups like the EFF, and vote with their actual votes on this stuff. People really do care. Just like how people really do care about honesty, free speech, candor, trust, and other values of that sort. its just, you know, hard to measure.

I like the intent of this! My main question is, how do we know redact.ws won't suddenly serve different Javascript one day, to certain clients, which send unencrypted payloads somewhere?

What is it? Seams like it's an implementation of ecc,but does what? A p2p chat? ::Shrugs:: I'm not sure the failure to adopt your one elusive product speaks for the entire pop.

Obviously you can't pick up a grocery delivery and remain anonymous.

But in theory if you could pay for groceries with monero (you can't afaik), you could pay from the same wallet you conducted a hack from or purchased a darknet server to host leaked data with. The grocery store wouldn't know the originating wallet or any of its other activity.

Anyone who thinks grocery stores are going to allow monero payments is pretty naive, but Monero at least makes these flows possible.

For example, if Walmart decided to let people pick up orders with monero payments, you'd log in with your walmart account (linked with real name), place your order, pay to the generated wallet address with Monero, and then show ID on pickup. Walmart would have no way of knowing where the money came from.

I don't have any Monero or particularly like it (but mainly because I consider proof of work unsustainable and wasteful). But you have to admit the privacy implications are interesting, and the technology is impressive.

There are already legal backdoors not actually referred to as that legally and they are used by corporations to meet their regulatory requirements for things like DLP. Google for example supports this. HTTPS doesn't even matter, their site supports DLP appliances logging in and intercepting all corporate interactions on the platform. The same capabilities exist for non corporate but that is used by law enforcement. This exists on all major platforms. This would play into E2EE if the servers create and manage the client E2EE keys which I believe is the case currently on all platforms that support E2EE. I am told that implementing client side libraries like OTR is too hard or too much friction. So what I am saying is that encryption need not be compromised when all corporations willingly create lawful intercept and DLP API's.

To get more information on this have your company reach out to each platform for DLP integrations.