[berkes]

Everything for this is in place. No changes or features outside of AP are needed.

Mastodon even has a simple key-value table that any profile can enable and fill with details such as "website: example.com", "twitter: @jack" and so on.

This feature already has "verifications". Meaning that you can add proof that example.com, keybase etc are really yours.

This could easily[1] be expanded to verify ownership of SMS, or messenger apps. Provided those apps have some form or authentication/proof in place.

I have this on our roadmap for our "fediverse linkedin" project (another story for another time) so would gladly offer help here; keybase with my contact details in my hn profile.

-- [1] It would be easy after a refactoring. The code handling this in Mastodon is not ugly persé, but rather unfortunate. Tightly coupled to the God-Model "User" (which seems to happen with every rails project at some point) and spread over some json-store, model and unrelated controllers.

[cjslep]

Oops, I think I misunderstood what I was replying to. I see what you mean.

I'm more interested in exploring getting the entire AP ecosystem be encrypted by default, using Chris' work.

I don't think I care that much about profile deep-linking to other apps. I would rather obsolete that need.

[sneak]

Encrypting data meant to be public to the whole web doesn’t make much sense to me.