Nostr Web Client

The Bluesky team has an academic paper describing the protocol that’s a pretty good high level but somewhat technical overview. It includes how they see Bluesky compares to Secure Scuttlebutt, Nostr, Farcaster, and ActivityPub/Mastodon.

I think folks who are building Nostr apps or advocating for it in comparison to Bluesky would do well to read it to understand what they’re doing and how we’re different.

We should also write up one for Nostr.

https://arxiv.org/abs/2402.03239

tf 1y ago 💬 2

I'm not sure what they're getting at with their description of Nostr

"Communication (e.g. reply threads) is only possible between users who have at least one relay in common"

That's true of any client-server architecture no?

Reply to this note

Please Login to reply.

Discussion

tf 1y ago 💬 2

It sounds like they haven't heard of the outbox model

Also this isn't true

"there is no federation among relays"

The section seems a bit dated

PABLOF7z 1y ago

80% of nostr misunderstanding (particularly wrt scaling) comes from not understanding how something like outbox would work.

which is fucking retarded.

the “public square” use case of nostr basically implies (something like) outbox; it’s like saying nostr can’t work because people can’t do math that quickly since the spec doesn’t mention computers.

rabble 1y ago

We don’t document the relay federation stuff in the nips so it’s easy to understand why they’d miss it.

CarlSaganBitcoiner 1y ago

not necessarily, one good example is LN we don't need to have a direct route between us, the payment is transmitted to many nodes/users in a graph mode until reach me.. But it's done indirectly.