WebSockets have an upper limit AFAIK, I'll have to check what it is but a single REQ can't be bigger than that
nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxthwden5te0dp38ytnrdaexzcmvv5h8xmmrd9skctcfh8d3u nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpz9mhxue69uhkummnw3ezuamfdejj7qgswaehxw309ahx7um5wghx6mmd9uag6jvy nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75sprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0nvx4fv
Do you guys know of any upward limit on the size of filters? E.g. how many pub keys can I reference in one filter? I’ve never hit any limits before just curious if you all have see anything.
Discussion
Websocket request limit in node defaults to 1GB, but most server implementations limit to something like 1-16MB. All of which would still work for very large filters. I'm just wondering if anyone has direct experiences with relays blocking for a REQ that was too large.