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.

  • Square Singer@feddit.de
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 year ago

    WIll this also affect all other .ml domains? Or is this some anti-piracy thing? (I don’t know fmhy, but from the name I guess it’s about piracy.)

    • Falldamage@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I understand it as the Mali government is taking back all the domains after a subletting contract ran out. A lot of sensitive emails that should go to .mil (US military) has been typo-sent to .ml-addresses instead. Here’s some more reading.

      (I am very tired here and might have misunderstood everything, please correct me if I am wrong)

      • JshKlsn@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Perhaps the military should have a system in place to not allow emails to be sent outside of very specific TLDs if it’s that sensitive? And perhaps have an automated contact book, instead of relying on someone typing out the to: address manually to be able to make that mistake in the first place?

        Seems like some very basic security measures for something so serious.

    • sab@kbin.social
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      It seems to be Mali just wanting their domains back, in which case it’s uncertain times for all .ml domains.

        • sab@kbin.social
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          Good thing join-lemmy is safely tucked away in a .org domain.

          This is extremely bad timing for Lemmy (if it ends up happening), but also a good example of how federation makes the entire social media landscape more robust. Had this happened to a centralized service it would be devastating.

          • I_Has_A_Hat@lemmy.ml
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            If it was always going to happen, now isn’t really a bad time. Sure, a month ago would have been better, but people still haven’t been here that long. If I wind up needing to migrate, and lose my current account, oh well. No big loss. I imagine others feel similar.

          • mrmanager@lemmy.today
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            1 year ago

            The instance is known by its domain name in the federation network. If that domain name changes, it’s like starting a new instance from scratch.

            Sounds like a complicated project to migrate communities and posts and users to a new instance without breaking something.

        • sab@kbin.social
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Never hurts. Could be a good opportunity to look around the threadiverse and see if you find anything interesting.

          However, as it only affects the domain, I expect the Lemmy developers will manage to migrate user data to the new domain should lemmy.ml go down. So your account won’t just disappear, but it might go down for a while. It might also affect communities hosted on .ml domains, as followers from other instances will not have the correct path any more.