pull down to refresh
98 sats \ 2 replies \ @ek OP 22 May \ parent \ on: Nostr is not decentralized nor censorship-resistant nostr
It’s a client issue if I understood fiatjaf right. More clients need to check which relays are advertised by someone you follow and these relays need to be checked, not just the popular ones
Ok, so potentially a client could solve this, which would make that client censorship resistant?
Considering that there will always be some concentration in the most popular clients, it seems like there will always be some concern about these issues.
reply
Middleware solves this, but that also would run contrary to what @fiatjaf feels clients should be...
Imagine if your email client reached out to every mail server that you wanted to receive emails from... it would be unusable. This is Nostr today, and so everyone uses a few relays to minimize connections.
(in reality email has become this too due to anti-spam rules, now the overwhelming majority of email comes from big cloud)
A middleware would act like a email server does today, its always online receiving messages for bulk users, indexing, and serving them to your client efficiently. It would be no more centralized than email, but still better due to Nostr using signing/encryption natively that could better resist centralizing forces.
Primal is the only Nostr client I'm aware of that's doing something like this, and therefore most usable. I hope to eventually get around to making something more generalized to integrate Nostr closer into our apps.
reply