Well good thing the American federal government doesn’t rely on a single privately-owned third-party digital identity provider operating on .me!
Timeline
Post
Remote status
Context
3
@badsamurai OTOH: .com, .net, and .org are an international security risk. They're all operated by Verisign and Verisign will do whatever the US Federal government asks them to do.
That also makes them a security risk for people in the USA who may end up on the bad side of the government for any reason.
I don't think any TLD is "safe".
That also makes them a security risk for people in the USA who may end up on the bad side of the government for any reason.
I don't think any TLD is "safe".
@feld absolutely true, and there was a good post earlier today about .in infra on Tucows (Canadian & American).
But we can’t water down the conversation with everything-isms. We need to narrow focus on the largest and most realistic risks, both macro and micro, to potential population. Ideally, governments should address the unacceptable risk criteria involving critical infrastructure and citizens’ data.
Some notable TLD disruptions over the years:
T dot me yesterday: https://cybernews.com/security/telegram-links-broken-after-domain-outage/
Zoom dot io outage last year: https://www.dotuptech.com/post/zoom-s-domain-outage-was-a-wake-up-call-here-s-what-it-means-for-the-future-of-domain-registrars
Regime change disruptions of .ly (Arab Spring) and .sd: https://dn.org/lessons-from-ly-and-sd-uprisings-takedowns-and-policy-whiplash/
@badsamurai thankfully I have had zero issues with my .me domain I've had since 2008 but I really don't trust any TLD at all. It's so sad we're in this position.
Replies
0Fetching replies…