(#3rhsaxa) so in effect it would look something like this: ``` --- subject: acct:me@sour.is aliases: - salty:me@sour.is - yarn:xuu@ev.sour.is - status:xuu@chaos.social - mailto:me@sour.is --- subject: salty:me@sour.is aliases: - acct:me@sour.is links: - rel: self type: application/json+salty href: https://ev.sour.is/inbox/01GAEMKXYJ4857JQP1MJGD61Z5 properties: "http://salty.im/ns/nick": xuu "http://salty.im/ns/display": Jon Lundy "http://salty.im/ns/pubkey": kex140fwaena9t0mrgnjeare5zuknmmvl0vc7agqy5yr938vusxfh9ys34vd2p --- subject: yarn:xuu@ev.sour.is links: - rel: https://txt.sour.is/user/xuu properties: "https://sour.is/rel/redirect": https://txt.sour.is/.well-known/webfinger?resource=acct%3Axuu%40txt.sour.is --- subject: status:xuu@chaos.social links: - rel: http://joinmastodon.org#xuu%40chaos.social properties: "https://sour.is/rel/redirect": https://chaos.social/.well-known/webfinger?resource=acct%3Axuu%40chaos.social --- subject: mailto:me@sour.is ... ```

(#3rhsaxa) @prologic Unfortunately the RFC's are a bit light in this regard. While it makes mention of different kinds of accounts like mailto: or status services.. it never combines them. It does make mention of using redirects to forward a request to other webfingers to provide additional detail. I am kinda partial to using salty:acct:me@sour.is, yarn:acct:xuu@txt.sour.is, mailto:me@sour.is that could redirect to a specific service. and a parent account acct:me@sour.is that would reference them in some way. either in properties or aliases.

(#3rhsaxa) @xuu Hmmm

(#3rhsaxa) @prologic That was exactly my thought at first too. but what do we put as the `rel` for salty account? since it is decentralized we dont have a set URL for machines to key off. so for example take the standard response from okta: ``` # http GET https://example.okta.com/.well-known/webfinger resource==acct:bob { "links": [ { "href": "https://example.okta.com/sso/idps/OKTA?login_hint=bob#", "properties": { "okta:idp:type": "OKTA" }, "rel": "http://openid.net/specs/connect/1.0/issuer", "titles": { "und": "example" } } ], "subject": "acct:bob" } ``` It gives one link that follows the OpenID login. So the details are specific to the subject `acct:bob`. Mastodons response: ``` { "subject": "acct:xuu@chaos.social", "aliases": [ "https://chaos.social/@xuu", "https://chaos.social/users/xuu" ], "links": [ { "rel": "http://webfinger.net/rel/profile-page", "type": "text/html", "href": "https://chaos.social/@xuu" }, { "rel": "self", "type": "application/activity+json", "href": "https://chaos.social/users/xuu" }, { "rel": "http://ostatus.org/schema/1.0/subscribe" } ] } ``` it supplies a profile page and a `self` which are both specific to that account.

(#3rhsaxa) @prologic Unfortunately the RFC's are a bit light in this regard. While it makes mention of different kinds of accounts like mailto: or status services.. it never combines them. It does make mention of using redirects to forward a request to other webfingers to provide additional detail. I am kinda partial to using salty:acct:me@sour.is, yarn:acct:xuu@txt.sour.is, mailto:me@sour.is that could redirect to a specific service. and a parent account acct:me@sour.is that would reference them in some way. either in properties or aliases.