made a draft to extend nip56, would appreciate feedback or imrovements.

The logic is that clients can start off users with a whitelist of auto preview domains, but that kind of data can also exist on relays for other users/clients to make decisions from.

```

{

"kind": 10099,

"content": "",

"tags": [

["d", "domain_lists"], // identifier

["white", "nostr.build"],

["white", "void.cat"],

["black", "malicious-site.net"],

["black", "scam-domain.com"]

["unknown", "ask"] // Options: "load" | "block" | "ask"

]

}

```

https://github.com/limina1/nips/blob/extend56/56.md

Reply to this note

Please Login to reply.

Discussion

Interesting…

GrapeRank uses follows, mutes, and reports “out of the box” to generate a WoT network of “trustable” users for any pubkey. We got this. nostr:npub1u5njm6g5h5cpw4wy8xugu62e5s7f6fnysv0sj0z3a8rengt2zqhsxrldq3

GrapeRank’s design allows it to ingest data from any source and create contextual trust scores.

So if liminal’s kind 10099 notes catch on, we could use them to generate curated lists of whitelists and blacklists. In other words, a composite of 10099 notes authored by trusted pubkeys. It would be a simple enough matter to add this feature to grapevine-brainstorm.vercel.app which is currently in production.

Alternatively, these lists can be handled in the background by your personalized grapevine WoT relay, which is what I’m currently working on.

🍇🧠⚡️

I approve of this. It would make it quite easy to build automatic lists based on web of trust as well.

definitely the ideal solution. I'm much more ok with friends reporting media domains instead of pubkeys themselves which isn't effective anyways because they are often randomly generated.