Unfortunately what seems to be the cached version of lemmy.fmhy.ml is now slowly disappearing from Cloudflare. Those 2 comments have now been lost as well along with most of the content.
Not a (permanent) solution, just a very (very, very,…) stupid idea, that I am not even sure would work.
What happened? They don’t own the domains anymore, the DNS records were removed so those domains don’t resolve to anything. But maybe they could be locally resolved by each instance. I added these entries to my /etc/hosts file when the DNS records were deleted:
This allowed me access to FMHY (while it was still up).
Even if this worked, why would it be stupid? Well it would have to be manually set by each instance. And those IP addresses may change from time to time, so it would have to be manually updated again, by every instance.
This doesn’t solve the main problem thought, in which the instance can no longer federate with other instance via activitypub. You can’t expect other instances to manually override their DNS in order to federate with fmhy again. Also, https will break as soon as their current certificate expires, at which point no instances can federate with fmhy even with dns override.
Hopefully this issue will force activitypub developers to rethink their approach with domain handling.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Not a (permanent) solution, just a very (very, very,…) stupid idea, that I am not even sure would work.
What happened? They don’t own the domains anymore, the DNS records were removed so those domains don’t resolve to anything. But maybe they could be locally resolved by each instance. I added these entries to my /etc/hosts file when the DNS records were deleted:
This allowed me access to FMHY (while it was still up).
Even if this worked, why would it be stupid? Well it would have to be manually set by each instance. And those IP addresses may change from time to time, so it would have to be manually updated again, by every instance.
A thanks for the IP addresses to dnshistory.org (fmhy.ml) and whoever wrote this comment: https://lemmy.fmhy.ml/comment/1231585 (lemmy.fmhy.ml)
This doesn’t solve the main problem thought, in which the instance can no longer federate with other instance via activitypub. You can’t expect other instances to manually override their DNS in order to federate with fmhy again. Also, https will break as soon as their current certificate expires, at which point no instances can federate with fmhy even with dns override.
Hopefully this issue will force activitypub developers to rethink their approach with domain handling.
They might have to implement a “domain change” thing like username change. It might be huge work