Relay devs and runners - do you limit massive filter subscriptions? Is it terrible to subscribe on a filter for kind 3 events for say 100,000 npubs?

Has anyone written a guide on relay filter etiquette? Or should I ask for what I need and if relays stop responding / block me, I submit smaller filters?

tagging a few folks that I know develop and run relays

#asknostr nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz

Reply to this note

Please Login to reply.

Discussion

Yes I limit too many tags, authors etc to relay

When I need to go through a massive list of npubs like that let's say for an import or archives or something, I will chunk it first

can't recall where I was discussing this with relay operators, tldr different relays will reject payloads above a certain size, and that anyway it makes no sense for a human to be following that many pubkeys. I don't think they'll block you

Strfry has a hardcoded filter size limit so that is the restriction you will encounter most commonly.

See discussion here: nostr:note1rpawm3yaaw3z74c43upfzpez48fy2w4vhqsqh6dxfmr0ac7pfgjs06jm4e

yeah, most sensible relays would reject such a filter; I long for the days of prefix-based REQs tbh

Yup, Nostream has limits for Numbers of authors on a REQ

if the pubkeys is too many, clients should split it into multiple requests.