Actually, OSM has added the "Lake America" alternative name as a US-specific official name by adding official_name:en-US=Lake America to the lake object. See changeset 188340009.

In OSM's tagging scheme, this is the correct way to do it: the US, and only the US, now officially refers to the lake as "Lake America", hence the use of a localised value for official_name=* However, the value of name=* is what is commonly rendered (depends on your renderer, but I'm yet to encounter one that cares about official_name=*), and this value remains "Lake Ontario". The value of name=* should generally be the common default name, and since everyone except the US government is unlikely to recognise the name change, leaving name=Lake Ontario well alone is also the correct way to do it, despite the current administration's contrary opinion. This means that you'll almost certainly continue to see "Lake Ontario" in OSM.

OSM has some comprehensive documentation on how differing names should be tagged, and it appears that the OSM community has followed this to the letter in dealing with this situation.

For those interested, the full amendment to immigration instructions may be found in Amendment Circular 2025-02.

A few things worth pointing out:

1. 1. This does apply to those nationalities that can travel to New Zealand visa-waiver (holding an Electronic Travel Authority) and that can apply for a Visitor Visa at the border.
2. 2. Remote work is not in itself a lawful reason to visit New Zealand and needs to be combined with a lawful activity that one may do on a Visitor Visa (e.g. tourism, visiting friends and family).
3. 3. Normal Visitor Visa rules continue to apply: one must have sufficient funds to support themselves (NZ$1000 per month, or NZ$400 if accomodation is prepaid) and an outward ticket to a country that one has a right to enter, and must be prepared to show this evidence to an immigration officer at the border if requested. The outward ticket part is usually checked by your airline when checking in for your flight.
4. 4. Social media influencers need to be particularly careful. If they are promoting an activity, event or product for gain or reward from a New Zealand business or person in New Zealand, this falls outside of the definition of "remote work" and they would need a Work Visa. See: that "IShowSpeed" idiot that did just that and found himself on the wrong end of a deportation liability notice.

It's entirely plausible that the replacement motherboard may have been shipped with an updated BIOS that has more sane defaults. Reading TFA, this appears to be the direction that Intel is pushing the motherboard manufacturers in.

I am the system administrator.
My voice is my passport.
Verify me.

They're pretty terrible in a RAID array though. While they perform well when writing and reading big files, RAID arrays often don't have those characteristics. There was that incident from a few years ago where Western Digital and Seagate didn't clearly demarcate SMR drives as such, and people that unknowingly inserted them into RAID arrays were less than thrilled.

Given the quality (or rather, lack thereof) of the software that Microsoft produces, it's not like anyone does any work there anyway.

Filesystems aren't broken. These Didgets kids should go and find Real Problems to solve, and get the fuck off our lawns.

India already has nukes, but I think you'll find that most of them are pointed at Pakistan (who they currently consider a greater threat).

And for those who don't know where that setting is, it's under "Network" (learn from my mistake and don't go hunting for it in "Remote Access" instead!). You'll also need to show advanced settings for it to show up.

To put this into terms that the average Slashdotter would understand: picture the above in terms of OS updates. The UK (and Australia) is like running apt list --upgradable, then picking and choosing which packages to update. The US is like Microsoft pushing Windows 10 feature updates on you.

This was previously the case, up until around the mid 19th century or so. The problem with this idea is that it only really works if each point in the country is relatively isolated from each other point -- and this fell apart rather rapidly when rail transport and telecommunications became a thing, as the improvements in global connectivity from around 1850 or so resulted in a need for interacting parties to communicate mutually comprehensible time references to one another. If you do some reading up on timekeeping on American railways from before time zones were a thing, you'll quickly discover that it was as convoluted and chaotic as modern day American elections.

And that's why a lot of places had adopted some standard time zone by around 1900: time zones accumulated these local differences into longer units (hours) so that nearby places can share a common timekeeping standard. Hell, it's not perfect -- no human system ever can be or ever will be -- but you have to ask yourself whether increasing the current 38 UTC offsets to ~1,440 (assuming UTC offsets to the nearest minute, or 0.25 degrees of longitude -- and this effectively was the system in the early 1800s, and is what you're proposing) is, in this day and age of global communications and connectivity, a good idea after all.

... and history tells us what phase follows.