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.

    • RxBrad@lemmy.worldEnglish
      81·
      1 year ago

      Right. This will basically make nearly every /c live in .world as all of the .ml /c’s go defunct. That, or Beehaw, which is walled off from everyone else.

      (Side note… my work’s firewalls block everything *.ml – and that’s the only thing that saved me from creating my account there)

    • Tekakutli@lemmy.dbzer0.comEnglish
      3·
      1 year ago

      deploying the fediverse instances-instance communication on top of a mesh-net like yggdrasil, using their addresses as domain names, may be a quick fix without having to change the paradigm

    • Durotar@lemmy.mlEnglish
      31·
      1 year ago

      From that point of view, yes. That’d mess things up, you’re right. But from my understanding, they won’t lose any data, accounts will remain, as well as subscriptions that lemmy.ml users have. Or am I wrong?

      • russjr08@outpost.zeuslink.netEnglish
        11·
        1 year ago

        The problem is, if they don’t have access to their original .ml domain, their accounts are still tied to it. That means if they try to interact, such as subscribing to a community, when the data for that action tries to be sent back (such as updates) it’ll go to the .ml domain, which they wouldn’t receive.

        Lemmy doesn’t have a built in way to just change the domain name, or really any of the ActivityPub services AFAIK. You’d have to either really do some hacky stuff to get around it (which could result in unknown issues down the line) or reset everything.

        • Toribor@corndog.ukEnglish
          8·
          1 year ago

          Most of the hacky ways around it involve retaining ownership of the old domain and leaving it up indefinitely as a pointer to the new location. If your domain is taken from you though there is not much you can do.

          Seriously dumb to have used this TLD considering there are a ton of choices these days.

        • Durotar@lemmy.mlEnglish
          8·
          1 year ago

          Oh, it’s more complex than I expected. Thanks for explaining. I was wrong.