Attached: 1 image
Queer.af mastodon instance has been shut down by the Taliban (not a joke, they seized the domain name).
https://akko.erincandescent.net/notice/AenoDMPN0SdVXSq9ZY
We (via the ICANN, see below) actually have the power to do that. The .af TLD only works because the root DNS servers delegate the .af TLD 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.
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).
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:
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.
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.