Starting today, the service I run, https://npm-stat.com/, receives 403 Forbidden errors when calling the download-counts API (see pvorb/npm-stat.com#57). It looks like you are blocking my site from doing calls to api.npmjs.org.
Can you tell me, if there's a way around this? If you want to get in touch with me, we can either discuss solutions here or in private (paul@vorba.ch).
As you might understand, I'm interested in keeping this service running as it's visited by at least one thousand users each day. The service does each request for a package's download counts at most once per day and persists the numbers in TimescaleDB. But the way you designed your API, I have to do that one request per package, if some counts are missing in the database.
If my site puts too much pressure on your API, maybe there is a way around this by providing a daily dump or something like that, that I can pull once? Just a suggestion, but you have my understanding if that's nothing that'll get much priority.
Starting today, the service I run, https://npm-stat.com/, receives
403 Forbidden
errors when calling the download-counts API (see pvorb/npm-stat.com#57). It looks like you are blocking my site from doing calls to api.npmjs.org.Can you tell me, if there's a way around this? If you want to get in touch with me, we can either discuss solutions here or in private (paul@vorba.ch).
As you might understand, I'm interested in keeping this service running as it's visited by at least one thousand users each day. The service does each request for a package's download counts at most once per day and persists the numbers in TimescaleDB. But the way you designed your API, I have to do that one request per package, if some counts are missing in the database.
If my site puts too much pressure on your API, maybe there is a way around this by providing a daily dump or something like that, that I can pull once? Just a suggestion, but you have my understanding if that's nothing that'll get much priority.
Here's the exact error page I see:
Thank you!