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???

IDK, but registrars are generally shitty and exploitative. I'd be surprised if they volunteered that info

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.

Only instances with a ".ml" at the end of the name may or may not be affected. Lemmy is a collection of instances so the loss of a few will not cripple the whole thing. Content over the whole is not greatly affected.

If your home log-in instance is one that's affected, you'll have to find a new one. You'll know right away because the instance will be unreachable. Not a big deal, last time I looked there was over 1200 instances to chose from.

Another consideration is any communities living on an affected instance may have issues. All communities are common to Lemmy, but each originates from a particular instance. We've not yet seen a major instance go down so I don't know how Lemmy deals with communities getting orphaned like that.