Nostr Web Client

The Grapevine is definitely complicated under the hood, but there’s a certain minimum complexity that is needed if we really want it to fly, and the fact that one self-taught dev (me) can build a working proof of concept shows that it can be done.

Think of it like an airplane. There’s a certain minimum degree of complexity that needs to be achieved if we want it to fly. Web of trust is the same way. But it’s absolutely doable.

franzap 1y ago

A few questions:

- have you drafted or implemented any NIPs for attestations?

- have you considered non-hierarchical taxonomies?

- do you recognize a difference between automatic curation (which I think you're after) and trust hints for manual curation?

In the case of zap.store (it's an appstore, not a physical products store) users will *never* have applications auto-installed because their Grapevine told them it's okay. There's a concious decision during a manual approval of whether to install an application or not. A strong WoT is there to help transmit high signal.

To be honest with you, Tapestry sounds well thought out but I have a million things to do and can't dive deep into it. Have you thought of putting something simpler out there, and let dev feedback guide the design instead? (I guess something like nostr vs bluesky)

Reply to this note

Please Login to reply.

Discussion

david 1y ago

I’ve outlined a roadmap for incorporation of the Grapevine into any platform, like the zap.store, in a stepwise fashion which will allow devs to roll it out gradually. It’s gone through several drafts but the most concise draft is here:

https://github.com/wds4/tapestry-protocol/blob/main/guides/grapevineIncorporation/steps.md