I don't think WoT needs a NIP, this is something clients can do differently without hurting interoperability.
nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn
Checkout my imagination of WOT user experience:
nostr:note1za8gapacw9l2r6eqxljpx478r8vgfsd3uxe3qkh7k424sc9nekssyevl7p
… in your scenario “mute” wd act as a “trustworthy down vote”, wherein if enough of your followers “muted jameson” then he MAY cease to be marked as “trustworthy” (for you) and you MAY be notified (depending on your WOT filter settings) of this change.
IMHO, “WOT filter” needs to be its own NIP, to provide a protocol for other NIP filters and a definition for consistent client UX.
Thoughts?
Discussion
No replies yet.