acct-URI like URI for content
⁂
We have acct-URI for referring to actors.
Ex: acct:[email protected]
We resolve this to an HTTP-URI using WebFinger.
⁂
We don't have an acct-URI like URI for referring to an actor's content.
Which would also be resolved with WebFinger.
Ex: obj:[email protected]/file.ext
⁂
I think there are many advantages to being able to refer to content separate from where it is stored.
2/
#acctURI has a way of representing user accounts on other hosts — sort of similar to the #fingerProtocol
For example —
acct:reiver%[email protected]
(Notice that the "@" in "[email protected]" gets percent-encoded as "%40".)
#WebFinger uses acct-URIs.
And the #Fediverse used WebFinger.
This is how you could represent a user on one Fediverse instance being used on another Fediverse instance without necessarily having to create a new account.
1/
Why can't I use my #Fediverse user account from one instance on other instances‽ Why do I have to create a new user account everywhere‽
For example, why can't I use ＠reiver＠mastodon.social on calckey.social ‽ Why do I have to create a new account on, for example, calckey.social ‽
I might not have to —
There are 2 technologies that the Fediverse uses (other than #ActivityPub ) that could make this possible — #acctURI & #webFinger
I'll explain —
A #URI type for #Ed25519 public-keys might be useful.
Maybe something like:
id:ed25519:hex.f034e38aae519cbf34c29a755f08b27ffb8175a9863405ebe572b18b65ec7fd9
(With a hexadecimal encoding.)
Which might be equivalent to
id:ed25519:b64.8DTjiq5RnL80wpp1Xwiyf_uBdamGNAXr5XKxi2Xsf9k
(With a base64url encoding.)
That way you could use it as a personal ID, in many contexts.
(I suppose this is a bit like the #acctURI )
@reiver ⊼ (Charles) 