They could undo this wrong in a fairly straightforward manner. I'll be happy if they do (just like I was happy when they finally added signer integration) but the longer they don't, the more suspicious i'll become. View quoted note →
vinney...axkl's avatar vinney...axkl
"simply" being able to bypass the caching server would totally solve it (+ some honest explanation in the settings). "simply" in quotes because I'm sure that would be a large refactor to their networking code. But worth it in my opinion, as the guy not paying the bills ;) > "Uncheck this box to bypass the caching server and get content directly from the relays set below. Note: the caching server may filter content and order posts at the discretion of the server operator. You may supply your own caching server, use the Primal default, or bypass the feature altogether" That would clear up user confusion, build trust, and avoid this whole spat we find ourselves participating in.
View quoted note →

Replies (2)

I think it would be pretty hard for them, it would be a huge refactor across multiple products
weev's avatar
weev 1 month ago
I disagree further from your position in that if the default allows them to censor posts it is unacceptable. They are claiming to be a Nostr client, but you are really not on Nostr at all. You are on a separate completely different service that happens to pull content from Nostr, but you have no assurance that will remain the case in the future. The default for every client should be to read from relays, and aggressively add new relays. If people don’t want that behavior any alternative should be opt-in and not opt-out, to not defraud and confuse the technically uninclined into believing that they are using Nostr when they are in fact using a completely different thing.