45 karma · joined March 8, 2023
I feel it important to point out that most to all such links as in the original article are in the very early stages of being investigated. And no personal or medical consequences should be drawn from that, and a lot of caution should be exercised.
The black line in Germany would cut off all of the shipping lanes and make gates and sluices necessary out there between the island chain. Where ground is totally unsuitable for that: The Wattenmeer is more of a tidal salt water swamp which goes out for tens of kilometers from the cost. Interrupted of course by deep cuts where the major rivers go out and shipping goes in. On the outer rim of the island chain, there is also a current along the coast that will make any major construction difficult, to say the least. Many islands struggle with that current reshaping them, for the most well-known example, see Sylt.
And before anyone says "well, they did it in the Netherlands", no, they didn't. The Ijsselmeer was a bay they cut off and drained, not an exposed coastline.
The realistic option (that is getting implemented over time) is just fortifying the existing dams. A few minor islands might cease to exist, but saving them won't be cost-effective.
Any other aspects of what UI design is supposed to be about, ergonomics, usability, consistency, accessibility, internationalization is total crap in HTML/CSS. What is the taborder of your custom HTML/CSS datepicker? What will happen when I press <Esc> on your custom css popup? What is the keyboard shortcut to highlight that form field or to open that hamburger menu? How will my screenreader pronounce that hamburger symbol? Will it be the same for the next great HTML/CSS creation? Will the date format follow my locale?
HTML/CSS is great only if you are the strictly visual aesthetics kind of "designer" who only care about reproducing their napkin drawings and photoshop mockups. For all the other things one would ask of a proper UI, HTML/CSS is either useless or actively detrimental.
And "involve" might mean: wait for a bunch of unresponsive external parties to produce a new binary each for a security issue they might not care about. Of course on very different timelines, etc.
The thing you need to guard against is relocated/reserve sectors, in HDDs same as in SSDs. The proper way to do this is full disk encryption, and if that's not possible, physical destruction.
But all modern HDDs retire sectors that exhibit a higher correctable error rate and replace them by reserve sectors. Those retired sectors then still contain readable data (maybe with some bit errors) if you know the appropriate factory mode commands. Overwriting the entire disk also won't overwrite retired sectors, except if the disk has an explicit function for it and you trust that function to work properly.
In short, you always need full disk encryption.
I'm also unsure as to why you are getting drives back at all, any of your customers should not have any kinds of storage devices leave their site intact. At least that is the standard over here in Europe for healthcare and other industries dealing with sensitive data.
Also, TRIM is only possible with drives that are still in working order. Very often you can't TRIM or secure delete a drive that is defective and returned by RMA. In that case you either need a very expensive no-disk-return support contract. Or you just use FDE.