As far as I'm aware the typical command-line stuff and most things just using SSL libs or language standard libraries don't do revocation at all by default.

Similar reason (though with the opposite effect) as how a cert can be fine for browsers but fail for curl when they don't send an intermediate: the "vanilla"/library/command-line stuff is just checking for a path to a trusted cert and not doing the CRL or AIA stuff a browser does.

Yes, exactly what the Apple article highlights! Appreciate the extra context.

CLI-based activity references etc/ssl/cert.pem. While they say this will be updated in the future (likely the next dot release), admins can also proactively remove the eMudhra entries.

I think it's just that Sony doesn't want to pay to license Dolby Vision, not any actual technical reason.

Ube is a purple yam. You might have seen it in Filipino food like halo halo, or various Instagram-worthy trendy ube-flavored purple foods.

It's the in thing just now for whatever reason. I see all the chain coffee shops are offering it. Next year it will be something else.

Not sure how coffee avoided the pickle trend, or maybe that's next

They're just joking that whatever you want, the opposite will happen: if it's something you'd rather faded away, it will stick around. But if it's something you actually want to keep and find again, it will be lost.

Thank you for translating. Reading the comment section of HN is again and again showing that we should never assume the other side understood what we meant.

Lots of libraries offer Kanopy (though it seems like a lot of them have dropped it; I think it's actually pretty expensive for them to offer).

The SIL Open Font License is pretty much the standard for freely releasing fonts. Poke around on Google Fonts or other places that have freely-licensed fonts and you'll find the vast majority use OFL.

Adobe's Source (the basis for this one), Google's Roboto and Google Sans, the very common Inter, Lato and Open Sans, coding/monospace fonts like Iosevka, JetBrains Mono... chances are that a free font you're aware of uses the OFL, particularly if it's even vaguely recent.

This seems like something more intended to avoid a bunch of pointless attempted signups from people who don't understand what having a domain means who then won't be able to do the later step where you verify that you actually own it.

A client-side check's not so unreasonable for that kind of thing.

Of course then you still want the list to be accurate and/or actually have some working support flow that results in an overzealous filter getting fixed. The code suggests that they do or did have a process at some point: the list of specific domains is an override that allows domains that would otherwise match one of the regexes and get blocked.

Yeah but they said it was important security.

I guess the distinction would be that in the formaction/formmethod case you'll also submit all the other form data, while the button action will just be an empty body.

An extra blank form on the page and the form attribute on the button can work around that, and at that point the argument would basically be: this is super clunky.

But there is no semantically valid reason for the button to be in the form if it doesn't submit the form. So move it outside.

"Ah so that's why I kept losing money!"

But seriously, safe to assume they meant to say calls and just accidentally wrote the wrong one.