That’s a good hot take, but I don’t really oppose people wanting to build community silos, I just think there are better ways to do that without relying on “picking specific relays”, a true spof.
Basically, treating relays as cattle, not pets.
I think the real mechanism regarding “privacy” and siloing community media is AUTH. (I’m using quotes here because I honestly don’t believe any kind of real privacy exists on social media, even with encryption, but that’s a hot take of mine.)
nostr:nprofile1qy2hwumn8ghj7mnfv4kzumn0wd68yvfwvdhk6qgswaehxw309ahx7um5wgh8w6twv5q3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7qgkwaehxw309aex2mrp0yhxummnw3ezucnpdejqqg9fgd8wze0dqxegd0k0cfm3autst56n05z3kwrj3zycesqdtjy9hctgqjfy has torn my idea apart in a way I probably couldn’t have done myself (unfortunately, the discussion thread has fragmented because poll support on Nostr is terrible):
He’s right. Just like NIP-70, “protected” events are really just asking people to respect the original uploader's intent. In other words, marking media as protected is just a statement of intention; people can easily ignore or bypass it. Still, this can be useful for well-behaved Blossom implementations run by well-intentioned folks, i.e. those mirroring to genuinely help. Marking a blob as protected is simply a request for other responsible Blossom users, nothing more.
Discussion
No replies yet.