Fediverse

28723 readers

123 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]

506

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

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

177 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] 1 points 1 year ago (1 children)

I got curious so I start digging into how mastodon do it. It's more like a hack, really. Mastodon uses WebFinger to resolve user account, so when you change domain, you can leave the old domain up so your federated servers can still resolve your users and realized the domain has been changed and update their federation data. But it turns out you can't exactly retire the old domain either because it's still tied to user account internally. So if you lose control of your old domain, you're probably as screwed as fmhy.ml.

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

Yeah, which is why I think storing remote user and instance public keys might be better. Then that can be used to authenticate the migration request (it'd probably need to be an extension to the activitypub standard).

The biggest problem I see is that an instance doesn't know about all the instances that have data pointing to them. So how does it communicate the changes to everyone? The mastadon way is probably the sensible way to do it, despite not supporting the loss of control of domain scenario.