hades

182 is the objectively correct answer.

30 years on the internet, never seen so many people being wrong.

I can't imagine how normal people use any software at all. When something doesn't work for me, often I can figure out what could've gone wrong. For instance, there might be bug in the JavaScript form handler, and I can just bypass it. Or an app doesn't invalidate its cache properly, so I just need to flush it manually.

One problem with that is that you will end up with two EFI partitions. This is not supported very well by anything, really, so you will run the risk of Windows messing with the wrong partition anyway.

I've updated my comment.

I switched to Proton from Express when the latter was bought out by Kape.

Proton works perfectly so far for me. Their desktop software was a bit meh, but they've since improved it. Otherwise I have no notes.

Edit: it appears the PWA support in Firefox is not ideal, see responses to this comment.

Chromium is not an offshoot of Chrome, it's more of a precursor to Chrome, and it is completely controlled by Google. As such, it will also drop support for extensions that do not support Manifest v3.

If you want to enable PWA support in Firefox, it looks like this is possible (however the experience doesn't seem to be great, see responses to this comment): https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Installing

For other browser suggestions see, e.g. https://www.xda-developers.com/4-browsers-manifest-v2-ublock-origin/

Ah yes, that's Android for ya.

If you wanted to support all possible drivers, you would basically need to rewrite the entire kernel. You could make one specific anticheat work by supporting its specific calls, but this will take a lot of work, and will probably be broken with the first ever update.

In the past there were projects that supported specific types of drivers, such as ndiswrapper, but that had a very limited scope.

Here's also an answer to a similar question: https://unix.stackexchange.com/questions/544776/installing-proprietary-windows-drivers-on-linux

All right then, Germany, keep your secrets.

Nice article!

You seem to be missing the word "by" in the table introducing threat T04. Also, the threat summary table uses ✅ and ❌ in a way that was counterintuitive to me: initially I thought ✅ meant the encryption approach protects against the threat.

A bigger issue IMO is how you describe email encryption in transit as a matter of fact, but according to Google transparency report[1] there are still domains that do not support in transit encryption, and, what's worse, when you send an email you can't tell if it will be encrypted or not.

[1] https://transparencyreport.google.com/safer-email/overview?hl=en

"take a decision" is also a valid phrase: https://www.merriam-webster.com/dictionary/take%20a%20decision