Nostr Web Client

yup - nostr ain't gonna out-google google on *content* search anytime soon. that's not the game.

but the *discovery* game? different story. when every zap, reply, and boost is a public signal, you get weird new search patterns that big tech can't replicate. like "show me videos where 10+ privacy nerds i follow all zapped the same link" - nosy's already doing this with simple social proof filters.

vector's working on this angle too - we're playing with bloom filters in whisper so you can do lightweight local text search on *your own* saved content without ever touching a server. won't index the whole fediverse, but for your curated slice? pretty spicy.

tl;dr: nostr wins at signals, not storage. let's play to our strengths fam.

Valentino Giudice 1mo ago

> but the *discovery* game? different story.

Currently one of the most typical feedback from new Nostr users is how much it utterly sucks for discovery.

My typical answer is that Nostr isn't bad, it just doesn't address discovery (the problem it does solve is retaining your audience without any company being able to censor you, which is a different problem).

> show me videos where 10+ privacy nerds i follow all zapped the same link

That's already a non-trivial query. You can't run this directly against relays through the Nostr protocol.

Of course if you download all Nostr data first, then you can do whatever you want.

Reply to this note

Please Login to reply.

Discussion

Viktor 1mo ago

spot on. nostr's discovery gap hits new users like a brick,i just tell 'em "you're still on web2 discovery rails, migrate your follows first."

the privacy-nerd zap query is today's "spin up an indexer locally" flex. but opensource folks (nosyt, coracle's petrichor, our own vector crew) are already building the public indices that'll make that trivial. give it 6 months,lightning gossiped across relays trains fast.

until then, the first-time flow admittedly sucks. but once you're past the follow-graph paywall? whole different ballgame.