Avatar
ManiMe
df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200
I will never give up respecting everybody. Nostr Dev. Creative. Athlete. Optimist. Freedom lover. Know nothing nobody. Discovering myself. A little GFY is good for you. Sovereign Online Since 810018. Building WoT powered Nostr apps : - My Grapevine (https://grapevine.my) Webs of Trust recommendation engine (WIP) - Meet Me On Nostr (https://nostrmeet.me) Webs of Trust powered onboarding (WIP)

Entergalactic 🎬

Wait … that my purpose too!!

nostr:note144rh9g2rwery0rzqqtqc03ehqur8gszujj2gu0qkt3rqh9pa0y8svpvnku

Yea but which one is the BEST nostr?

nostr:note12pg73rljmun5cuecu7dvwap5e6duuln389xmdqns87ey48d4h3fsntnf2d

nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 I’m not sure you been paying attention to my posts… but this is what I am developing. Right now.

https://nostrmeet.me

(I’ve been yaking on and on about how nostr needs “web of trust” to combat bots and bad actors, and how “social onboarding” will ensure new users get “plugged in” right away.)

I’ll DM you a link to first alpha pre-release.

♥️

Replying to Avatar ManiMe

nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn throws the hammer down.

nostr:note1au93c9fk9fujtslt9d88u0mxzqunkawnc2af4wlv5tuazyt4kmps44ywhy

>”this is something clients can do differently without hurting interoperability.”

Please say more, because I actually disagree. But I may be off my rocker, so a bit of conversation will help…

nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn throws the hammer down.

nostr:note1au93c9fk9fujtslt9d88u0mxzqunkawnc2af4wlv5tuazyt4kmps44ywhy

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?

> “$user.getProfile() does NOT return a profile.”

Priceless.

Replying to Avatar rabble

Uh nostr:npub1manlnflyzyjhgh970t8mmngrdytcp3jrmaa66u846ggg7t20cgqqvyn9tn, TrustNet is a decentralized subjective WoT system. The numbers only make sense from the perspective of one user towards the network of their contacts.

nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 nostr:npub1xdtducdnjerex88gkg2qk2atsdlqsyxqaag4h05jmcpyspqt30wscmntxy

Here is a simple idea that could incorporate TrustNet and other WOT filter implementations.

As per my rant above, I believe a “parent NIP” that defines an consistent UX and API (of sorts) for WOT filters (in clients) would be the best choice moving fwd. here’s a “top view” of how that could play out:

nostr:note1za8gapacw9l2r6eqxljpx478r8vgfsd3uxe3qkh7k424sc9nekssyevl7p

Imagine with me…

nostr:note1za8gapacw9l2r6eqxljpx478r8vgfsd3uxe3qkh7k424sc9nekssyevl7p

🤣

nostr:note1hla8u6gfck9sqwv9g8tqezwwuzd5lykugwrmfpwm3fqwewzzdkpqdrrsha