Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://mitra.social/objects/018be452-4c49-7fa3-4783-521e1e2551eb">silverpill (silverpill@mitra.social)'s status on Sunday, 19-Nov-2023 06:25:59 JST</a><a href="https://mitra.social/users/silverpill" title="silverpill@mitra.social"><img src="https://gnusocial.jp/avatar/85321-48-20230105202807.webp" width="48" height="48" alt="silverpill" style="position: absolute; left: 0; top: 0;">silverpill</a><div><a href="https://were.social/objects/b816ee63-b9ff-43e5-9b9c-44fc70ad4179" rel="in-reply-to">in reply to</a><ul><li></ul></div></section><article><p><a href="https://were.social/users/arcanicanis">@arcanicanis</a></p><p>&gt;Maybe a public key-based identifier for a ‘activity/actor storage server’?</p><p>I'm proposing <a href="https://www.w3.org/TR/did-core/#did-url-syntax">DID URLs</a> for IDs. Take a look at section named <a href="https://codeberg.org/fediverse/fep/src/branch/main/fep/ae97/fep-ae97.md#server-independent-ids">"Server independent IDs"</a> in FEP-ae97.</p><p>For example, if actor ID is</p><p>did🔑z6MkrJVnaZkeFzdQyMZu1cgjg7k1pZZ6pvBQ7XJPt4swbTQ2</p><p>(just a public key), then we can construct object IDs in the following way:</p>did🔑z6MkrJVnaZkeFzdQyMZu1cgjg7k1pZZ6pvBQ7XJPt4swbTQ2/object/f66a006b-fe66-4ca6-9a4c-b292e33712ec
<p>Resolution process:</p><p>1.  Resolve did🔑z6Mkr... to actor object.<br>1.1. If you already know this actor, look it up in database.<br>1.2. If you don't know this actor, use ?hosts= hint, look it up on specified servers<br>1.3. If there's no hint, try to request object from some popular server (mastodon.social?) or from an indexer service<br>2.  Actor object should contain an up-to-date list of servers where data is replicated.<br>3.  Resolve DID URL to object<br>3.1. If you already know this object, look it up in database<br>3.2. If you don't know this object, look it up on servers associated with an actor</p><p>Other types of DIDs will require a different resolution algorithm.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/2347472#notice-4634692">In conversation</a><time datetime="2023-11-19T06:25:59+09:00" title="Sunday, 19-Nov-2023 06:25:59 JST">about a year ago</time> <span>from <span><a href="https://mitra.social/objects/018be452-4c49-7fa3-4783-521e1e2551eb" rel="external" title="Sent from mitra.social via ActivityPub">mitra.social</a></span></span><a href="https://mitra.social/objects/018be452-4c49-7fa3-4783-521e1e2551eb">permalink</a></footer></blockquote>

Corresponding Notice

Embed this notice
silverpill (silverpill@mitra.social)'s status on Sunday, 19-Nov-2023 06:25:59 JSTsilverpill
in reply to
- arcanicanis
@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:
did🔑z6MkrJVnaZkeFzdQyMZu1cgjg7k1pZZ6pvBQ7XJPt4swbTQ2/object/f66a006b-fe66-4ca6-9a4c-b292e33712ec
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.
In conversationabout a year ago from mitra.socialpermalink

Public

Embed Notice

HTML Code

Corresponding Notice