Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails
21–30 of 239 posts
Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails
#22The 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.
I was going to ask why something like mail.gov.nl doesn't exist but it turns out [0] (edit: wikipedia is full of lies) that they don't have a reserved second level domain for official government services to use? Is this really one of the countries pushing digital IDs?
> Official second-level domains do not exist.
Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails
#23The 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
#24The irony that it is data from civil servants that wan to implement the biggest central digital censorship endeavor in the western hemisphere.
Ah, yes. Sure. Proof?
Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails
#25I was trying to read the article, but those animations kept distracting me.
Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails
#26Digital sovereignity is not enough. You need to get electronic communications completely off the internet.
Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails
#27Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails
#28This 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
#29The 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.
It's mind blowing that government bureaucrats would be permitted to use commercial providers for official business at all. The provider being foreign is merely the cherry on top. I was going to ask why something like mail.gov.nl doesn't exist but it turns out [0] (edit: wikipedia is full of lies) that they don't have a reserved second level domain for official government services to use? Is this really one of the cou…
Re: Digital Sovereignty Becomes an Imperative as the US Reads Dutch Emails
#30This 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.