I did have the same feeling about flashlights for camping/hiking with lithium batteries, though, until someone walked me through just how much better they are than lugging around AAs.

USB-C has allowed me to grab one decent two-port charging brick, two solid 6ft cables, and charge just about everything I own just by keeping those in my backpack. If I think I'll need to move any data fast, etc., I just throw my one good USB4 cable in my bag, too.

I will admit, though, that I've had some crappy situations at work where it turned out my flaky monitor setup was due to the stupid work-provided docks coming with cables that only supported 10Gbps. Better labeling would've solved those ones.

And if your landlord is balking at including heat in rent, there's a decent chance it's because your bill will be outrageous because there's zero insulation, and as a tenant there's little you can do to fix that.

Entirely unsurprised that someone would refuse to give up their workflow, though! I've rarely found a user with specific needs who wants to change literally anything else about their system, since what they have works for them.

The language towards the end of the press release implies to me that they're targeting last-gen Intel MacBook Air users thinking about upgrades more than anyone with an M2/3/4 MacBook.

Typically seems like $100-200 per year for coverage that would handle the loss of most of one's possessions, provided you don't get screwed by "well, you don't have the receipt" or "we only cover water ingress, not floods or leaks".

As someone who recently started using iNaturalist, I've been curious about this. I think it's an awesome platform and really cool that people can share what they find, etc, but I noticed that people would pile on with species-level IDs on pictures that were obviously ambiguous between different species known to exist in the vicinity.

I of course want as much data as possible to be available to science, but it piqued my interest about whether a negative feedback loop of misidentifications to future identification models could form.

GPS system time is currently 18s ahead of UTC since it doesn't take UTC's leap seconds into account [0]

This (old) paper from USNO [1] goes into more detail about how GPS time is related to USNO's realization of UTC, as well as talking a bit about how TAI is determined (in hindsight! - by collecting data from clocks around the world and then processing it).

[0] https://www.cnmoc.usff.navy.mil/Our-Commands/United-States-N... [1] https://ntrs.nasa.gov/api/citations/19960042620/downloads/19...

The GPS satellite clocks are steered to the US Naval Observatory’s UTC as opposed to NIST’s, and GPS fails over to the USNO’s Alternate Master Clock [0] in Colorado.

[0] https://www.cnmoc.usff.navy.mil/Our-Commands/United-States-N...

Conveniently for me, they keep releasing things right as I start to have an interest in using that thing.

So far, I've been a big fan of netplan (which I guess is tied in with cloud-init?). Dropping a YAML file that declares the network setup I want and lets a swappable renderer make it so on the backend is a nice change from the brittle-over-time series of commands that it took previously.

That in turn reminds me of the DHL flight out of Baghdad in 2003 that was hit by a missile [0]. Absolutely amazing that they managed to keep it together and land with damage like that.

[0] https://en.wikipedia.org/wiki/2003_Baghdad_DHL_attempted_sho...

Don’t like the thought of explaining a radio experiment to a flight attendant at 30,000 feet!

Of course, you can't know the true intentions of the teams, but they all seem to have gone down there with great respect for the ship as a gravesite.

So you’ll get a bunch of “hopefully this week” up until it expires.

I absolutely refuse to hand over my credentials and cannot wait for the practice to die.

Personally, I appreciate getting an email with details and a link for tracking. It does get annoying when it turns into low-grade spam, though.