Skip Navigation

lemmy.fmhy.ml is gone

very.bignutty.xyz FREEMEDIAHECKYEAH (@FMHY)

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 do...

FREEMEDIAHECKYEAH (@FMHY)

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.

171 comments
  • Posting here for visibility as I guess most people on Lemmy are not on Firefish/Mastodon

  • Re-federation is probably possible. BUT! You're going to always have problems with older content. Case in point my federation error messages is at 2300. About half are failed requests on fmhy.ml.

    So for re-federation what's needed:

    1: Remote instances should unsubscribe all users from any fmhy groups. They're dead now. They can only announce that and hope they do. I reckon when their errors start ramping up (as I saw yesterday) they will be looking into why. Probably to help de-federate from the old URL
    2: The fmhy instance should unsubscribe all users from all remote groups but keep a note of the groups while identifying as fmhy.ml. Then once on a configuration for the new domain re-subscribe to each one. The first step should hopefully stop them trying (and failing) to federate new events to the old URL. The second step should trigger federation with the new one.
    3: They could be able to keep the DB. But I am not sure in what places the old domain might be stored in the DB and what would need fixing there. Also not sure if they'd need to regenerate keys. Not sure if they'll see the key was attached to the old domain and refuse to talk to the instance.

    Now what's going to be a problem? Well ALL the existing content out there has references to users on the old domain. It's VERY hard to fix that. Like every instance would need to fix their database. Not worth it. But, whenever someone likes/unlikes or comments or whatever a post made from fmhy.ml then there's a good chance a remote instance will queue up a retrieval of:

    1: User info about the poster/commentor/liker
    2: Missing comments/posts for a like/comment event

    And those will fail and error log. I don't think there's a way around that aside from editing the whole database on every instance. Again, IMO not worth it.

    Would be a nice federation feature if, provided you could identify with the correct private key, announce a domain change which would automatically trigger the above in federated instances, or at the very least some kind of internal redirect for outgoing messages.

  • Because this caught everyone by surprise or was there some indication that things would just continue business as usual? The registrar has known the contract ended since it was signed 10 years ago, I would figure this would have been accounted for.

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

  • Hello! I'm new to Lemmy, could someone break this down like I'm 5 and explain what it means for the people who were already on there?

    • It means anybody who will want to go to site lemmy.fmhy.ml will not load site and would think its down, maybe some will find out on google about it, some are already on multiple instances...

      Also all links to lemmy.fmhy.ml are dead/gone now.

      Btw the domain *.ml was free as i read, at least they could get some 1-5 USD domain name extension.

    • 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.

  • Thanks for that, was concerned about keeping my subscription to that community. Keep us posted and let us know where you end up so I can change over my community subscription.

    Anyway I think the lesson learned here is don't use free TLDs. Lemmy is not at all designed to deal with domain name changes.

  • I initially started on Lemmy.ml but decided to look for smaller instances. Not only just to be safe for stuff like this, but also to find a tighter community. I found an instance dedicated to the area I grew up around and have been really happy with that move.

171 comments