Embed Notice

@arcanicanis

>Maybe a public key-based identifier for a ‘activity/actor storage server’?

I'm proposing DID URLs for IDs. Take a look at section named "Server independent IDs" in FEP-ae97.

For example, if actor ID is

did🔑z6MkrJVnaZkeFzdQyMZu1cgjg7k1pZZ6pvBQ7XJPt4swbTQ2

(just a public key), then we can construct object IDs in the following way:

Resolution process:

1. Resolve did🔑z6Mkr... to actor object.
1.1. If you already know this actor, look it up in database.
1.2. If you don't know this actor, use ?hosts= hint, look it up on specified servers
1.3. If there's no hint, try to request object from some popular server (mastodon.social?) or from an indexer service
2. Actor object should contain an up-to-date list of servers where data is replicated.
3. Resolve DID URL to object
3.1. If you already know this object, look it up in database
3.2. If you don't know this object, look it up on servers associated with an actor

Other types of DIDs will require a different resolution algorithm.