this post was submitted on 21 Jul 2023
59 points (95.4% liked)

Fediverse

27828 readers
264 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to !moderators@lemmy.world!

Rules

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy

founded 1 year ago
MODERATORS
 

Can't post images because they're too big so here's imgur: https://imgur.com/a/Fm52ZTB

Edit: lemmy.ml and lemmy.world seem to have come back, I'm just a bit worried that it's another one of those hacks.

you are viewing a single comment's thread
view the rest of the comments
[–] kid2908@lemmynsfw.com 11 points 1 year ago

And it seem to getting worse for lemmy fmhy

https://very.bignutty.xyz/notes/9hg4dquksvbha67h

  • All services, except Lemmy, is up and running again via the new domain: https://fmhy.net
  • Lemmy itself will require a significant database cleanup to get users transferred, posts and communities may not be possible
  • Cleanup will have to be done either manually or with a custom script

And now to answer some common questions I've seen floating around:

  • Why is lemmy.ml not affected? WE DON'T KNOW. My assumption is that it's popular (or lucky enough) to not be affected by this change. The only difference between our two domains is that lemmy.ml doesn't use CF, and AFAIK, multiple other domains (with and without cf) are still unreachable.
  • Why can't you just change the domain? That's not how federation works. Most services (including Mastodon and Lemmy) do not support changing URL properly, as doing so could potentially break the whole network.
  • Why is it taking so long to get back up? Not all staff members have access to the server, CF, or domain registrar. Not to mention that this is a complicated task that requires a lot of effort, and one that we didn't even know we had to do until the following morning. (We were under the assumption that the .ml TLD didn't just explode.)