I really like the general idea of decentralized identity. Personally I'd prefer to keep my identities on different apps/platforms mostly (99%) separate. It seems to me that giving an adversary a map (especially usernames and email identities) of your online presence is a bad idea especially if they get access to one account and get some private details they may be able to use to socially engineer their way into other accounts.
Would the following be functionally equivalent?:<p>- on each platform, include your pgp key id in the "bio"/"about" of your profile<p>- in your pgp key, include your profile URLs on each platform as an identity.<p>(In DNS, CERT RR exists for this purpose already.)
An example user page is my page here:<p><a href="https://keyoxide.org/4af679d0aba0ed4b07bf7b6932ca3267c8d187d7" rel="nofollow">https://keyoxide.org/4af679d0aba0ed4b07bf7b6932ca3267c8d187d...</a><p>Keyoxide is a really nice, but difficult to set up, tool
There's also <a href="https://keys.pub/" rel="nofollow">https://keys.pub/</a> (from someone ex-Keybase, if I remember correctly). I haven't looked at either closely. Can anyone compare and contrast?
> Of course, one could opt for full anonymity! In which case, keep these properties as separated as possible.<p>I really like the fact that they don't dismiss people that want to do things differently and don't need/want what they offer.
On the one hand, I like this idea.<p>On the other hand, I prefer to avoid linking identities, especially in a publicly visible way.<p>I see how it's useful for those that do!
And now there is an Android app for it: <a href="https://blog.keyoxide.org/now-on-android/" rel="nofollow">https://blog.keyoxide.org/now-on-android/</a>
Decentralized identity is a pie in the sky to me. It sounds great but when you really start to think about what identity is, it’s formed by your relationships and connections.<p>Tools like this may be useful in some instances but auth will always tend towards centralization