I will never understand why some relays limit filters in 12/subscription.. so low...
Discussion
Why do you need that many ? I think damus uses max like 6
Sometimes I do per user EOSEs, so you have to give a since field that is different for every user you are interested. In Notifications, we can display up to 50 users as a time. So, 50 filters for metadata since last time.
I limit the relay to 12-20 active subscriptions! more than that my android is slow
Tragedy of the commons comes to mind when I read these kinds of misdirected comments.
Relays are finite resources. The better question is why your specific algorithm needs that many. From that we can then have a conversation.
What's the difference in costs from 10 to 30 filters per sub?
Why not 300 filters?
Just because I don't think that is needed. 10 is just way to low for today's use cases.
The way the conversation should go is:
- I, Victor, have a particular use case for having more than 10 filters
- I find out relays have limits, let me contact relay devs to get those limits increased
- Relay devs hear you out and increase your limits
Instead we get this useless conversation and nobody is winning š„
I am not sure that works. First because I don't know which relays our users are trying to access. It's all one by one, after a lot of debug time. Quite impractical these days.
And second, relays are seeing that Amethyst hitting their rate limits all the time. So they already have that information. They shouldn't need me going there and make the life of their users better.
Btw, relays are getting hit no matter what. The app will send 10 filters, then the next 10, then the next 10 as soon as each receives an EOSE... So i don't think people are saving any costs by limiting to 10... It just takes longer to get everything.
āCosts savingsā is the wrong assumption here
12 subscriptions are too few. I set it to 50 on my relay, because it seems that some clients will use more subscriptions. If it is below this number, there will sometimes be an error message.
I thought you were talking about the number of subscriptions. I misunderstood.
But bigger number of subscriptions also help... I had to mix unrelated filters into given subscriptions just to avoid the 10 sub limit some relays have.
Have you seen Amethyst hitting your relay limits?
I think the different settings of each relay will indeed bring difficulties to the client. Similarly, relay operators also spend a lot of time to investigate and adjust in order to support different clients. I saw the problem of exceeding the limit before, but I just changed the settings, I havenāt seen what the client is.
Iām testing some clients on iOS now. I havenāt had time to see Amethests yet. Is the subscription ID a 4 character string? I noticed that the requests for this kind of subscription number are quite frequent.
How much would you recommend?
30 should be a good number these days, even for heavy clients like Amethyst
Iām keep banging up against this limit in Nos too.
