Fediverse

Somewhat related. Basically, the management of the .ml TLD are being handed back to Mali government, and they seem to revoking.ml domains left and right.

I suspect they're revoking registration for .ml domains that was registered for free. the company that originally managed .ml domains had a free domain offers where you could register any .ml domain for free, the caveat is you don't have the ownership right to that free domain. Maybe Mali government doesn't honor such free domain registration and wish to revoke them all.

They may not have taken the lemmy.ml domain back yet, but because the different instances are federated, you'll still be able to see contents from an instance that's gone.

lemmy.fmhy.ml is pirate friendly, lemmy.ml is not. Maybe the Mali government suddenly decided they don't like piracy because... reasons? Maybe the Somalian pirates pissed them off???

Not that easily, no. With ActivityPub your user ID is tied to the instance URL. If you subscribe to a community for example, when that community tries to "honor" your subscription by sending you updates of what is happening, it'll go to that .ml domain and be lost.

There's no official supported way to change your instance domain other than to start fresh. They might be able to do something hacky such as change all of the domains in the database and while locally that might appear to work, I don't know if it would work across the federation.

I do know on the instance I run, I accidentally broke the webserver config for one of the ActivityPub endpoints and the result was that when I sent out comments, it never actually got federated / published yet I can still see them from my instance. New subscriptions also didn't work. It was as if I effectively shadow-banned the instance by accident.

This isn't really that huge of a blow, it's a learning curve sure but just because some people made dumb decisions on what TLD to use based on something they decided it means (and backtracked to say they chose it because it was free, I know) doesn't mean federated platforms don't work. Actually imo it points to the strength of federation that we can still be here using lemmy on our instances while they switch.

All this really did was teach instance owners (who this might be their first experience hosting things too btw) that you have to use a TLD that is more stable like a .org, .com, .net, etc over a "free" one, and this is afaik the first instance of something like this happening, so honestly they didn't have precedent to base this on before.