dpc on Nostr: The follows and bans are already a more or less explicit 'trust' and 'distrust' ...
The follows and bans are already a more or less explicit 'trust' and 'distrust' relationships published for others to consume, so in a way the primitives are implemented.
In `cargo-crev` a trust relationship had 3 levels: high, medium, low, so it was possible to differentiate between different level of interest and trust, and then in cases where there was mutual distrust between two people in a WoT, decide which one to side with (or ignore both). There were also explicit overrides. If someone in your WoT banned someone, and you disagreed, you could override it. The complexity of it doesn't give a best UX, but it's there.
There's also trust distance tracking, and I always wanted to add maximum flow analysis to prevent sibyl attacks creating many identities. But I'm not sure if this is useful for nostr.
Published at
2023-02-08 20:44:01Event JSON
{
"id": "613456351274605a584681748275bb29e8351c6bc6680303882868062aa643b1",
"pubkey": "274611b4728b0c40be1cf180d8f3427d7d3eebc55645d869a002e8b657f8cd61",
"created_at": 1675889041,
"kind": 1,
"tags": [
[
"e",
"0cd6821a46db47d9594753054889e1d9ce0459d5186183b8d340a4ee01a66d6d",
"",
"root"
],
[
"p",
"274611b4728b0c40be1cf180d8f3427d7d3eebc55645d869a002e8b657f8cd61"
]
],
"content": "The follows and bans are already a more or less explicit 'trust' and 'distrust' relationships published for others to consume, so in a way the primitives are implemented.\n\nIn `cargo-crev` a trust relationship had 3 levels: high, medium, low, so it was possible to differentiate between different level of interest and trust, and then in cases where there was mutual distrust between two people in a WoT, decide which one to side with (or ignore both). There were also explicit overrides. If someone in your WoT banned someone, and you disagreed, you could override it. The complexity of it doesn't give a best UX, but it's there.\n\nThere's also trust distance tracking, and I always wanted to add maximum flow analysis to prevent sibyl attacks creating many identities. But I'm not sure if this is useful for nostr. ",
"sig": "b47d608127140aa2a7a763e05c41ba777a746c232de23cc8dae66207726ae5632e1602f5fe703303b97e213b66553ec62b5bb91671f0b8adbb4ee38e579d15cc"
}