this post was submitted on 28 Jul 2026
89 points (100.0% liked)

Fediverse

43240 readers
92 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, Mbin, 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)

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] fubarx@lemmy.world 6 points 4 days ago

The whole thing about moving from centralized to decentralized had a core glitch. Whatever server you signed on would effectively lock you in. What happened if things didn't go as planned? LOLA is a good step, but it's still not enough.

Long time ago, URNs were designed to handle URLs that moved. These were permanent resource indicators that would allow the underlying data to move but not break the link. The HTTP redirect codes were supposed to help. Idea was, a website could redirect to a new location so clicking on a link would never get you a 404. It assumed both source and target site were still accessible so source could send the 301, 302, 307, or 308 codes. Very genteel. But what if the source site or account were zapped or suddenly blocked?

Redirect codes work if the owner moved them and has now set up a suggested next location. But it doesn't handle the negative reasons. Getting forcibly banned, site getting hacked, sites shutting down, owner not paying the bill (for economic, health, or political reasons), anything else that could render the content inaccessible. It's nice to add constructs to avoid getting account hacked. But what if owner is in jail, muffled, coerced, going through a tough personal stretch, or dead?

They still need to solve for real life and how shit happens.