| ▲ | rjst01 5 days ago |
| One day I will give a lighting talk about the load bearing teapot, or how and why I made HTTP Status 418 a load bearing part of an internal API, and why it was the least bad option considering the constraints. |
|
| ▲ | renewiltord 4 days ago | parent [-] |
| It’s a classic. Binance will give you 429 errors to back off then 418s to tell you you will be IP banned and then they’ll ban you. |
| |
| ▲ | hinkley 4 days ago | parent [-] | | Google’s spiders will punish you for giving them too many 429 responses. It’s hell for hosting sites with vanity urls. They can’t tell they’re sending you 50+ req/s. It’s practically a protection racket. Only AWS gets the money. | | |
| ▲ | wbl 4 days ago | parent [-] | | 50 requests/sec? Did you forget a few zeros? | | |
| ▲ | hinkley 4 days ago | parent [-] | | Little’s law is a bitch, and you can get away with a little throttling but not much. Also, that’s a bit dismissive for HN. |
|
|
|