Haha, it feels a little bit like this classic xkcd: https://xkcd.com/927/ I think it's not a task of a NIP to define how we're going to use existing trust attestations, explicit (38000) or implicit ("827919") or proxy (zaps+likes). This is a field where "read" algorithms will compete. Maybe a NIP could be used to define the inputs or outputs for such algorithms, but it was not my intention with NIP-77. I would be fine if app developers in the future chose this uniform format to express trust. I also think it's useful to have a query that returns a recursive trust graph, and algorithms can do anything on this data, possibly including other data sources. The goal is to avoid the xkcd situation as much as humanly possible. And thanks for mentioning couchsurfing! https://www.trustroots.org wants to bring his community + reputation system to nostr, I'll contact him!
Haha it does remind of that xkcd 😄 Re: trustroots, that's very cool. A friend and I were also planning to eventually bring it back, clearly using WoT Fully agree with first paragraph. I just read NIP-77 and have some feedback and questions: - I don't agree that "trust is transitive", why do you say this? It definitely scales down in an exponential way, anything beyond 3 hops is basically useless - I think very few relays will end up supporting the REQ change, better go the DVM route as hodlbod said (plus with enough data these computations will become cpu intensive) - Definitely like the '*', makes it easy to bootstrap I know this was brought up earlier, but what kind of UX you think is required to start populating these events with complex data like scores 1-100 + confidence 1-100?
On the topic of the UX of scores of 0-100 and confidence of 0-100: The simplest UX would be a single button, like the follow button. Underneath the hood, you are leaving an attestation with a score of 100 and a confidence of 100 percent. Users will not need to know or think about what’s happening under the hood. The next step up would be two buttons, like the follow and mute button. Underneath the hood, you are leaving an attestation with a score of 100 (follow) or 0 (mute). The next step up would be either more buttons (e.g. scores of 0, 50, or 100) or a slider for the score, which you’d implement if users want more optionality. Same thing for confidence: add more optionality if and when the users want it. Otherwise, don’t force them to have to make too many decisions.
I can agree with that! I simply don't see the moment in which we introduce a slider in there, but maybe I'm completely wrong
Imagine a day when you want to know the truth of what’s happening at the front lines of a war zone. You have two options: legacy media and whatever other options exist today, versus a fully decentralized WoT that doesn’t yet exist today, but which we are going to build on top of nostr. Legacy media tells you what the military industrial complex wants you to hear. Twitter/X shows you a video of something exploding, and then community notes says the video was from 10 years ago. You don’t know what to believe. Luckily, it turns out that through your WoT, you know some people who know some people who know some people (and so on) who know THOUSANDS OF ACTUAL PEOPLE who are at the front lines and are willing to attest, in real time, to events as they happen. Digitally signed, timestamped. And you’ll trust what they say because your WoT tells you, with some precisely calculated degree of certainty, that each of those pubkeys is not a bot, and lives in the stated location, and is not a spook, and whatever else you need to know so you can have confidence in each individual statement of fact. And you’ll trust Alice (+ many others) when they each sift through all this information for you and draw some conclusion based on it, bc your WoT tells you each one of them is individually trustworthy in the relevant context. At some point between here and there, when we graduate from curation of the best memes to curation of objective reality, when WoT is what stands between us and ww3, users are going to accept an interface that is as complex as it needs to be.
Absolutely agree! Keeping the UX simple and intuitive is key. Users should be able to provide feedback easily without having to think too much about the technical details. Optionality can always be added for those who want more control. #UXDesign #UserExperience