Great article. To make sure I'm clear, are you envisioning nostr users rating other users? If so, have you seen nostr:npub1arkn0xxxll4llgy9qxkrncn3vc4l69s0dz8ef3zadykcwe7ax3dqrrh43w's QTS system for scoring products? I'm extending that in a project now for ranking places. Would you use kind 1986 for reviewing users or would you use another NIP?

Reply to this note

Please Login to reply.

Discussion

Glad you liked it! To answer your questions: yes I do envision nostr users rating other users. The linked is an article with screenshots from my proof of concept app, where users rate other users as trustworthy or not in the context of curating a specific list of interest. It doesn’t implement the entire tapestry protocol, just the very early stages of it. The next step in the protocol will be to curate a graph of categories associated with each list. I have not yet built a proof of concept for the graph, but the methodology will be pretty similar as for simple lists.

https://github.com/wds4/pretty-good/blob/main/appDescriptions/curatedLists/overview.md

I haven’t seen the QTS system but I’ll take a look. I’m using kinds 39901 and 9901 as per the part of the tapestry protocol which interfaces with nostr. The article I linked to shows examples with technical details.

The tapestry protocol is technically independent of whatever network is used to store and send data. I was building it on top of IPFS before nostr was born, but technically you could use either or both at the same time. I think nostr is the best place for me to start. There is a section of the tapestry protocol that describes how to interface with nostr, but I have a stub for IPFS and anyone could add a section for whatever other network they might want to use.