I think there should be a "555 Bad Timer" error for when servers can't keep up or are running slow. Like a "429 Too Many Requests" error but it's the server's fault.
418 I'm a teapot
101–110 of 195 posts
Re: 418 I'm a teapot
#102Many years ago, some person misconfigured their squid proxy and was hitting https://jsonip.com to the point my server at the time was turning green in the gills. I started responding with 418 "You are a tea kettle" or something like that to those specific requests. The originating dev actually paid attention to their error messages and quickly resolved their config issue. Fast forward to March this year. Some fucking…
You're a better person than me. I'd start returning nonsense like `999.9` to see if I could trigger a ton of bug reports for someone.
other evil ideas:
- return a 200 with broken JSON, possibly triggering parse errors or exceptions in the caller
- return a payload that generates catastrophic resource consumption on the other end, e.g Content-Encoding: gzip and feed it a deflate bomb
- hack TCP and/or TLS to leave the other end waiting/stalling in an attempt to rate limit (timeout) or starve resources (ulimit) on the other end (e.g abuse 3 way handshake)
Re: 418 I'm a teapot
#103Earlier quoted context omitted.
Yeah I know. That is a legit critique. What's been happening is your essential black swan event. I've been running the service for 12 years and have never had this problem. There are hundreds of websites and independent users that have never abused the api like this until March. I have always been able to absorb the traffic impact. This is different. Someone wasn't thinking and randomly added the domain to a lazy pie…
Unethical tip: start returning the content of this article [0] to these devices. The Chinese government will "fix" the devs for you or simply block all traffic to your site. [0] https://en.wikipedia.org/wiki/1989_Tiananmen_Square_protests...
How’s that unethical?
Love it.
Re: 418 I'm a teapot
#104Earlier quoted context omitted.
Yeah I know. That is a legit critique. What's been happening is your essential black swan event. I've been running the service for 12 years and have never had this problem. There are hundreds of websites and independent users that have never abused the api like this until March. I have always been able to absorb the traffic impact. This is different. Someone wasn't thinking and randomly added the domain to a lazy pie…
Explicitly telling some junior software developer in China that he can call an API for free an unlimited number of times, then afterwards calling it abuse and him and a-hole dev is definitively a bit of an a-hole thing to do in my view.
It says that you can call it unlimited number of times, not millions of devices that you’re selling.
Re: 418 I'm a teapot
#105Earlier quoted context omitted.
You absolutely can. Nobody has an obligation to serve you if you are an asshole.
Why complain instead of mitigating? Or why not complain AND mitigate at the very least? Do not serve it to assholes?
I’ll never understand “no complain” argument.
Person has a valid complaint, goddamnit, they have all the rights to complain.
Re: 418 I'm a teapot
#106Earlier quoted context omitted.
> you can't complain then if people are using it. Yes he can complain, and bombarding a free service for unlimited requests isn't okay. For starters because the people doing that, will usually be among the first to cry when the free service stops being free, blocks their requests or suddenly requires an API key.
> bombarding a free service for unlimited requests isn't okay Hummmm.... OP's website on https://getjsonip.com/ says: > Supports unlimited requests and is free. Seems like we have a bit of a contradiction here.
[deleted]
Re: 418 I'm a teapot
#107Earlier quoted context omitted.
Unethical tip: start returning the content of this article [0] to these devices. The Chinese government will "fix" the devs for you or simply block all traffic to your site. [0] https://en.wikipedia.org/wiki/1989_Tiananmen_Square_protests...
How’s that unethical? Love it.
Unethical because it can get the devs into legal trouble and the Chinese government is known to be aggressive in their choice of "solutions".
Re: 418 I'm a teapot
#108Earlier quoted context omitted.
That’s typically why it’s a good idea to include a crappy “generate API” key button so you can block traffic like this, you don’t even need a registration process - someone can just email with reference to their API key to discuss their issues.
> you don’t even need a registration process You should put it behind a CAPTCHA of some sort however, otherwise, some smartass will just write a "library" auto-fetching an api key as soon as the one it has currently cached stops working. And yes, that is an annoyance to users, but so what? Please direct all complaints to the comparatively small number of people responsible for the fact that the rest of us cannot have…
This is not really a problem, you can easily disable generating new keys and sidestep the problem. Everyone who's legit can keep using their old keys.
Re: 418 I'm a teapot
#109Earlier quoted context omitted.
Explicitly telling some junior software developer in China that he can call an API for free an unlimited number of times, then afterwards calling it abuse and him and a-hole dev is definitively a bit of an a-hole thing to do in my view.
It says that you can call it unlimited number of times, not millions of devices that you’re selling.
It says:
> Supports unlimited requests and is free.
Typically "unlimited" is more than a million.
Re: 418 I'm a teapot
#110Many years ago, some person misconfigured their squid proxy and was hitting https://jsonip.com to the point my server at the time was turning green in the gills. I started responding with 418 "You are a tea kettle" or something like that to those specific requests. The originating dev actually paid attention to their error messages and quickly resolved their config issue. Fast forward to March this year. Some fucking…
> literally fucking killing me
Wow, that's crazy.