Instead of ActivityPub objects all having an absolute URL, they should have a relative URL, that is based on the originating actor.

That would implicitly make each actor it's own namespace (in the sense that DNS is a namespace), and allow easy(-ier) movement of actors between federated instances, by greatly decreasing potential URL breakage.

It could also lead to increased compatibility with future p2p uses of ActivityPub.

@doenietzomoeilijk instances are run on volunteer basis, so they're already non-permanent in the sense that any instance in the network can die at any point.
Building a network that requires everything to stay online perpetually makes the network fragile IMO, so I think we should rather design so that we allow some degree of non-permanence.

Follow

@doenietzomoeilijk in other words: I don't know? Can we make it work with non-permanent URLs?

Sign in to participate in the conversation
Manowar.social

Private mastodon server run by Zatnosk