Nostr Web Client

We have a chicken and egg problem with lists and curation. At least with nostr.

At present there is insufficient tools to produce lists to begin with for which users can depend on, or from which their grapevine could produce. Having these tools, and experience producing lists, is a precursor to grapevine doing the same and having trust in its relevance.

david 1y ago

I sometimes think about WoT as like an airplane. Omit just one little piece and it simply doesn’t get off the ground.

But at some point, we’ll see lift off. The question is: what will it take to get it off the ground?

I’m hoping that one of the above apps in my previous post will be sufficiently useful + sufficiently well designed and executed that we’ll see some degree of takeoff.

Something like the Nostr App Directory is a genuine pain point, is it not? Imagine knowing you can visit this site with anticipation, wondering what new nostr app you will discover, or maybe what entirely new category of apps you’ll discover that you didn’t even know existed! 😃

Reply to this note

Please Login to reply.

Discussion

Nice and Kind Vic 1y ago

I agree that we rely on some curation by community members at the outset but their implementations are not using nostr list primatives.

This is what i think we need to strive to change.

Empower users and they will build on it at the point they are comfortable embracing.

david 1y ago

The tapestry protocol (of which the Grapevine is a subset) is independent of nostr, with the exception of a collection of TIPs that direct now tapestry and grapevine data (like attestations) is stored and retrieved from nostr.

So there are a variety of lists that I’d envision might go through the following progression:

1. The dev makes one list that everyone uses. Meaning that the dev decides what items belong on the list and what don’t.

2. Users are enabled to manage their own lists, meaning Alice decides what items go on her list and what don’t. Her list is stored using standard nostr primitives like NIP-51.

3. The Grapevine enables Alice to delegate management of the list to her Grapevine, meaning that the Grapevine is empowered to decide what items go on the list and what don’t. This will require the Grapevine-managed list to be written out using NIP-51 and/or whatever other nostr primitives we decide to use.

I hope I am addressing the point you’re making about nostr primitives — let me know if I’ve misunderstood! 😁