That’s odd, but truly sorry.

OK kids, one more time. Repeat after me: Cloud is just someone else’s computer.

Yeah, I run dual stack without much trouble myself. I believe it is mainly difficult for people because eyeball diagnostics are impossible with 6.

It’s vulnerable af. And I mean really, it’s as bad as Netscalers or Fortigate shit. Like https://www.bleepingcomputer.com/news/security/hackers-abuse-ipv6-networking-feature-to-hijack-software-updates/ or https://www.bleepingcomputer.com/news/security/hackers-abuse-ipv6-networking-feature-to-hijack-software-updates/

Problem is, yes it’s hard to implement but it’s even a lot harder to get it properly secured. Especially because few people are using it, and not securing it is worse than disabling it.

Not surprising, science is done in proper metric to start with.

Nice opinion piece, but I disagree with the core idea that dnssec’s biggest problem is visibility (also, there hasn’t been any padlock icon in years in browsers). IMHO we have 3 main drivers that made https a success, and dnnsec (and smtps) not:

• enforced by browsers: while you could file it under “visibility”, the difference to me is that browsers refuse to load your site without https. If they had resorted to a mere red address bar, https would never really have taken off.
• ”atomic”: a site with failed https is only 1 failed site. Other sites, APIs, mail servers etc under the same domain will still work.
• DNSSEC is HARD. Yes, your dns./website provider makes it look easy but really, this stuff is seriously hard to do right now, and there is little tooling to help you with it; the same reason smtps (and maybe ipv6) failed so hard, I think.

Paying customers can install a protocol bridge between Proton and regular mail client. This does break the security of local storage as TB doesn’t supply any.

Ceasefire only exists if you stop shooting, and everyone knows you can’t do that

It’s 12b usd spent elsewhere too.

Which is true, however: if they pull it off, others will follow. Don’t let perfect be the enemy of good.

Why all the effort? Wait a few weeks and Microsoft will have renamed it themselves anyway.

Great, massive step forward. Rust’s memory safety will prevent potential PE vulnerabilities (and more).

Nee dat is wéér anders. Even kijken … út it Fryske lân komt een mân mè lânge tân… of zo.

Dutcher than Dutch, don’t worry. Good to have you back mate!

Wâ mojje nâh @Stamets@lemmy.world , hèi ek wâ vajje án??

firk repo

A fulfilling life if I ever saw one.

Anthropomorphising your overhyped statistics algorithm again I see. Here’s your straight jacket, solitary confinement for the rest of the week chaps!

I did not say that.
I said the central EU is trying - almost literally on a weekly basis - to require companies like Signal and Whatsapp to replace their end-to-end encryption with a backdoored one, and the excuses they throw up every time is “pedophiles” and “terrorists”. I am quite aware Switzerland is trying that as well, hence the announcement by Proton to leave the country if the government keeps hanging on to that dumb idea.

Be careful with any EU country… there’s a weekly attempt to introduce backdoored encryption, because “pedophiles” and “terrorists”.