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.

  • Treczoks@lemmy.worldEnglish
    71·
    1 year ago

    But they only took the domain name, not the server? So it should be no issue to just get another domain, change a bit of config on the system and web server, and be up and running in no time?

    • russjr08@outpost.zeuslink.netEnglish
      9·
      1 year ago

      Not that easily, no. With ActivityPub your user ID is tied to the instance URL. If you subscribe to a community for example, when that community tries to “honor” your subscription by sending you updates of what is happening, it’ll go to that .ml domain and be lost.

      There’s no official supported way to change your instance domain other than to start fresh. They might be able to do something hacky such as change all of the domains in the database and while locally that might appear to work, I don’t know if it would work across the federation.

      I do know on the instance I run, I accidentally broke the webserver config for one of the ActivityPub endpoints and the result was that when I sent out comments, it never actually got federated / published yet I can still see them from my instance. New subscriptions also didn’t work. It was as if I effectively shadow-banned the instance by accident.