Nostr Web Client

The protocol I am using is divided into two main sections: the concept graph, which describes how information is represented, and the grapevine, which describes how it is curated. The concept graph describes how to ask a question and the grapevine describes how your WoT answers it.

Ultimately, this protocol will be encoded using the concept graph and managed by your grapevine. Your grapevine is going to manage the protocol and the code that allows your grapevine to exist! Gonna take a long time to get there but it will happen. But even before we reach that point, we’ll be able to build some useful platforms.

david 1y ago

Imagine a nostr apps page that enables your grapevine to manage a list of nostr apps, a hierarchy of categories of apps, and assigns each app to the appropriate category(ies).

Imagine a Wikipedia where you pick the ppl who pick the ppl who pick the ppl who manage the articles.

Imagine Yelp where your WoT weeds out fake reviews. Imagine being able to pay a few sats for reviews from trusted sources, thus incentivizing users to enter high quality info into the system (bc when ppl see low quality info, the WoT will decrease their trust score in that context).

Imagine legacy social media minus all the bots, scammers and trolls, with better ability to find the content you want.

Every legacy platform will be rebuilt. And your identity and all associated information will be portable.

Reply to this note

Discussion