505
lemmy.fmhy.ml is gone [update from the team] (very.bignutty.xyz)
submitted 3 years ago by to c/fediverse@lemmy.world
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
[–] 31 points 3 years ago (6 children)

Federation connections are by domain name, so .. it is a big deal

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 7 points 3 years 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)

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 3 years ago (3 children)

    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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 11 points 3 years ago (2 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 8 points 3 years 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.

  • permalink
  • fedilink
  • source
  • parent