FREEMEDIAHECKYEAH (@FMHY)
very.bignutty.xyz
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.

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.

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

    • @[email protected]
      30•1 year ago

      Not really. Most centralized services are accessible via multiple domains, e.g. for different countries. This would just disable one of them, but users could still use another to log into their accounts. For the Fediverse it “disables” an entire instance, cuts it off from federation and locks out users.

      Lets not put a positive spin on a situation that exposes a weakness of the current system. The federation protocol needs to be able to handle these things gracefully, like propagating domain changes and migrating accounts between instances!

      • @[email protected]
        7•1 year ago

        I’m now wondering what happens if the Mali government (or someone else) begins using those domains with their own lemmy instance, potentially with malicious content.

        Would the instances they’ve federated with begin ingesting and serving that content automatically? Or would that be blocked due to key mismatch?

        • @[email protected]
          6•1 year ago

          Afaik it is all connected to the domain name, so they could definitely start to impersonate any .ml instance. Other instances could detect that the signing key for federation messages changed, but that’s about it. Their admins would probably have to block/defederate them manually.

        • ඞmir
          6•1 year ago

          I think they need the private key for the https certificate to do that

    • @[email protected]
      10•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.

      • @[email protected]
        6•1 year ago

        I was frustrated with the outage yesterday and created a new account on a different instance so I could still browse. Couple hours later I had all my subscriptions filled out and the experience is almost identical to my first account.