SilberWitch on Nostr: This is the part nobody gets. Nostr clients are defined as software interfaces that ...
This is the part nobody gets.
Nostr clients are defined as software interfaces that sign notes and read/write to relays. That's why my CLI is a client, even though it resides on the same Linux laptop as my relay, and can only be used over the terminal. Where clients reside or run (phone, remote server, local browser, cloud, desktop, refrigerator, etc.) isn't what decides that they are clients.
Nostr is, fundamentally, a client-server architecture, with the relay functioning as server (event store) and the client simply displaying what the relay sends it, according to the user's settings.
Placing an _additional_ server _between_ the client and the relay, is a fundamental change to the architecture. You can do that, perhaps because you want to curate or park the data, but as we can now see in real-time, many of their users didn't know they were doing that. It isn't immediately obvious.
Nostr clients are defined as software interfaces that sign notes and read/write to relays. That's why my CLI is a client, even though it resides on the same Linux laptop as my relay, and can only be used over the terminal. Where clients reside or run (phone, remote server, local browser, cloud, desktop, refrigerator, etc.) isn't what decides that they are clients.
Nostr is, fundamentally, a client-server architecture, with the relay functioning as server (event store) and the client simply displaying what the relay sends it, according to the user's settings.
Placing an _additional_ server _between_ the client and the relay, is a fundamental change to the architecture. You can do that, perhaps because you want to curate or park the data, but as we can now see in real-time, many of their users didn't know they were doing that. It isn't immediately obvious.