<story><title>418 I&apos;m a teapot</title><url>https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/418</url></story><parent_chain><item><author>geuis</author><text>Many years ago, some person misconfigured their squid proxy and was hitting &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;jsonip.com&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;jsonip.com&lt;/a&gt; to the point my server at the time was turning green in the gills.&lt;p&gt;I started responding with 418 &amp;quot;You are a tea kettle&amp;quot; or something like that to those specific requests. The originating dev actually paid attention to their error messages and quickly resolved their config issue.&lt;p&gt;Fast forward to March this year. Some fucking numb nuts a-hole decided to add jsonip.com to an EXTREMELY widely used version of Dalvik&amp;#x2F;Android software that gets deployed to hundreds of thousands or millions of devices.&lt;p&gt;Overnight my traffic levels increased by 300%. I&amp;#x27;m a solo dev offering a free service for 12 years. That kind of increase in traffic costs me money I&amp;#x27;ve never had to plan for.&lt;p&gt;I ended up switching to Cloudeflare to handle the load with a WAF filter on the offending android tvs and other devices.&lt;p&gt;However Cloudflare doesn&amp;#x27;t properly route ipv4 address because &amp;quot;ipv6 is cool so we only do that&amp;quot; or something. Despite numerous support requests, that&amp;#x27;s still &lt;i&gt;shmaybe&lt;/i&gt; an enterprise level feature.&lt;p&gt;I apologize to any long time users of the service. This was completely unexpected after more than a decade. I&amp;#x27;ve been trying different &amp;quot;fixes&amp;quot; for 2 months and have not resolved a way to block this garbage traffic and still provide the original services.&lt;p&gt;Yea sorry I turned this funny old internet post about the mit coffee pot into a thing happening to me.&lt;p&gt;But if for some ungodly reason you&amp;#x27;re the dev or know who did  it, REMOVE MY SERVICE ADDRESS FROM YOUR OUT OF DATE FROM TV&amp;#x2F;SMART DEVICE ANDROID code. You&amp;#x27;re literally fucking killing me. I&amp;#x27;ve literally spend dozens of hours trying to find out if this was a contribution to a public source repo. Nothing.&lt;p&gt;Based on the Dalvik user agent, I only found a handful of references in Chinese repos. But google search is so terrible these days, even those are false flags.&lt;p&gt;So I have &lt;i&gt;no&lt;/i&gt; idea who to contact about this. Some dipshit on your team(s) decided to abuse a free service as though there isn&amp;#x27;t a single human person behind it absorbing the costs and making sure it runs.</text></item></parent_chain><comment><author>mrweasel</author><text>Could you start returning wrong answers, &amp;quot;country&amp;quot;:&amp;quot;TW&amp;quot; should do it.&lt;p&gt;We had to deal with image scrapers who didn&amp;#x27;t respond to requests to stop, even if we provided an API service. I configured nginx to just serve them images of a beaver and a few 1GB junk files, they stopped pretty quickly.</text></comment>
<story><title>418 I&apos;m a teapot</title><url>https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/418</url></story><parent_chain><item><author>geuis</author><text>Many years ago, some person misconfigured their squid proxy and was hitting &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;jsonip.com&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;jsonip.com&lt;/a&gt; to the point my server at the time was turning green in the gills.&lt;p&gt;I started responding with 418 &amp;quot;You are a tea kettle&amp;quot; or something like that to those specific requests. The originating dev actually paid attention to their error messages and quickly resolved their config issue.&lt;p&gt;Fast forward to March this year. Some fucking numb nuts a-hole decided to add jsonip.com to an EXTREMELY widely used version of Dalvik&amp;#x2F;Android software that gets deployed to hundreds of thousands or millions of devices.&lt;p&gt;Overnight my traffic levels increased by 300%. I&amp;#x27;m a solo dev offering a free service for 12 years. That kind of increase in traffic costs me money I&amp;#x27;ve never had to plan for.&lt;p&gt;I ended up switching to Cloudeflare to handle the load with a WAF filter on the offending android tvs and other devices.&lt;p&gt;However Cloudflare doesn&amp;#x27;t properly route ipv4 address because &amp;quot;ipv6 is cool so we only do that&amp;quot; or something. Despite numerous support requests, that&amp;#x27;s still &lt;i&gt;shmaybe&lt;/i&gt; an enterprise level feature.&lt;p&gt;I apologize to any long time users of the service. This was completely unexpected after more than a decade. I&amp;#x27;ve been trying different &amp;quot;fixes&amp;quot; for 2 months and have not resolved a way to block this garbage traffic and still provide the original services.&lt;p&gt;Yea sorry I turned this funny old internet post about the mit coffee pot into a thing happening to me.&lt;p&gt;But if for some ungodly reason you&amp;#x27;re the dev or know who did  it, REMOVE MY SERVICE ADDRESS FROM YOUR OUT OF DATE FROM TV&amp;#x2F;SMART DEVICE ANDROID code. You&amp;#x27;re literally fucking killing me. I&amp;#x27;ve literally spend dozens of hours trying to find out if this was a contribution to a public source repo. Nothing.&lt;p&gt;Based on the Dalvik user agent, I only found a handful of references in Chinese repos. But google search is so terrible these days, even those are false flags.&lt;p&gt;So I have &lt;i&gt;no&lt;/i&gt; idea who to contact about this. Some dipshit on your team(s) decided to abuse a free service as though there isn&amp;#x27;t a single human person behind it absorbing the costs and making sure it runs.</text></item></parent_chain><comment><author>dannyw</author><text>Your website on &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;getjsonip.com&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;getjsonip.com&amp;#x2F;&lt;/a&gt; says:&lt;p&gt;&amp;gt; Supports unlimited requests and is free.&lt;p&gt;Maybe update that text? There is no guidance on acceptable thresholds, rate limits, etc.</text></comment>