Fediverse

27910 readers

1 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to [email protected]!

Rules

Posts must be on topic.
Be respectful of others.
Cite the sources used for graphs and other statistics.
Follow the general Lemmy.world rules.

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 2 years ago

MODERATORS

[email protected]

489

lemmy.fmhy.ml is gone [update from the team] (very.bignutty.xyz)

submitted 1 year ago by [email protected] to c/[email protected]

178 comments fedilink hide all child comments

An update:

fmhy.ml is gone, due to the ongoing fiasco with mali government taking all their .ml domains back
As such, lemmy.fmhy.ml is also gone, we are currently exploring ways to refederate (or somehow restart federation entirely) without breaking anything substantial
We have backups, so don't worry about data loss (you can view them on other instances anyway)

Currently, we have fmhy.net and are exploring options to somehow migrate, thank you for your patience.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 9 points 1 year ago

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.