This was in nostrudel but it's not a client issue, the relays reject the event I'm sending because of the size of the event
Which app?
nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8 recently applied a near term fix for this issue on damus.
https://github.com/damus-io/damus/issues/2194
If other apps are behaving the same way, maybe I should make this a #nostrability issue, and future test case for #nostrCI
Discussion
Thanks for that note! I think it makes sense to track how apps interact with relays on nostrability as well, as this affects the end user experience.
In this case queries are rejected, which seems like an unhappy path.
https://github.com/nostrability/nostrability/issues/41
nostr:npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx do relays advertise in some way current follow list max count limit? Do relays notify users, outside of the above error nostr:npub1ktt8phjnkfmfrsxrgqpztdjuxk3x6psf80xyray0l3c7pyrln49qhkyhz0 experienced on nostrudel?
cc nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
Relay implementations can expose this in their NIP-11 document
https://github.com/nostr-protocol/nips/blob/master/11.md#server-limitations
You can find this document by sending a HTTP request to the relay url with the "Accept" header set to "application/nostr+json". My relay uses strfry which doesn't expose that information unfortunately. You can test it by sending this curl request:
curl 'https://nostr.oxtr.dev' --header 'Accept: application/nostr+json'
🙏
Added to nostrability repo
already answered somewhat, but some relays reply in limitations property of NIP-11, and form this you can infer the max follows of a kind 3.