No idea if this is feasible or not, but could the fediverse have an internal DNS-esque system where domain details could be updated to reflect communities moving?
Kinda,
So everything in the fediverse uses its https url as an id. To fetch the content after its been posted, a server needs the content to be live.
As a result, everything breaks when domains go down.
FEP-ef61 fixes this, by making objects portable, and making it possible for servers to request them from other servers.
No idea if this is feasible or not, but could the fediverse have an internal DNS-esque system where domain details could be updated to reflect communities moving?
Kinda, So everything in the fediverse uses its https url as an id. To fetch the content after its been posted, a server needs the content to be live.
As a result, everything breaks when domains go down.
FEP-ef61 fixes this, by making objects portable, and making it possible for servers to request them from other servers.
https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md
This isn’t implemented by anything major yet unfortunately.
That’s awesome! Thanks for the info. Hopefully we can see something like this implemented in the near future.