.io is the ccTLD for Chagos Islands.

UK will give sovereignty of Chagos Islands to Mauritius.

There is a mixed history of what happens to the ccTLD in such cases.

See also https://news.ycombinator.com/item?id=41729526

Some cars already do this, like Tesla's Adaptive Headlights feature [1].

[1] https://www.tesla.com/ownersmanual/model3/en_sg/GUID-1C20964...

> High beams are currently turned on, and Adaptive Headlights is ready to turn off the high beams if light is detected in front of Model 3.

The description makes it sound like the Tesla implementation of "Adaptive headlights" is actually just "automatic high beams". The most common extra feature of adaptive headlights is corner-adaptive, the ability to pivot into the direction of travel. For the past years adaptive headlights could even mean "smart headlights" with selective dimming. Does Tesla include these features as well?

Anecdotally I can say that what stands out with (some?) Tesla headlights is that they keep the high beams shining for way too long and even the low beams seem to be overly bright. I can't say if this is down to the driver manually controlling the high beams or the general calibration of the incoming light sensor and the auto leveling of the headlight.

Tesla's are the worst offenders outside of big trucks imo

After the detonation of the first nuclear weapons, any newly produced steel has a low dose of nuclear fallout.

For applications that need to avoid the background radiation (like physics research), pre atomic age steel is extracted, like from old shipwrecks.

https://en.m.wikipedia.org/wiki/Low-background_steel

When you don't have a need for a cryptographic digest, it's important to think of the channel's bit error distribution in selecting a checksum algorithm.

Different checksum algorithms can provide better error detection for specific channel error models (potentially even with fewer bits). Non-cryptographic checksums are typically designed for various failure models like a burst of corrupt bits, trading off what they do/don't detect to better match detection of corruption in the data they will protect.

For example, if you know that there will be at most one bit flip in your message, a single bit checksum (parity check) is sufficient to identify that an error occurred, regardless of your message size. (Note that this is an illustrative example only, since, typically, messages have a certain number of errors for a certain number of message bits -- the expected number of errors depends on the size of the message.)

"When you don't have a need for a cryptographic digest, it's important to think of the channel's bit error distribution in selecting a checksum algorithm."

Important real-life-facts.

There was no "give-me-an-appropriate-hash" function.

There was:

md5sum yourfile.txt

Nobody wants to think about "channel's bit error distribution" in a non-security critical context. In fact, its irrelevant, and possibly a usability issue.

I used them extensively when I worked on Radar contact tracking. They are an effective tool when used with a good understanding of the limitations.

Posted earlier: https://news.ycombinator.com/item?id=37753719

The Navy Electricity and Electronics Training Series (NEETS) are a good high level overview that can help you learn which areas you want to explore further. Specifically to the questions you asked, module 1 will give you the overview on basic circuits.

[1] https://archive.org/details/neetsmodules_202003/