(the reason is that bsky.app links are exempted, and video.bsky.app is a rickroll)

Note the warning of course, but I'll just try it on an alt first.

Thinking about doing it today myself: github.com/bluesky-soci...

But from all the docs and ToS I can find, it looks like you can technically use TLDs like .cu, .kp, .sy, .ve, etc. as long as you/your business aren't actually considered a target of those sanctions.

As for Tonga/.to, the geopolitics seem... fine? They're so low-profile.

Okay, scratch that. Some services (e.g., DigiCert) will refuse to issue certificates for Russian and Belarusian TLDs. But just because a country code is sanctioned or embargoed, doesn't mean the corresponding TLD will be affected.

knowledge.digicert.com/solution/emb...

brb fact checking myself

ccTLDs run the risk of being impacted by sanctions. Nameservers in the US, for example, aren’t allowed to support (off the top of my head): .ru, .ve, .kp, .cu, or .sy. And .sd used to be on that list.

.to was considered a “gccTLD” by Google (not sure if they still use that terminology officially), which are supposed to be a little better than non-generic ccTLDs in terms of SEO.

Re: the `string4.rs` exercise... it's very clever how the `str::trim` methods return `&str`, whereas the `str::replace` and `str::to_lowercase` methods return `String`. I take it this is because trim doesn't actually require the creation of a new string, and it's more a view of the original string?

In the meantime, you’ll also find me tinkering with Python 3.13 features (experimental freethreading! 🏄‍♂️ GIL? Who’s GIL?), Rust, AT Protocol, and maybe getting back into NixOS.

So, my friends—I am back! I’ll be knocking on your doors to find my next quest. Get in touch if you’re in search of my skills.

I’m proud also of the work my colleagues continue to do. Independent public media is a shining example of operational efficiency, unwavering morale, and tireless service in an industry that demands more from less every day. Please consider donating to your local stations, especially now.

No, of course not. I think my tone must’ve come across wrong. I’m also saying this would be ridiculous and unlikely.

Right. By “break,” I should say “apply whatever measures they plan on applying to UK users that already have ADP enabled.”

You’re right. But what they know vs. what they’ll agree to use for this UK compliance are _hopefully_ different. They can also know your GPS location, but if they break ADP for Americans flying through the LHR airport, a lot more hell would be raised.

Anyone know what standard Apple would use to determine if someone is a “UK customer”? I can think of several metrics…