Live data from Hacker News

418 I'm a teapot

developer.mozilla.org

191–195 of 195 posts

Re: 418 I'm a teapot

#191
post #89

Earlier quoted context omitted.

> 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.

I see no contradiction. There is a difference between gracefully and responsibly using something that is offered for free, and just bombarding it with requests like no tomorrow. People can of course do the latter. But then they don't get to complain when at some point, the available offerings present walls of legalese instead of a few simple and clear statements, and the user experience goes from seamless and easy to…

It all depends on the nature of the work you are doing.

One thing is to own a service that's used by 10 MAU and you extend the service with a job that calls the OP's service 100 times a second. That's bad, you are using way more than you need.

Another thing is to own a mobile app used by 10M MAU and you embed the OP's service into the app. That's not bad intention, you just added a new service to your app. The problem is that the OP's definition of "unlimited" is not really unlimited.

Re: 418 I'm a teapot

#192
post #89

Earlier 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.

You can say that the local community water well has "unlimited uses", then complain when Nestle comes over and takes all the water.

No difference here.

Re: 418 I'm a teapot

#193
post #59

Many 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…

icanhazip.com had similar issues. Cloudflare took over the project https://major.io/2021/06/06/a-new-future-for-icanhazip/ Fyi, dns can be used to obtain public ip from large companies, without the overhead of tcp and http dig +short txt ch whoami.cloudflare @1.0.0.1 dig +short txt o-o.myaddr.l.google.com @ns1.google.com dig +short myip.opendns.com @resolver1.opendns.com

What does the "ch" mean?

Re: 418 I'm a teapot

#195

Earlier quoted context omitted.

I hate to add to your headache, but multiple pihole ad blacklists contain your domain. It looks like https://winhelp2002.mvps.org/ may be the original source of the blacklisting.

pihole and other dns blocklists would reduce traffic to their service, not increase it

Yeah but it means their service is less valuable. If adblockers block traffic to that domain then there's less incentive to pay for the service because an undetermined but ever growing percentage of traffic will block it.

Now it's a headache for a different reason.

Post reply on HN