FWIW, I hate to see people having to create multiple identities as a bit of a hurdle to engage with #Fediverse in those different ways.
If I want my Fediverse identity to post both a microblogging message and Pixelfed type content, it stinks to have to wrangle between split identities instead of having it all tied to one.
I BELIEVE #ActivityPub has the capability to support single identities across services, though I don't know if it's ever really been implemented.
But I really hope development of programs like #Mastodon go in that direction so that someday, sooner rather than later, a person can present a single identity that crosses between services.
@volkris @david Agreed it's not ideal. I feel like I've heard about efforts to develop decentralized personal identity keychains, where you can lend your identity to a service without that service OWNING your identity, you own it. I don't recall what it's called or if it's ready for prime time yet. Identity as a service? I imagine it's complicated, as identifying oneself inevitably is.
On the topic of #Fediverse identity, I dipped my toe in for a second and came across an interesting thread.
#ActivityPub is the tip of a huge (and I'd say convoluted) iceberg, so it's hard for me to remember much of it at once.
Oversimplifying, identities are merely URIs, so a person could be credited for content across platforms by specifying the same URI on each post. Except...
I refreshed my memory on the protections against simply forging someone else's id by specifying their URI.
When a person is followed, their server/instance issues a certificate on their behalf, which causes other problems should the server lose the cert.
I suppose the next hoop to jump through, that I don't have time to dive into, is wondering whether the user could simply provide their person cert as they register on a new instance.
