Client-side algorithms are not the same as protocol-level algorithms.
You don’t like an algo a client implements use a different client, the protocol is agnostic of this and stays the same.
nostr:note1ztzrwhq0f40l84qwlqwv4qq9d792lnykh9rphnzf7355xaknmzaqdgdqyd
100%. #FreePrimal
Don't like something in Nostr? Build your own tool or use a different one. Period. That's the value here.
The issue with primal is also that since the client is geting data from their "caching" backend service, they can (not saying they do) also censor anything, not only trending. Until they don't give the option of not using their caching backend and get data from relays directly there is space for disagreement.
I, personally, see no evil in this. Nostr, the protocol, does not censor anybody and users content is discoverable in a multitude of ways regardless of what a particular client does.
