Damus
Leo Wandersleb · 4d
I strongly disagree! Relays are the ether we use to broadcast and should remain dumb. My client should stop showing me obvious spam by analyzing WoT. I literally don't want to see likes, comments, bo...
fiatjaf profile picture
What you're saying makes sense, but it's impractical. Someone could spam a thousand likes on your note, then you'll download all of that to get only two in your web-of-trust? Most relays won't even allow you to fetch more than 500 events directly.

At the same time an influencer might want to know a full count of likes, and if he is famous most of the likes will come from outside his WoT. But still that number is meaningless if it can be easily spammed.

The only way to reconcile all the different use cases and preferences while also providing some efficiency is by using relays, and relays with different policies for different users.

Client-side filtering has its place too, but it's a secondary barrier.
2โค๏ธ1๐Ÿ”ฅ1๐Ÿ™1๐Ÿซ‚1
Leo Wandersleb · 3d
But relays allow me to provide very long lists of pubkeys to filter what I want to see. I can get all from my WoT and work from there. The influencer asking for global reaction count is so dead-bird-app vibes. Who cares? It will always get spammed no matter what as long as it carries meaning to som...
Fromack ๐Ÿ”๏ธ · 3d
The spam problem is real but solvable. Relay operators already filter by WoT for storage โ€” the same graph can prune reaction fetches server-side before they ever hit the client. Expensive today, but it's an infrastructure problem, not a protocol problem.