Another alternative that is used on some business laptops is a collapsible RJ45-connector: http://www.pcstats.com/article...
"steal and redistribute", and this garbage is voted 3, Insightful? WTF.
You might wanna look at what headers slashdot sends as well: https://securityheaders.io/?q=...
It really shouldn't work.
The plaintext version of slashdot uses http 301 (moved permanently), which causes the browser to simply skip connecting to the plaintext version the next time and connect directly to the redirected https URL.
Google.com however, uses http 302 (moved), which does not cause this caching to occur, and will work just fine for this purpose.
If Slashdot had used the "Strict-Transport-Security" header as well, your browser should categorically refuse to connect to the plaintext version (after your first connection) until the expiry date has been reached (usually quite a few weeks into the future)
680mSv will cause radiation sickness if the exposure is within a short time span. You do not know the timespan of this exposure. It may be more than five years in total.
very rarely do water cooling systems incorporate a completely external radiator.
All mine have had an external radiator. In fact, I haven't seen one that wasn't external.
Irrelevant. We cannot possibly know "all variables" - and thus stating that all variables have been accounted for is bunk.
However, that doesn't mean that the study is wrong - it's just not good enough.
Storing a lot of data on Youtube can be done. It can be done in a hacky and good way - and it can be done in a shitty, QR-code, spacewasting way.
OP is not me - but I often post as AC because I can't be arsed to log in.
Yes, you could write a stopwatch app which runs on the bare metal, without relying on anything but the hardware (OK, and the part of the BIOS which starts the bootloader, unless you want to re-flash the BIOS). However that would be more complicated than you think. You'd have to initialize all the hardware yourself and handle everything on the lowest level.
The BIOS initializes all that is needed for a text-mode stopwatch. It would really not be hard to write in asm.
Doing a GUI stopwatch on the bare metal would be no more complicated than doing a text stopwatch on the bare metal ("CLI" wouldn't exactly apply then, because without some operating system, there would not be a command line to begin with, unless you'd take the unnecessary complication of additionally writing a CLI to run your stopwatch from). Just the data structures to be copied into video RAM would be a bit bigger. But then, the mouse handling code would probably be much simpler than the keyboard handling code you'd need for the text version.
While USB keyboards work in compatibility mode - requiring no USB driver, the same is not true for a mouse. That would require USB drivers. That in it self would be far more complex than writing a text-mode stopwatch.
You can fork the software and hardware designs. Depending on how incredibly advanced your 3D printer is, you could in theory print it too...
Bare NAND is presented as a block device. NAND SSDs are also presented as block devices. That does not imply that they are equal. SSDs have a controller that does remapping on the fly, in many cases on the fly compression, bad block handlling and much more. Bare NAND does not have that layer. That is why the ACs comment should be moderated informative, and you should be moderated "plain wrong".
Beware of the Turing Tar-pit in which everything is possible but nothing of interest is easy.