(#3rhsaxa) @xuu Hmmm

(#3rhsaxa) @prologic that worked.. But took crazy long time

(#3rhsaxa) @prologic that worked.. But took crazy long time

(#3rhsaxa) @xuu I'm not so convinced of this "prefixing" here... We're sort of euplidating that extra bit of information anyway in the `rel`(s) -- Maybe @abucci is right and we stick to the spirit of the spec and an alias is just that, another identifier that is the same as this one. For example in `yarnd` we could add support in Settings for adding other "identities" that are the same as your, so a webfinger for `prologic@twtxt.net` _could_ also have `prologic@shortcircuit.net.au` and `james@mills.io` as aliases?

(#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) 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) @xuu that doesn't seem to fit the spirit of the spec, at least by my read (I could be wrong obv). The example on Wikipedia's webfinger page, ```json { "subject": "acct:bob@example.com", "aliases": [ "https://www.example.com/~bob/" ], "properties": { "http://example.com/ns/role": "employee" }, "links": [{ "rel": "http://webfinger.example/rel/profile-page", "href": "https://www.example.com/~bob/" }, { "rel": "http://webfinger.example/rel/businesscard", "href": "https://www.example.com/~bob/bob.vcf" } ] } ``` and then the comparison with how mastodon uses webfinger, ```json { "subject": "acct:Mastodon@mastodon.social", "aliases": [ "https://mastodon.social/@Mastodon", "https://mastodon.social/users/Mastodon" ], "links": [ { "rel": "http://webfinger.net/rel/profile-page", "type": "text/html", "href": "https://mastodon.social/@Mastodon" }, { "rel": "self", "type": "application/activity+json", "href": "https://mastodon.social/users/Mastodon" }, { "rel": "http://ostatus.org/schema/1.0/subscribe", "template": "https://mastodon.social/authorize_interaction?uri={uri}" } ] } ``` suggests to me you want to leave the `subject`/`acct` bit as is (don't add prefixes) and put extra information you care to include in the `links` section, where you're free to define the `rel` URIs however you see fit. The notion here is that webfinger is offering a mapping from an account name to additional information about that account, so if anything you'd use a `"subject": "acct:SALTY ACCOUNT_REPRESENTATION"` line in the JSON to achieve what you're saying if you don't want to do that via `links`.

(#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) @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) Moreover, what does the upstream spec have to say about this?