Thread

🛡️
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

Replies (22)

I agree. The 'primal problem' was not front and center in my mind, until yesterday i tried out their search for a bunch of things and got suspicious as to how on earth it could possibly work. I asked some jungle dweller just to check, and he confirmed my suspicions. What is most confusing is that when you listen to them talk they say all the right things. If the idea is to do the right thing 'eventually', then when will that eventually be? Its now right? Right?
🛡️
↩ replying to Constant
I think also it’s important to differentiate between now and the vision. You might do things now in a certain way until you figure out how to do it in a better way. For example, Primal may understand that the caching relay is not a good idea, but it’s a temporary patch until they figure out things. Who knows what other people think. But it’s good to give people the benefit of the doubt.
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!
jb55's avatar jb55
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 →
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.
ใครใช้ primal รู้ตัวไว้ด้วย
jb55's avatar jb55
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 →