Would also be useful for defining who can see public versus private notes, when encrypted notes and accounts are developed.
Perhaps they could be DMed a key-half, or something.
nostr:npub1manlnflyzyjhgh970t8mmngrdytcp3jrmaa66u846ggg7t20cgqqvyn9tn nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240 nostr:npub1nu9m6k6dca28f9humvq0ad334a3czu0qrevw0pd4ml2pzaumx0mqyr3ars
We need an "inner web" layer to WoT. We could call them "trustees". 🤔
Discussion
Interesting, how would those encrypted notes work? Conceptually I could imagine encrypting a note for 1-of-N multisig, where N is the number of trusted recipients. Probably tricky to implement.
I've never developed an encryption scheme, before, so I don't know how it works. I just know that it works because people use shared keys, split keys, and distributed keys, in other systems.
We could also make all notes encrypted by default and allow for some accounts or notes to "go public" as an option. Probably easier than the other way around.
A public square with default encryption would be next-level because npubs could publish notes on any relay, but define precisely who can read them.
Could make a client where the note is confirmed after “are you sure you want to post this?” “To what audience?” Etc…
“You can’t delete this shit after ARE YOU SURE” ?
😂💯
So many warnings the first one being “This client is wayyy too annoying for shitposting, go do that somewhere else trust me 👈🏻😜"
😂
Pop under windows randomly to move along to the next step
Hey, but fr.
Why not have an installer that helps you setup your client or relay and suggests different default-settings, depending upon the user's preferences?
Kind of like Alby just did for their extension?
Yeah lay choices and consequences out in layman’s terms, give examples that are easy to understand, easy to adjust the settings, occasional check ups on tuning, compile your own data privately, train your own algorithm over time?
And you could have a "visibility setting"
1) Profile and all notes public.
2) Profile public and all notes private. Request for invitations allowed. Individual notes can be made public.
3) Profile and all notes private. Invitation only.
Or something.
It's an interesting concept for sure. I think it's also easy to go overboard with it though, discoverability could really plummet if it's encrypted by default (and most people don't notice)
That's true, but you should probably at least prompt for privacy options during the setup routine.
