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.

  • syntax@unilem.orgEnglish
    41·
    1 year ago

    This is why we host our instance on a .org. Honestly another huge blow for Lemmy. It doesn’t really inspire confidence in the platform. Hopefully after enough time passes smaller instances like us and the bigger ones left will have help up a good track record to inspire confidence again.

    • ArcaneSlime@lemmy.dbzer0.comEnglish
      41·
      1 year ago

      This isn’t really that huge of a blow, it’s a learning curve sure but just because some people made dumb decisions on what TLD to use based on something they decided it means (and backtracked to say they chose it because it was free, I know) doesn’t mean federated platforms don’t work. Actually imo it points to the strength of federation that we can still be here using lemmy on our instances while they switch.

      All this really did was teach instance owners (who this might be their first experience hosting things too btw) that you have to use a TLD that is more stable like a .org, .com, .net, etc over a “free” one, and this is afaik the first instance of something like this happening, so honestly they didn’t have precedent to base this on before.

      • syntax@unilem.orgEnglish
        2·
        1 year ago

        By no means did i mean that federated platform’s wont work, far from it. Im more considering the reputational damage of the platform. For me all the .ml instances unresolvable. And it doesn’t look good when the “official” instance is lost. If i were an outsider considering moving to lemmy and i saw vlemmy disappear, lemmy world get hacked, and .ml loosing their domains id be pretty hesitant on making the switch. Thats where i sit for the moment. Lets all hope we can get a good track record going now.

      • gizzle@reddthat.comEnglish
        1·
        1 year ago

        Exactly, IMO this has nothing to do with lemmy itself and everything to do with dumbass domain names.

    • Poiar@sh.itjust.worksEnglish
      1·
      1 year ago

      Only one went down - most everyone else are still up.

      This is the opposite of a blow. It directly shows the resilience of the fediverse.

        • Poiar@sh.itjust.worksEnglish
          2·
          1 year ago

          This just shows how putting all eggs into one basket is a bad idea.

          Only the fewest of few instances should have used .ml - they should have spread out. This is the beauty of the fediverse when done as intended.

          The only drawback I see, is that people want to make instances bigger, scaling tall, when they should have been scaling wide + wanting to use the same odd TLD. We reap what we sow.