(#3rhsaxa) @xuu Yeah I see where you're coming from, and if your Salty IM address is on another domain entirely, then yeah... But if for example you have a Yarn and Salty account on the same domain, and both are for example xuu@sour.is -- I would fully expect to see them both as aliases with respective `rel`(s) no?

(#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 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) @xuu So... From a practical perspective, wouldn't it make sense to have related identifiers that are "related" to the subject? Hence `rel`? If I were a user, I would expect to lookup only `prologic@twtxt.net` to find both my Yarn and Salty accounts and ways to follow or message me as such.

Trying to wrap my head around webfinger.. my first thoughts about it were that a subject of acct:me@sour.is would have a listing of rel's for the different accounts that are related to me (ie. yarn, salty, twitter, mastodon, etc...) but maybe my thinking is at the wrong level.. that each of those accounts would be on a subject level and the rels are describing different aspects of that account. so i would have salty:acct:xuu@sour.is, twitter:acct:xuu, mastodon:acct:xuu@chaos.social, yarn:acct:xuu@ev.sour.is and then i could have a main acct:me@sour.is that links them together as aliases. I found okta will do something similar with its accounts to show as okta:acct:user@domain so maybe I am on to something?