@Gargron I‘ve been seeing “error: too many requests” a lot in the last several days myself. I suspect it might be that I’ve been playing with a lot of clients and maybe too many are refreshing often enough that I got rate limited.

Would love to see these limits increase! I think they’re all authenticated requests too.

@Gargron @gruber just to step in here, I'm guessing the issue is that Per IP rate limit. If that could be per OAuth token it'd probably be hit a lot less often. As of now its kind of easy to hit if you are running clients on multiple devices + have a lot of push notifications (which is another issue that I owe you some details on).

@Gargron @gruber Mastodon.social already amounts to what, 20-30% of the accounts on the network? Wouldn't that be the perfect opportunity for you to promote *other* instances to help spread things out a bit?

@Gargron @gruber another thing that would help is raising the per-request results returned, specially for /api/v1/notifications, 30 per batch is way too low for some accounts.

@Gargron @gruber even I, with my tiny account, did hit the rate limiter when exploring/searching other accounts

@Gargron @gruber definitively very easy to replicate when using a few clients simultaneously. My quick and dirty fix is just to increase the limit (and decrease the timeout) on my own instance for authenticated calls.

@Gargron @gruber Eugen, this is the rate limits that I am facing.
https://mastodon.social/@eshwarnag/109747214491867939