Are the clients still pulling the events from people I've muted and then suppressing them in the feed? That is not persistent. Ugh.
Discussion
Elaborate?
In your feed, they're still showing you people you've muted.
Or, by you or I muting someone, clients are suppressing that person in everyone else's feed?
The first.
Hmmm, not happening to me on Primal or Amethyst. Takes a minute to propagate a mute. But no problems here on that front.
The latter. Questionable.
When my phone battery runs down or my Internet is slow, I can see their posts. They just hang there.
Or they get downloaded and hidden.
Why am I being forced to spend bandwidth on downloading the posts of people I've muted? Literally downloading trolls and cryptospam.
Well, okay. Therefore, I can't see all of the posts from people I'm following and share relays with, so I guess that evens it out.
well, it's a very raw thing so far, and if there was a personal caching relay service you could skip all that and plug in custom filters and stuff... i started working on filters for strfry, was the first thing i did as far as nostr goes, then i got the replicatr job
I have the wine filter, but it doesn't consider mutes.
nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku Where are these clients typically filtering feeds?
Relay-side? Do they run a caching intermediary? Or fully app-side like nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl is alluding to?
yeah, relay-side
Well, in the query of the relay data. But they aren't always accounting for mutes.
well, idk how advanced the sprocket got, i just started it
I actually have no idea. 🤣 Just guessing.
They must be including mutes or I wouldn't see them?
nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h is the responsible party i believe, he didn't update me on how it progressed
hahah that is why it is called a Feed . . . gotta run your own lil local client beloved as a widget