i know, this would be nice and will happen eventually.. nip11 no love tho?. we barely use it 😂 im looking at some now, there is a max_filters: and apparently i set it to 256. this is informational only, i know the relay goes to ~1000 and will adjust 😎 but y no one use this?
That's my issue with nip-11... It's all informational. So most relays have it wrong. We can't rely on it to make decisions. We need to turn this into core protocol features to get the to be widely used and pushing the relay operator (by having less queries) if they are not in sync.
so if relays change one little tag, and any client actually uses it.. thats how these things get adopted right? its in the spec for nip11 already.. the thing is, even once i add dynamic limits nip, it will still be these informational values just transmitted different.
Yeah, if they just copy paste it, then it's the same thing. But my hope was to make clients always comply with limits for their own benefit and because of that if the relay's limits are wrong the client will use less of that relay, which will make things disappear for users pissing off a lot of people and hopefully fixing the limits of the relay.