😎 how many active users? do you fulfill limit-less subscriptions fully (i.e. all of history?)
Discussion
I’ve been thinking relays should be able to redirect clients to download older (and compressed) event data from “firehose” subscriptions (i.e. [.., {}]) from a different url/endpoint — which could then be cdn cached etc.
I have a hard cap at 900, which I bump against. And yes, you can get the entire event stream with a subscription, there are no limits other than what the client requests.
Do you see a lot of limit-less firehose queries? I’ve been thinking about auto-limiting users/clients that request the same big query repeatedly.
Lots of queries for 5000 events (with limit), not too many that return 10k+. But lots of repetitive ones that just eat bandwidth. I have some simple protections, but could use more.
Consider implementing this, please! I'd love to not limit "tier 1" users at the expense of limiting random accounts when server hits its limits.
#[5]