Bluesky vs Nostr: 8 differences that matter

Who holds your identity

On Nostr, your identity is a cryptographic key pair generated on your own device: a public key (npub) you share, and a private key (nsec) that is the account. No company issued it, so no company can reset it, seize it, or hand it to someone else. The flip side is stated plainly: there is no account recovery. Lose the nsec and the identity is gone forever — a feature for censorship resistance, a real responsibility for you. The keys guide covers how to store it safely.

On Bluesky, your identity is a DID (decentralized identifier) managed together with a Personal Data Store (PDS) — for most accounts today, one hosted by Bluesky. The DID design means you can keep your identity while changing handles or (in principle) providers, and your PDS can help you recover access. That is more forgiving — and it means an intermediary stays in the loop.

Portability: claims vs reality

Both protocols market data portability. The difference is how much of it exists today.

Nostr's portability is native. Your posts are signed events stored on several relays at once. Switching clients means importing your key — nothing else moves, because nothing is locked to a server. The honest caveat: relays make no promise to keep your old posts forever, so persistence depends on which relays you use.

Bluesky's portability is designed, and partly delivered. The AT Protocol was built for account migration, and the architecture allows self-hosted PDSes. In practice most accounts live on Bluesky-hosted infrastructure, and the network depends on a central Relay/Indexer — a bottleneck and a potential point of control until third-party federation matures.

The architecture, in one diagram each

Nostr is just clients and relays. Relays are interchangeable dumb stores; they do not talk to each other. Your client publishes to several and merges what it reads back:

┌────────┐      ┌─────────┐      ┌──────────┐
│  You   │─────►│ Relay 1 │◄─────│  Friend  │
│(client)│──┐   └─────────┘   ┌──│ (client) │
└────────┘  │   ┌─────────┐   │  └──────────┘
            └──►│ Relay 2 │◄──┘
                └─────────┘
  Dumb relays. No federation. Clients aggregate.

Bluesky stores your data in a PDS, and a central Relay/Indexer run by Bluesky aggregates every PDS into one searchable network view:

┌────────┐   ┌───────────────────┐   ┌────────┐
│  You   │──►│   Relay/Indexer   │◄──│ Friend │
│ (app)  │   │  (run by Bluesky) │   │ (app)  │
└────────┘   └─────────┬─────────┘   └────────┘
                       │ aggregates
        ┌───────┐  ┌───┴───┐  ┌───────┐
        │ PDS A │  │ PDS B │  │ PDS C │
        └───────┘  └───────┘  └───────┘
  Your data in a PDS; one central index reads it all.

Moderation & getting banned

Nostr pushes moderation to the edges: each relay sets its own policy, and your client filters what you see. If a relay drops you, you publish through others — annoying, not fatal. The trade-off is equally real: spam is harder to fight, and curation is largely on you.

Bluesky moderates where the network converges: Bluesky PBC can act at the relay/indexer level. That gives better spam control and a calmer default feed — and it means the open network, as most people experience it, relies on Bluesky's goodwill.

Sign-up & privacy

Joining Nostr means generating keys — locally, in seconds. No email, no phone number, no form. You are pseudonymous by default. Two honest caveats: normal posts are public, and metadata (which relays you use, when you post) can be analyzed.

Joining Bluesky means creating an account with Bluesky PBC (or another PDS host). It works like signing up for any modern platform, and the company hosting your PDS has access to your data.

Money

Nostr has payments in its bloodstream: zaps are Bitcoin Lightning tips attached to posts, sent person-to-person with no platform taking a cut. You do not need Bitcoin to read or post — zaps are optional — but if you create things people like, value can flow to you directly. The zaps guide explains how.

Bluesky has nothing comparable built in. Payments simply are not part of the protocol.

What Bluesky does better

An honest comparison cuts both ways. Bluesky is genuinely ahead on:

• Onboarding. Sign-up and the first day feel like the Twitter you remember. Nostr asks you to understand keys first.
• Discovery and search. A central index gives fast, consistent, network-wide search. Nostr has no global view, so finding people takes more effort.
• Custom feeds. A marketplace of algorithmic feeds you can switch between is a real product innovation.
• Professional infrastructure. A funded team, uptime, caching, apps that rarely break. Much of Nostr is volunteer-built and it shows at the edges.

The 8 differences at a glance

Can I use both?

Yes — and it is the pragmatic answer. The networks do not connect, but nothing stops you from holding a Bluesky account for reach and familiarity while keeping a Nostr identity that belongs only to you. Many people treat them as different tools: Bluesky for the mainstream conversation, Nostr for the account nobody can take away and for Lightning-native tipping.