The admin stated they won’t be renewing the domain because .af is now controlled by the Taliban.
Link to post: https://queer.af/@postmaster/111733741786950083
Could we, like, leave the clickbait headlines to reddit? Thanks. The queer.af admins just decided – wisely – not to renew the domain considering who the fee would go to.
The queer.af admins just decided – wisely – not to renew the domain considering who the fee would go to.
So the Taliban being in control of the .af domain. Made the admins not to renew the instance. To put in away, “The instance has been killed by the Taliban.”.
No. The instance being killed by the taliban is the opposite of that is happening here.
The taliban has done nothing, in this case. The admins of the instance have chosen not to keep the instance due to not wanting to fund the taliban in anyway.
This phrasing fucks up which way the action flows, which is important for a headline to get right to remain accurate to the story. Does that make sense?
Reading that headline scared me. For a moment I thought the instance owner was killed by the Taliban.
Another reason to not use ccTLDs.
If the Taliban take over Australia I’ve got bigger issues to worry about than my domain name.
Better to just setup your own ccTLD, for maximum trust.
(honestly only half joking)
.io is the British Indian ocean’s territory, probably not really a risk i doubt anything’s going to happen there.
Nope. The ones you’re mentioned are gTLD (generic top-level domain) but most of the other domains are generic TLD too. See here for the list: https://en.wikipedia.org/wiki/List_of_Internet_top-level_domains
Just don’t use country-code TLDs because they can removed by those countries. For example fmhy.ml and now queer.af.
Just use .net or so. Or make it dependent on where you host, so .fi or .de or .us or whatever. TLDs aren’t just for lulz, and getting specific country ones just for “funny” combinations just leads to stuff like this happening.
No need to limit yourself to US tld’s, country ones for funny domains can be stable as well. My domain koffie.nu (coffee.now in Dutch), registered in '98, is still going strong. I just hope the rising sealevel won’t wipe away the country any time soon.
DNS engineer here: it’s the bane of my existence. Vanity TLDs were a cash grab for ICANN. They have made defensive domains a nightmare
If you’re on the country code, you open yourself up to risk. ml has been a risk before.
Your headline is misleading though. Taliban didn’t kill it. Admin did.
If the Taliban never got control of the .af domain in the first place. The Admin would have renew it. So the Taliban did kill it.
If the US hadn’t pulled out, the Taliban wouldn’t be in charge. So Trump killed it.
Indirectly doing things allows anyone to take the blame!
They could get a .ck domain instead and move to queer.as.fu.ck, no?
Wouldn’t that need them to get the fu.ck domain itself? I have a feeling that is already used by someone else, but there currently isn’t any website at that domain (doesn’t mean it isnt used)
Activitypub makes it next to impossible to “move” an instance to a new domain.
Every post/comment/and user is uniquely identified using the domain. In the eyes of ActivityPub changing the domain just makes each of those things a completely new thing.
You can set up a new service at your new domain and potentially get most all your users to migrate but they’ll be leaving behind their entire histories and as a “new” fediverse user they’ll only be discoverable via the historical posts for as long as the original server is reachable.
Thats IMO one of the worst engineering decisions in the protocol, besides all the others, but this one (making identity depend on domains, meaning on third parties antithetical to decentralization) is… laughable. Who was responsible for it?
But, the theory goes, you’re not supposed to be reliant on third parties as you should be in control of your own domain (or within a few degrees of the person who is).
Large instances are what are antithetical to decentralisation.
Of course, the reality of it is that, it just hasn’t worked out like that.
Not sure how well this would actually work, but couldn’t the admins “copy” the instance to the new domain and then initiate an account migration from the old to the new instance for every account? That should both push out the account transfer to all the other instances and preserve the post history as well.
