Sucks, but makes sense.
I’m surprised they even attempted to use that domain. The instance still exists and will need to be routed through a new domain. Which, again sucks, because any reference links will be broken now… which… again… has me wondering why they even went with that domain in the first place. Albeit, it was a clever use of a top level. I wonder how many others are doing the same.
🤷🏽♂️
I suspect they skipped checking who controls that domain at the time and just saw that it would make for a good name. Not good practice but I can see how that happened.
The only shame here is that there is no way for an instance to “prove” it is the successor to a defunct domain.
A lot of Lemmy and Mastadon instances have really obnoxious names. I hope they learn from this as use a conventional domain/TLD, and not some random ass countries who could get taken away at any minute.
Is my instance in danger? 😱 Will Luxembourg disappear overnight?
You never know when the Luxembourgish taliban will take over.
NOONE EXPECTS THE LUXEMBORGIAN TALIBAN!
The fact that pornhub is HQ’d in Luxembourg leads me to believe this will be some sort of sexy taliban
Stupid sexy Taliban!
We are ready to reunite Luxembourg any day now, better get ready to move to the be tld.
You mean fr?
No, of course not
I suspect they skipped checking who controls that domain at the time and just saw that it would make for a good name. Not good practice but I can see how that happened.
https://kbin.social/m/random/p/4648694/To-the-people-who-are-like-What-did-you-expect
Ahh. I have several domains and a lot of experience with managing various services, but I’m unfamiliar with any requirements regarding the federation process itself. I imagine this may be challenging, but not impossible to handle. Yet another level of suck in this situation.
I doubt most people know that country TLDs are different from vanity TLDs. I know when I look up domains, they’re usually all smooshed together and then the terms are in a giant block of ToS.
The vast majority of people likely don’t know that .tv isn’t a vanity or official TLD, but the Tuvalu country TLD. And its royalties make up nearly 10% of the state’s budget.
So… twitch.tv is actually twitch…Tuvalu???
Back in the days bit.ly was a quite popular link shortener (it’s still a link shortener) and when shit went down in Lybia gadda.fi (or some other spelling don’t remember) plopped up as a novelty shortener to protest against using just any country TLD for random internet domains. .fi should be fine, it’s Finland.
Interesting. I wonder if that has anything to do with why some companies started dumping them for regular TLDs.
Similarly, the .io TLD is for territories around the Indian Ocean. But for some reason, it became popular for cheap little flash-style games.
Yeah, this is most probably true.
Honestly though, I don’t even know what most of the generic domains are that were created. It’s still deeply ingrained in me that any serious website should be using .com, .net, or .org. But… the amount of domains that were purchased just for the purpose of resale at an astronomical value has made so many of those unreachable.
There are some dot-coms that I have wanted for years which have been sitting stagnantly for more than two decades. I’d love to buy them, but there’s no way I’d pay the asking price. At least generic TLDs break that stalemate for a lot of folks.
Here in Germany most (German) websites use .de, so its definetly not unprofessional here.
I am also not surprised that .de is one of the most used country TLDs out there.
It’s certainly become normalized. And it was good to open up the TLDs for various purposes. 😊
To the people who are like “What did you expect to happen when you picked a .af domain, are you idiots?”
Yes, we were aware of the possibility of suspension from the start Yes, we were aware that political circumstances could change But thumbing your nose at conservative autocrats as an even minor form of protest is fun In the end pretty much everyone has migrated out successfully (and I’ll continue to help anyone who remains) We’ve all gotten a fun story out of this
I’ve been signalling the probable demise of queer.af to my followers for the past year. We knew the end was coming; we just anticipated it to take a little longer
So long; it was fun while it lasted.
💜
Similar thing happened with an instance I was on, it couldn’t be fixed and they had to start a new instance. Think the problem was federation related, you need every instance admin to change the domain manually in their instance
I was afraid of that. If this is common enough, i think it’s something the devs can introduce a feature for which would propagate such a change. Doubt it’s high on the totem of things to do, though.
deleted by creator
OP, this title is stupidly misleading and incorrect, you should change it immediately.
The Taliban seized the DOMAIN, aka the ownership of the
queer.afname that people could type into their browsers, and their system would resolve into an IP address.As the Taliban control
Afghanistan, (see where the domain comes from), this was inevitable and the instance owners were already planning to retire the instance as they didn’t want to give money to the Taliban to keep it up.The INSTANCE, aka the physical server, was not in Afghanistan, and still has its IP address(es), and so has had absolutely nothing happen to it.
Unfortunately, I think due to the way ActivityPub works, the domain name is inexorably tied to the instance. Trying to migrate to a new domain name would break a lot of federation to my understanding.
It looks like someone posted an attempt at a workaround here (latest reply): https://github.com/mastodon/mastodon/issues/5774
But it does require the
self-destructbutton because the old domain name has to be erased from other servers.Yep, the other workaround that’s elsewhere in this thread is to set up an entry with a different authoritative DNS in the hosts file, allowing a single machine to resolve the old domain manually.
This could be part of a greater effort, basically asking other instances to help the users evacuate the instance and transfer their accounts, before running
tootctl self-destructDoes federation involve some sort of key exchange? If not, would that mean that if one loses control of a domain somebody could spin up a new Lemmy instance to spoof the old one and potentially harvest data?
Not in ActivityPub no.
The main privacy/security issue is mostly mitigated by the fact that there’s a sync behavior for accounts and follows and distribution of content where the host can push revocation messages, triggering other servers to delete follows and wipe cached account data originating from that hosting server, which means that somebody who takes over a domain after a wipe can’t imitate the exact same accounts. But old links can still be redirected because there’s no way to verify what they were supposed to point to, so some degree of impersonation remains possible unless other servers agree to preemptively defederate…
Literally says domain in the title. Also says they seized the domain in the summary text below.
Ah, af for Afganastan not “as fuck”.
I suppose that depends on your point of view.
Any chance they rebrand to queerasfu.ck?
I think queer.fr would be an awesome domain name too
I mentioned on Mastodon the domain name “queersare.us” (parody of Toys R Us I guess) which actually makes use of the United States’ ccTLD that barely gets used. Someone pointed out to me exactly why that’s the case and it has something to do with scammers.
No, since profanities are generally frowned upon in serious website domains.
sh.itjust.works would like a word
That’s a subdomain. The registered domain is itjust.works which they clearly won’t care about.
Who is “they” though
QueerAsSu.ch doesn’t have the same ring to it, but they’ll be safe unless the gnomes of Zurich come for them.
how many times is this going to get posted
FWIW, this is the first time I’m reading this. I’ll allow it.
As many times as possible because it’s funny af
seizes your comment in taliban
Not exactly a surprise. It was known it will happen ahead of time: https://archive.is/EaSjE
I thought it already happened when I first saw that post. I’m surprised they didn’t try to figure something else out and kill it sooner.
I don’t think they could do anything about it. As far as I know, Mastodon doesn’t support any kind of instance renaming, so the hostname is one thing you cannot change. You can only spin up a completely new instance.
I thought they’d already shut down. Renaming isn’t an option, but you can at least direct your users to the new instance.
I figured they would have almost instantly gone read only and prepared the self destruction. But I guess they just closed off registration and set the self destruct pretty far out.
Who’s bright idea was it to integrate the domain name itself directly into the software such that changing the domain name totally fucks up the whole thing? Is there actually a good reason for this to not work like any other website where the domain name is just an address and changing it doesn’t actually have any effect other than requiring users to type in or bookmark a different URL?
Federation combined with keeping the historical federated data consistent is certainly a bitch. We can’t have it all. It could be like email that only handles delivery at any point in time and history is purely local, but Mastodon specifically keeps the federated data public. Propagating the change on the historical data to the federated instances would be nearly impossible. I don’t see how it could have been done better without sacrificing something else.
If only we could just tell everyone living in the dark ages they get no say in anything if their say is shitting on someone they don’t like.
We (via the ICANN, see below) actually have the power to do that. The.afTLD only works because the root DNS servers delegate the.afTLD to the Afghan nameservers. As soon as we stop doing that, they are powerless.And as a bonus, the ICANN could set the nameservers to OpenNIC’s, setting a precedent for a more public ownership of the Internet. But somehow I highly doubt they would ever do that…Edit: I did what I documented here to do, and here is the (automated) answer from the ICANN:
Dear [name],
Thank you for contacting ICANN Contractual Compliance.
Your complaint involved a domain name registered under a country code top-level domain.
Please note that ICANN has no contractual authority to address complaints involving country code top-level domains (ccTLDs), such as .us, .eu, .ac, or domain names registered under a ccTLD (e.g. example.us, example.eu, example.ac). ICANN does not accredit registrars or set policy for ccTLDs and has no contractual authority to take compliance action against ccTLD operators. For inquiries and issues involving ccTLDs, you may wish to contact the relevant ccTLD manager using the contact details at https://www.iana.org/domains/root/db. This page will also help you determine which top-level domains (TLDs) are country codes (outside of ICANNs scope) and which ones are generic (within ICANNs scope).
Please note that responses to closed cases are not monitored. Therefore, if you require future assistance or have any questions regarding this case that is being closed, please email compliance@icann.org. if you have a new complaint, please submit it at http://www.icann.org/resources/compliance/complaints.
ICANN is requesting your feedback on this closed complaint. Please complete this optional survey here.
Sincerely,
ICANN Contractual Compliance
Of course, the contact details at https://www.iana.org/domains/root/db/af.html are the Afghan ministry contact information, so this is a no go.
And the IANA being managed by the ICANN, aside from electing to use alternative DNS servers, there isn’t much we can do.
ICANN is going to become a UN agency before they kick out states as stakeholders. Their status, though, is not derived from that but by silent agreement from the ISPs handing out servers following ICANN’s root servers as default, they’d have to fuck up quite badly for that institutional inertia to change, and any replacement on that level is absolutely bound to respect ccTLDs as control over their own ccTLD is a national security issue for all states, and push come to shove they’d legislate that domestic ISPs have to hand out servers that respect at least their own ccTLD.
And there’s nothing wrong with that. Plenty of letter combinations to choose from especially now that there’s vanity domains. If this was the early 2000s e.g. lemmy.world would simply be lemmy.net.
ICANN is going to become a UN agency before they kick out states as stakeholders.
You seem to be absolutely right. The conduct of the Afghan registry goes square against the ICANN base registry agreement, yet they won’t do squat against ccTLDs, as evidenced per the email I received (see my edit).
Thank you for your comment.
I nearly broke my neck from the double take on that title lol.
As I was reading the title I was fully prepared to see one of the Republican states name in the end
I’m pretty sure none of them control registrars
US states don’t have registrars (four cities do however) and even .us is pretty much only used for domain hacks vs. a lot of TLDs that are actually used to identify country (which I’ve seen a few people criticize Americans over, but while I don’t think it had anything to do with privacy as much as Americans just getting used to everything being .com, I think that’s ultimately a good thing.)
How tf did they seize it? isn’t mastodon instance federated? don’t the admins own it?
Ultimately each country makes the rules for domains under its top level, for those that are named for the country, like .af for Afghanistan. Everything about the instance is intact and can be moved to a different domain.
@zoostation @i_have_no_enemies Indeed, choosing .af was a bad idea for a LGBT service. But there are other bad choices (people registering names under .social without reading the fine print, which says, among other things, that some lobbies can easily take down domain names)
https://www.eff.org/fr/node/96673yea found a fix by someone else as well
Stéphane Bortzmeyer @bortzmeyer@mastodon.gougere.fr
@GossiTheDog Since the authoritative name servers still reply; you can also ask the #DNS resolver administrator to forward requests for queer.af to kiki.bunny.net and coco.bunny.net.
did not know they can control domain names,
is it possible to deny them that request? why did maston comply with them?
It’s got nothing to do with Mastodon—it’s the domain name system. If DNS doesn’t direct the request to the intended server, the server never sees it.
That’s not how it works… the .af domain is reserved for use by Afganistan by ICANN and the government of Afganistan is the Taliban. Same with the commies on .ml which is reserved for Malaysia.
Everything else correct. But ml is actually Mali. my is Malaysia.
Dammit. The whole thing is basically absurd though because these letters mean fuckall in Afghanistan, Mali, and Malaysia and I think URLs can even have unicode now, though idk about tlds
To be fair, I didn’t know ml was Mali, I had to look that up. But I did know Malaysia was my, which was what prompted me to look ml up.
There are tons of tlds with arbritrary unicode characters
@i_have_no_enemies @zoostation Maston? You mean Mastodon? The software did not “comply”, it just issues regular DNS requets and the domain name servers for .af now reply NXDOMAIN (No Such Domain) for queer.af.
See https://catnip.article19.org/ (or @b0rk zines).@i_have_no_enemies @zoostation @b0rk By the way, there is a #DNS client on the fediverse, @DNSresolver See for instance https://mastodon.gougere.fr/@bortzmeyer/111919725507892158 to see a query and the answer.
Still have to buy/register a domain name, and I’m assuming in this case, it’s through a particular organization that doesn’t like that kind of stuff.
domain is centralized and subject to a state power.
is it possible to change that or any other workaround is available?
Doubt it. Top level domains by country code were created explicitly for this purpose… for use by and to be managed by the corresponding state.
Wikipedia rabbit hole:
OpenNic have been trying to fix it for a long time, but only people who use their DNS servers can access their domains.
I use their DNS servers on philosophical grounds, but I have literally never come across someone using one of their exclusive domain names.
From what I understand, their own domains are not actually decentralized. Each of them has it’s own “authority” that can control what is or is not allowed to be registered. Emercoin domains look more promising, but I am not knowledgeable enough about them to say that they are actually decentralized. I would say that the closest thing to fediverse is DNS system in I2P, there different DNS providers federate with each other and share their records.
There are some projects to create decentralized DNS systems, but almost no one uses them, so if you try to use them than you limit amount of your potential users drastically.
it will be useful for websites that are intentionally made to be accessible to a small minority
@i_have_no_enemies Almost every Internet activity start with a #DNS request. So, DNS is often (ab)used for political goals.
Also, domain names are organized in a tree so if you control a domain (in that case .af), you also control all names underneath.
There are social networks that don’t rely on the DNS but they have other issues. In the mean time, take DNS seriously and choose your domain name with care.
