EU :
Our commitment to the fediverse is here to stay.
We are working on a solution to ensure our continued presence on your feeds, taking full advantage of Mastodon’s identity portability.
And we are even growing the team behind our Mastodon presence, increasing efforts to engage with your comments on our posts.
We are fully committed to being a real part of the conversation in the fediverse.
Interested in our next steps? Follow us as we take on this new chapter.
/me : 🤔
The fediverse really needs key-signed messages.
As long as accounts reside on one server it fails to accomplish its goals, IMO
The Fediverse’s main goal was to be a middle ground between completely centralized and completely decentralized networks, though… So I’d say it has accomplished its goal.
But wouldn‘t the public key need to be somewhere to? At some point down the line you will probably have to trust some server.
No, that’s not how that works.
Users can generate their own keys, and you know it’s the same user as long as they have the same key, even if they’re on different servers.
No certificate authority is required for this kind of use case.
It would be a simple enough feature to code on top of the existing Fediverse
Is there any benefit to it over nostr though? You’d have to link your public key to your account(s) and store a backup of your private key in addition to your regular login/password just to get a more fragmented and less seamless version of nostr. A lot of people already have issues figuring out how fediverse works with multiple instances and all… now they’d have multiple accounts with different credentials to keep track of on top of a meta login/password (pub/priv key). With nostr you only have 1 login/password (pub/priv key) to everything, it’s just long and you can’t change it. At least I think that’s how it works, I don’t really use twitter/nostr/mastodon type of sites.
