Live data from Hacker News

Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails

korte.co

11–20 of 239 posts

Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails

#11
post #2

One understated outcome of Trump 2.0 is waking up some sections of the European intelligentsia to the risk of dependency on the United States. Trump 1.0 should've been enough, but instead European leaders were just too thankful for a Biden back-to-normal scenario that they basically took no action allowing the US to further extend its dominance. Better late than never. Incidentally, trying to build EU tech independen…

Because Trump has 2.5 years left and they may be hoping a Democrat wins

Trump was elected. Twice. It was not a fluke, not a once in a lifetime event, he's a symptom of wider processes happening in the US. The world has changed and the old order is not coming back

Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails

#12
This is entirely the wrong lesson to take from this. Why are we still using a plaintext protocol in this day and age? Why can we not get an E2EE addition to the email protocol with full backwards compatibility?

Yes, I understand that it would be imperfect since inevitably not all servers would support it thus forcing additional understanding and decisions on the end user. No, I don't care that a user other than myself might leak my messages in plaintext. Perfectionism in this regard only serves to further shoot us in the foot. Yes, I understand that key distribution is a difficult problem but then that's the case no matter the protocol. Other protocols have solutions that work reasonably well at this point.

There's no justification for the current status quo.

Alternatively I'd be fine using matrix for all my PII related needs (healthcare, government, subscription services, etc, etc) but somehow I don't see that happening any time soon.

Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails

#13
The fact that government agencies, particularly those that deal with international concerns like these are using non sovereign tech for communications is mind-blowing. They might as well use public gmail.. atleast it would be cheaper. If you want it not exposed directly, host it yourself and take measures to secure it for intended eyes only. This should be common sense.

Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails

#15

This is entirely the wrong lesson to take from this. Why are we still using a plaintext protocol in this day and age? Why can we not get an E2EE addition to the email protocol with full backwards compatibility? Yes, I understand that it would be imperfect since inevitably not all servers would support it thus forcing additional understanding and decisions on the end user. No, I don't care that a user other than mysel…

Getting from here to there is going to be tough, but I agree 100%. Not only should email be E2EE, but it should include a certificate scheme such that you know the person purporting to be the sender is actually the sender.

Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails

#16

This is entirely the wrong lesson to take from this. Why are we still using a plaintext protocol in this day and age? Why can we not get an E2EE addition to the email protocol with full backwards compatibility? Yes, I understand that it would be imperfect since inevitably not all servers would support it thus forcing additional understanding and decisions on the end user. No, I don't care that a user other than mysel…

How about the metadata? Perhaps if you mean something like self-hosted Matrix, then I agree.

Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails

#18
post #4

The irony that it is data from civil servants that wan to implement the biggest central digital censorship endeavor in the western hemisphere.

Is this about EU Chat Control? Because that was mostly pushed from Denmark no?

Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails

#19

This is entirely the wrong lesson to take from this. Why are we still using a plaintext protocol in this day and age? Why can we not get an E2EE addition to the email protocol with full backwards compatibility? Yes, I understand that it would be imperfect since inevitably not all servers would support it thus forcing additional understanding and decisions on the end user. No, I don't care that a user other than mysel…

For large organization data the keys would need to be stored within the organization, not with one particular user as in the case of your personal PII needs.

And then you'd still need to worry about digital sovereignity for the keys.

Post reply on HN