

Man, Vance, just shut up. You don’t have to be a sycophant to stay his VP and takeover when he kicks it.
Owner and admin of blimps.xyz
I’m a dorky inflatable latex coyote! Linux nerd, baker, some 3D things as I learn. Also love latex. The material, not the typography thing.
Links: https://fursona.directory/@KayOhtie
KeyOxide: openpgp4fpr:134CEDFA7E5546F251394038260773BD8F218384


Man, Vance, just shut up. You don’t have to be a sycophant to stay his VP and takeover when he kicks it.


Nextdoor drives me nuts. I see people posting ChatGPT-generated menu poster things with not-food images in them and some folks just slurping it up despite things like when there’s 5 sides listed, and because 2 of them are potato it ends up scrambling them into one gross object (raw/boiled fry-shaped potato sprinkled with paprika, mashing up ‘potato salad’ and ‘french fries’).
Or ‘chicken’ that is Ribbed For Your Pleasure, or chicken where every hair pore is toasted so that it looks simultaneously burnt and raw.
Huh, kinda cool. I mean it makes sense too since it’s got that “copying someone’s homework” benefit for updates too.


Not an article, but as others have pointed out with Google, what’s more likely is that Apple hasn’t added an explicit processing exception to the US GIS data published at the federal level.
Most map providers ingest this data and process it, along with adjustments or additions of their own, and that includes the names of features like Lake Ontario and the Gulf of Mexico. Google appear to update their GIS data very frequently, hence it appearing the same day it was published by the USGS.
Apple must take longer. In addition, the zoom level thing is probably from it just prioritizing the Canadian GIS data at that zoom level for that feature body, which still has the correct name. Meanwhile, MapQuest would’ve outright added a processing rule to rewrite that name so they can continue to use the USGS GIS data but have “Lake Ontario” show up properly. Same thing for both Google and Apple on “Gulf of America” showing up, because Google processes daily and Apple less often and neither added a rule to keep the canonical name the same.
So I don’t know if I’d say “capitulation”, in terms of what that generally means, taking specific actions to give into something, but maybe it does, since this is effectively Apple’s inaction passively leading to it. Maybe it’s more complicity through inaction.


It’s also literally rules of the subreddit.


All 3 mechanisms are native to a yubikey, and do not require yubikey-specific software/drivers to function as they use USB standards like FIDO2, keyboard for HMAC, and PIV/CCID for OpenPGP.
FIDO2 is built-in out-of-the-box, HMAC just requires adding the key to HMAC on slot 1 or 2 (tap vs long-hold key-inputs) using the personalization tool, or using gpg(2) to card-edit for OpenPGP.
None of these require YK software to operate.
Wouldn’t surprise if Creative Commons had something to do with this. The copyleft licenses of it, of anything more restrictive basically than MIT and “attribution”, are listed as “restrictive” and “not open” or something. I think coupled with the complicated legal language versus “idk, whatever man” doesn’t help for lots of new projects.
That said… Most of the stuff I’ve done has been so “idk, man, I made a thing for me and figured others might benefit” that I just gave it the MIT license for that reason. And it may just be as simple as that reasoning.