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".
iNaturalist is sometimes used by our ecologists/biologists as a starting point for collating occurrence data.
The iNaturalist data itself is likely specifically being pulled from gbif. Then they go private/specialty databases that have more spatially and taxonomically accurate records.
But iNaturalist data is often not considered high quality enough to be publishable by itself (wide brush statement) in my field of plant conservation.
We've tried to have some conversations with iNaturalist and they weren't really interest in talking, gave me pause on what their motives as an organization are.
But conservation tools are few and far between, and iNaturalist is a really powerful tool for initial data exploration.
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.
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...
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...
GPS has its own independent timescale called GPS Time. GPS Time is generated and maintained by Atomic clocks onboard the GPS satellites (cesium and rubidium).
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.
Cannot emphasize this enough. People with barely enough knowledge (“script kiddies” so to speak) are configuring and using RPi’s. They just want to follow the tutorial and get it working so they can do what they really want. (Eg image processing or run their 3D printer.) Nothing against this kind of user. I help them when, but…
This creates a situation where “the wrong tutorial” problem is unnecessarily easy to stumble on.
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...
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.