rmccue

Seems to me more like they've deployed some default WAF in front of their web properties, without considering the specific needs for the CRL endpoints.

The article’s example of “mis(c)e(l)lany” is one example that stood out to me like this - perhaps in some dialects it’s pronounced with a single S sound, but it’s definitely two for me. (And on the flip side, I wouldn’t retain the second I in “suficient”.)

I feel like it’d make for a great interface for a physical controller for smart lights/speakers. I’ve got a Hue Tap Dial with a physically spinning wheel, but the click wheel would be great instead.

I’m half tempted to buy an old iPod and attempt to hack something together…

Sounds like you're rate limited; working for me.

It's credited at the end as being a repost of the article from The Sentinel, so at the very least, the link should be updated.

YYMMDD is standard(ish) ISO 8601 - the new versions of the spec require a 4 digit year but older ones allowed it, and ISO 8601 is also commonly used in manufacturing.

The CLI tools for automation are still a pain to use and missing functionality, which also means LLMs use it less; Claude gives up when it sees Chrome isn’t installed unless I specifically tell it to try and use Firefox.

I created an automation tool recently for taking screenshots (for SOC2 reporting, hopefully tptacek is proud), and getting it working with FF on the CLI was very painful (but necessary since I needed my cookies!)

As just one data point here, let me say thank you for all your writing on it; it was super useful to have things to point at to say “we don’t have to just blindly do a thing the auditor suggested!” for our SOC2.

At least concert tickets are somewhat aligned with listening to music, unlike autoplaying video podcasts on the homepage rather than showing my playlists.

A lot of these videos get recommended to me, and although I haven't done hardware designs in 10+ years at this point, it's pushing me to get back into it again - and PCBWay lives in my head rent-free for when I do. If it were a one-off sponsorship I'd have forgotten about it, but the consistency across a load of different channels really cements it.

An "aggregator" is the thing that discovers and lists repositories - the equivalent of a search engine. Anyone can operate one themselves, and we (the FAIR project) operate a canonical one on our website, which is fair.pm.

I think it's understandable for both Backblaze and most users, but surely the solution is to add `.git` to their default exclusion list which the user can manage.