November 28, 2024 at 1:56 PM
- Resume/CVs templates
- Trackers (budget, habit, etc)
- Automatization for business: via make or Zapier, or...
- Calculators (startup economy, cap tables, rates)
- Invoices/Billing management
- Recruitment & Interviewing
... etc
More details here ⬇️
- Trackers (budget, habit, etc)
- Automatization for business: via make or Zapier, or...
- Calculators (startup economy, cap tables, rates)
- Invoices/Billing management
- Recruitment & Interviewing
... etc
More details here ⬇️
November 26, 2024 at 8:24 PM
- Resume/CVs templates
- Trackers (budget, habit, etc)
- Automatization for business: via make or Zapier, or...
- Calculators (startup economy, cap tables, rates)
- Invoices/Billing management
- Recruitment & Interviewing
... etc
More details here ⬇️
- Trackers (budget, habit, etc)
- Automatization for business: via make or Zapier, or...
- Calculators (startup economy, cap tables, rates)
- Invoices/Billing management
- Recruitment & Interviewing
... etc
More details here ⬇️
So I set up rotating proxies on webshare (use any other you prefer) to be able to send any number of requests from multiple geo-distributed IPs
It works way better now!
429 error has gone.
It works way better now!
429 error has gone.
November 25, 2024 at 10:42 AM
So I set up rotating proxies on webshare (use any other you prefer) to be able to send any number of requests from multiple geo-distributed IPs
It works way better now!
429 error has gone.
It works way better now!
429 error has gone.
First, I added delays between requests to avoid overwhelming the server via axios-rate-limit. By slowing things down, I was able to stay within the site's rate limits without triggering the error.
But I wasn't happy about the speed.
So I set up ...
November 25, 2024 at 10:42 AM
First, I added delays between requests to avoid overwhelming the server via axios-rate-limit. By slowing things down, I was able to stay within the site's rate limits without triggering the error.
But I wasn't happy about the speed.
So I set up ...
It turns out I was sending too many requests too quickly, and the website wasn’t happy about it.
This error meant I had exceeded the rate limits set by the server, and I had to adjust my approach to keep things moving.
Here’s what I did to solve it:
This error meant I had exceeded the rate limits set by the server, and I had to adjust my approach to keep things moving.
Here’s what I did to solve it:
November 25, 2024 at 10:42 AM
It turns out I was sending too many requests too quickly, and the website wasn’t happy about it.
This error meant I had exceeded the rate limits set by the server, and I had to adjust my approach to keep things moving.
Here’s what I did to solve it:
This error meant I had exceeded the rate limits set by the server, and I had to adjust my approach to keep things moving.
Here’s what I did to solve it: