No as a Service

&gt; {&quot;error&quot;:&quot;Too many requests, please try again later.&quot;}<p>I guess it still works.

Not sure why, but reasons.json is mostly duplicates (as many as 50!) of the same 25 responses: <a href="https:&#x2F;&#x2F;gist.github.com&#x2F;deanputney&#x2F;4143ca30f7823ce53d894d3ede0a99c3" rel="nofollow">https:&#x2F;&#x2F;gist.github.com&#x2F;deanputney&#x2F;4143ca30f7823ce53d894d3ed...</a><p>It&#x27;d be easier to add new ones if they were in there a single time each. Maybe the duplication is meant to handle distribution?

Fun idea. I wonder why the rejection messages are repeated so often in the &quot;reasons&quot; file.<p>&quot;I truly value our connection, and I hope my no doesn&#x27;t change that.&quot; shows up 45 times.<p>Seems like most of the rejections appear between 30 and 50 times.

I made a lot of things like this as a noob and threw them up on github.<p>As you gain experience, these projects become a testament to how far you&#x27;ve come.<p>&quot;An http endpoint that returns a random array element&quot; becomes so incredibly trivial that you can&#x27;t believe you even made a repo for it, and one day you sheepishly delete it.

Example responses:<p><a href="https:&#x2F;&#x2F;raw.githubusercontent.com&#x2F;hotheadhacker&#x2F;no-as-a-service&#x2F;refs&#x2F;heads&#x2F;main&#x2F;reasons.json" rel="nofollow">https:&#x2F;&#x2F;raw.githubusercontent.com&#x2F;hotheadhacker&#x2F;no-as-a-serv...</a>

Well this is something... someone creating a service off the back of a meme that&#x27;s been flying around my networks for the past two days...

{&quot;error&quot;:&quot;Too many requests, please try again later.&quot;}<p>a missed opportunity for some humor

It could be genuinely useful for testing HTTP clients if it had a wider array of failure modes.<p>Some ideas:<p>- All the different HTTP status codes<p>- expired&#x2F;invalid TLS cert<p>- no TLS cipher overlap<p>- invalid syntax at the TLS and&#x2F;or HTTP level<p>- hang&#x2F;timeout<p>- endless slowloris-style response<p>- compression-bomb<p>- DNS failure (and&#x2F;or round-robin DNS where some IPs are bad)<p>- infinite redirect loop<p>- ipv6-only<p>- ipv4-only<p>- Invalid JSON or XML syntax

Looks impressive, but out of the 1000 possible responses, only 26 are unique.

A worthy spiritual disciple of the Journal of Universal Rejection (<a href="https:&#x2F;&#x2F;www.universalrejection.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.universalrejection.org&#x2F;</a>)

nice. Reminds me of BOFH (Bastard operator from Hell) . And those box-like calendars with page-per-day with some excuse^w^w tip on each :)<p><a href="https:&#x2F;&#x2F;bofh.bjash.com&#x2F;bofh&#x2F;bofh1.html" rel="nofollow">https:&#x2F;&#x2F;bofh.bjash.com&#x2F;bofh&#x2F;bofh1.html</a>

Oh great, it&#x27;s Balatro&#x27;s Wheel of Fortune card as a Service (WoFaaS)

The API rate limiting has been removed.

inb4 someone genuinely doesn&#x27;t understand why you wouldn&#x27;t do this with an LLM

:)

:)

&gt; Rate Limit: 10 requests per minute per IP<p>I understand that one wants some rate limiting so that others don&#x27;t just use this as a backend for their own service causing every single request for their service to also create an API request. But this is as simple and resource unintensive as it gets for an HTTP server. 10 requests per minute is just silly.<p>Also could it be that the limit isn&#x27;t enforced against the origin IP address but against the whole Cloudflare reverse proxy?