Where are the people that were designing a full-on web of trust architecture on Nostr? They messaged me a couple of months ago but I cannot find them anywhere. I hope they didn't get discouraged from implementing it.

They had some cool ideas to individually declare levels of trust in Nostr. For instance, I would trust nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx to help me choose my hardware wallet, but not my vegetables.

We are getting to a point where that level of detail can actually be helpful.

Reply to this note

Please Login to reply.

Discussion

Definitely! This came up in Nests yesterday, there are people who I certainly trust for recommendations on who to follow, but not necessarily who to mute. And visa versa! Social networks are infinitely complex, and there are no easy answers here πŸ€”

I would like to know too. nostr:npub1avar8zfzwswhq9xh3t0gc5l38pf5kesrkqe2s2ymrnymv3ddl2ps38t7kg has been working on Notabot.net which is a specific kind of web-of-trust, but I don’t think that’s what you’re referring to. At Nos we talk about implementing TrustNet a lot, but it’s not in the short-term roadmap.

I think this can all be done with lists

I would absolutely like to know what vegetables he would recommend!

I bet he is going to recommend "beer" as a vegetable. :)

I'd wager a 10k zap that he's got some pretty good insight on food sovereignty of all types... (Even if he doesn't regularly eat kale salad)

I wagged my chin about this some but haven't gotten around to it yet. I don't think it's really possible without a server side component

What would the server do? Just summarize info from relays?

You could implement some of what you're talking about naively by inheriting moderation decisions from certain lists/pubkeys, but a more nuanced model with real social graph analysis becomes pretty computationally intensive pretty quick.

Can we do that as a service? Users subscribe to pub keys that provide the analysis and return a new Nostr event type to the app. We have a similar thing for Feed recommendations here: https://github.com/nostr-protocol/nips/pull/493

Yeah, I think so. Either that, or via custom relays.

I just did a pre release (v0.1.1-alpha) for pretty good apps. Desktop (currently mac and linux, but win forthcoming).

Anyone can make a list of hardware wallets or veggies or whatevs. Anyone can add items to any list. Anyone can endorse / reject any item on any list, and anyone can endorse / block any user as a trusted curator of that list.

For testnet, I’m using kind 9901 for lists and items; endorsements are kind 39901, parameterized replaceable events. Your app downloads data, crunches some numbers and says β€œhere is your crowdsourced list of Awesome Hardware Wallets: A, B, C …”

Curator trust is contextual, transitive and calculated in a PageRank-like fashion, so if Alice trusts Bob to curate wallets, Bob trusts you, and you trust Marty, then Marty will have influence over Alice’s list even if she doesn’t know who he is. Influence of unvetted users is set to a default which is usually low or zero to screen out sybil attacks, but can be adjusted if you’re not currently experiencing sybil attacks and want a more permissive system so you can get more input from more sources. There are several other parameters you can play with; as you adjust them, you can watch items pop on and off the list and hopefully get an intuitive feel for how the parameters work.

I welcome any feedback that anyone may have! πŸ™‚

(I meant to say Matt, not Marty, lol. But they both know wallets so they’d both probably end up in your hardware wallets web of trust!)