Nostr Web Client

I feel like perhaps we’re being quick to try and decentralise everything and store all config, data or state in published Nostr events by default 😟

The cross app support Nostr enables is awesome - but it comes with an insane privacy cost. Worse than todays social networks. Are we building something worse?

A public following list is fine. But I want a private one too. I want private lists. I want private block lists or mutes. I want private bookmarks. I want private connected relays. And so on.

The current client app approach is basically ‘give the government a direct event feed for everything you do or have, in a nice standardise format for them to process’.

We really need to rethink the public first mindset in Nostr clients. Most data can be synced using iCloud or something that’s not public - and made public by choice by the user as needed. You can even store the data as Nostr events locally without publishing if you like that format.

Let’s not build a privacy nightmare..

Lurking Cat 2y ago

Let's see...

Private mute: snort.social already implemented this along with public block list

Private bookmark: not yet but almost, CMIIW, Nostros implement public bookmark in latest release

Private relay: if you refer to only whitelisted can read and write (not like current paid relay who allow read by everyone) then NIP-42 possible to achieve that

Reply to this note

Please Login to reply.

Discussion

Lurking Cat 2y ago

For the privacy issue, i think it has became secondary issue since the inception. Because, at first, nostr design is mainly focused on censorship-resistance protocol.

"The simplest open protocol that is able to create a censorship-resistant global "social" network once and for all." - Nostr Github

But, truly agree that privacy issue should also be addressed properly. :)