Federation is not the same as sovereignty
Mastodon is the flagship of the fediverse, and it deserves real respect. It proved that millions of people will use a decentralized social network when the experience is good enough. It runs on ActivityPub, a mature W3C standard, and it interoperates with a whole galaxy of software: Pleroma, Misskey, PeerTube, and more.
But federation and sovereignty are not the same thing. Mastodon decentralizes servers. Nostr decentralizes identity. That distinction sounds academic until the server your account lives on shuts down, changes its rules, or defederates from a community you care about. Then it becomes the most important thing about the network.
Your account lives on an instance
When you join Mastodon, you pick an instance: mastodon.social, fosstodon.org, some community server. Your handle is @you@that-instance. Your posts, your follows, and your login all live in that instance's database, administered by whoever runs it.
This has genuine virtues. A good admin curates a community, sets a culture, and moderates in a way that a global algorithm never could. Small instances feel like neighborhoods. That is a real strength, and I do not want to wave it away.
The cost is that your identity is a tenancy. The admin can suspend you, the instance can go bankrupt or simply burn out its volunteer operator, and your handle is only yours for as long as that server exists. Mastodon added account migration to soften this: you can move to a new instance and bring your followers with you. But your posts do not move: your history stays behind, and your identity string changes because the domain is baked into it. You are portable the way a phone number used to be portable only within one carrier.
In Nostr there is no instance. Your identity is a secp256k1 keypair that you generate yourself and that no server issues or can revoke. You post to relays, but you are not of any relay. Drop one relay, use another, use ten; your identity does not change, because it was never tied to a server in the first place. There is no admin who can suspend the account itself, because there is no account in the database sense. There is only a key and the signatures it produces.
Moderation and defederation
This is where the philosophies pull hardest in opposite directions.
Mastodon's moderation is a strength and a liability at once. Instance admins moderate their local timeline, and instances defederate from ones they consider toxic. When it works, a community keeps bad actors out without any central authority. When it goes wrong, you can be cut off from friends because your admin and their admin had a falling out: a decision made above your head that silently reshapes who you can even see. Defederation protects communities and fragments them in the same motion.
Nostr pushes moderation to the edges. Relays can refuse content, and clients can filter, mute, and apply shared block lists. No relay can erase you from the network, because you can always publish elsewhere and your followers can always find you by your key. The trade-off is the mirror image of Mastodon's: it is very hard to be silenced, and also harder to build the tightly-moderated neighborhood feel that a well-run instance provides. Nostr resists censorship by making moderation a client-side choice rather than a server-side gate.
| Aspect | Mastodon (ActivityPub) | Nostr |
|---|---|---|
| Identity | @user@instance, issued by a server |
Self-generated keypair |
| Account home | One instance's database | No home: a key plus relays |
| If your server dies | Followers migrate, posts are lost | Nothing happens: switch relays |
| Moderation | Instance admins + defederation | Client-side filters + relay policy |
| Suspension | Admin can suspend your account | No account to suspend |
| Data custody | Held by your instance | Held by relays you publish to |
Data custody
On Mastodon, your data is in your instance's care. That can be excellent (a conscientious admin who backs up diligently and respects your privacy) or it can be fragile, resting on one volunteer's spare-time server and monthly hosting bill. Either way, the custody is not yours. When instances shut down, and they regularly do, the archives usually go with them.
On Nostr, custody is more honest about its own limits. Your events are signed and self-authenticating, so anyone can verify them, but no relay promises to keep them. You publish to several relays and hope enough of them stay around. It is more resilient than a single instance and less guaranteed than a system designed around durable storage. Nostr removed the landlord but did not, on its own, give you a deed to the house.
Where Gozzip fits
Gozzip agrees with Nostr's core move: identity should be a key you own, not a tenancy a server grants. Start there, and the whole class of "my instance defederated / shut down / suspended me" problems simply does not arise. Your key is yours, and no operator stands between you and your own account.
Then Gozzip closes the gap that Nostr leaves open: the honest weakness in custody. Rather than hoping relays hold your history, your data lives on your social graph: the people you trust store your events through reciprocal pacts, and reads flow from your own device, to your contacts, to relays only as a fallback. It is the neighborhood feeling that Mastodon does well (your community actually holds your data), but without an admin who can lock the door, and without your identity dissolving when a server goes dark.
And because Gozzip is Nostr underneath, the fediverse is not a rival. Public posts bridge out to ActivityPub, so a Mastodon user can follow and reply to you across the boundary. You get portable identity, community-held storage, and interop with the network Mastodon already built: keys instead of tenancy, friends instead of a server, and a door only you hold the key to.
