/r/freemediaheckyeah (@FMHY)
very.bignutty.xyz
An update: - fmhy.ml is gone (https://fmhy.net is now up), due to the ongoing fiasco with mali government taking all their .ml domains back and also Freenom being sued by Meta - 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 https://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
    1·
    11 months 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.

  • Nix@merv.newsEnglish
    0·
    11 months ago

    Lemmy has had such a crazy month and a half. Insane growth, XSS injections, DDOS attacks, admin takeover, domain name seizures. What a wild ride

  • Square Singer@feddit.deEnglish
    0·
    11 months 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.eeEnglish
      1·
      11 months 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.mlEnglish
        1·
        11 months 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
      0·
      11 months 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
          1·
          11 months 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.

          • mrmanager@lemmy.todayEnglish
            1·
            11 months 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
          0·
          11 months 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
            1·
            11 months 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.

  • FlashPossum@fedia.io
    0·
    11 months ago

    Is Mali gov just removing all DNS records without warning?
    No respect for existing contracts, or at least some heads up a couple of months earlier.

    • 001100 010010@lemmy.dbzer0.comEnglish
      1·
      11 months ago

      Governments just love doing stuff whenever they can, because what are you gonna do? This is a country under a military junta, there is no legal process to get back the domain.

    • JshKlsn@lemmy.mlEnglish
      0·
      11 months ago

      Damn, lemmy.zip, eh? If that instance is public, I don’t see that being a good thing.

      Tons of businesses, people, etc, are all banning .zip and .mov TLDs for security purposes. I’ve personally banned all those domains from my network as well.

      Bold move.

        • JoeyJoeJoeJr@lemmy.mlEnglish
          1·
          11 months ago

          See https://youtu.be/GCVJsz7EODA and https://youtu.be/V82lHNsSPww

          There are a few problems, but I believe the biggest issue is that .zip and .mov are valid and common file extensions, and it’s common for people to write something like ‘example dot zip’ or ‘attachment dot mov’ in emails, tweets, etc. Things like email clients have features where they automatically convert text that looks like a web address into clickable links. So now, retroactively, all those emails etc suddenly have a link, where they used to just have text, and the domains that are equivalent to those previously benign file names are being purchased by nefarious actors to exploit people unaware of the issue.