we should stop calling clients that talk to a centralized server instead of relays a "nostr client". Otherwise this will lead to confusion when the app goes down and they think nostr is unreliable, which may irreversibly damage nostr's reputation.
if you make a web browser that doesn't fetch from websites directly and instead uses some centralized server to do this for you, you wouldn't call this a web browser.
gm
Thread
Login to reply
Replies (13)
who would have thought...
GM
GOOD WORDS. #PV
Directly reading from the relay network also provides some protection from censorship crackdowns by limiting a client's complete technical control as the sole host, curator, and deliverer of content, keeping it in the hands of users to decide what they can and want to see.
And if you run a centralized server, at least make it a native relay; this way you can comply while still protecting your users' freedoms.
Say NO to NINO!
we should stop calling clients that talk to a centralized server instead of relays a "nostr client". Otherwise this will lead to confusion when the app goes down and they think nostr is unreliable, which may irreversibly damage nostr's reputation.
if you make a web browser that doesn't fetch from websites directly and instead uses some centralized server to do this for you, you wouldn't call this a web browser.
gm
View quoted note →
Not going to lie, I assumed the primal caching service was an optional/nice-to-have that only sped things up. But just tested disabling it and it seemed to basically completely disabled the app 😕
TIL
View quoted note →
I think this is fair. I use nostr on my platform to enhance user experiences with non-technical folks on centralized algorithm apps but don't take the same responsibilities as a nostr client does with key management and other things.
Even on nostr I keep my claims fairly low.
by this logic, neither damus nor amethyst would be nostr clients as they talk to servers for upload/download media resources
the relabeling here is not wise
ใครใช้ primal รู้ตัวไว้ด้วย
we should stop calling clients that talk to a centralized server instead of relays a "nostr client". Otherwise this will lead to confusion when the app goes down and they think nostr is unreliable, which may irreversibly damage nostr's reputation.
if you make a web browser that doesn't fetch from websites directly and instead uses some centralized server to do this for you, you wouldn't call this a web browser.
gm
View quoted note →
NACK.
Common consensus is that a user-facing application interacting with one/many network/s is a client. A browser in contrast is a user-facing application showcasing a variety of clients/applications.
@npub12262...grkj warned folks a year ago and got hate for it
Sometimes the angry cat is right 🤫
actually most of times they’re right
It’s still a nostr client if it interacts with the nostr protocol, just not a good one…
Good nostr clients should give their users the option to interact with WHICHEVER server they want