But relays allow me to provide very long lists of pubkeys to...

Leo Wandersleb

npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6

hex

0308f5b0f5f22bceeff51fda26bb17dd86f6d5ece46f25aa40c5094444a2ada3

nevent

nevent1qqsqxz84kr6ly27wal63lk3xhvtamphk6hkwgme94fqv2z2ygj32mgcprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgsydl97xpj74udw0qg5vkfyujyjxd3l706jd0t0w0turp93d0vvung6ah679

Kind-1 (TextNote)

2026-02-21T18:40:14Z

↳ Reply to 3bf0c63f... (npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6)

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 t...

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 some people. Don't cater to that vanity metric. Let the influencers brag about their imaginary influence. Nostr as a protocol or its infrastructure shouldn't care about that. Relays should care that they get paid for the bits stored and forwarded. Nothing more.

By elevating the role of the relay I fear we get censorship on a per-relay basis and if client devs get lazy about handling spam from open relays, we might get relay concentration. I know it's not the end of the world as others can always make a more open relay so I'm not fighting your vision but I hope I can convince enough devs to make the alternative happen. Have a flag on requests to limit results to follows of follows so I don't need to upload 10k pubkeys with every request.

Client-side filtering as a secondary barrier does nothing if the relays use standard filter heuristics, blocking what I want not to be filtered.

Raw JSON

{
  "kind": 1,
  "id": "0308f5b0f5f22bceeff51fda26bb17dd86f6d5ece46f25aa40c5094444a2ada3",
  "pubkey": "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d",
  "created_at": 1771699214,
  "tags": [
    [
      "e",
      "bbb18519803ac7084915c3dcb3e8cc507664ca1d3633d09147ff3b8599fa19ad",
      "wss://relay.damus.io/",
      "root",
      "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d"
    ],
    [
      "e",
      "e3a89f529329b06ad89c7171ad467d1efc0b5eae8a44b0f6d720218f19196621",
      "wss://relay.primal.net/",
      "reply",
      "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
    ],
    [
      "p",
      "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
    ],
    [
      "client",
      "jumble"
    ]
  ],
  "content": "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.\n\nThe 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 some people. Don't cater to that vanity metric. Let the influencers brag about their imaginary influence. Nostr as a protocol or its infrastructure shouldn't care about that. Relays should care that they get paid for the bits stored and forwarded. Nothing more.\n\nBy elevating the role of the relay I fear we get censorship on a per-relay basis and if client devs get lazy about handling spam from open relays, we might get relay concentration. I know it's not the end of the world as others can always make a more open relay so I'm not fighting your vision but I hope I can convince enough devs to make the alternative happen. Have a flag on requests to limit results to follows of follows so I don't need to upload 10k pubkeys with every request.\n\nClient-side filtering as a secondary barrier does nothing if the relays use standard filter heuristics, blocking what I want not to be filtered.",
  "sig": "64282cf79615250572d95e17483658c692f4818b1da9fb483f3f654ce7c0573dfef40c503cbf9697b561a2442d72b6c0ee8cc848967318e6eddcefb5e7720270"
}