> {"error":"Too many requests, please try again later."}

I guess it still works.

Bug report: when the server is overloaded, the No's are no longer random :)

Not sure why, but reasons.json is mostly duplicates (as many as 50!) of the same 25 responses: https://gist.github.com/deanputney/4143ca30f7823ce53d894d3ed...

It'd be easier to add new ones if they were in there a single time each. Maybe the duplication is meant to handle distribution?

ah, yes, the "memory is no object" way of obtaining a weighted distribution. If you need that sweet sweet O(1) selection time, maybe check out the Alias Method :)

Example responses:

https://raw.githubusercontent.com/hotheadhacker/no-as-a-serv...

Fun idea. I wonder why the rejection messages are repeated so often in the "reasons" file.

"I truly value our connection, and I hope my no doesn't change that." shows up 45 times.

Seems like most of the rejections appear between 30 and 50 times.

A single large file is also sadness for incorporating suggestions from collaborators as you're always dealing with merge conflicts. Better might be a folder of plain text files, where each can have multiple lines in it, and they're grouped by theme or contributor or something.

There are 25 unique responses in that 1000-line file.

Was wondering the same thing.. Probably cruft so it looks impressive at a glance.

If you ask LLMs for a long enough list of things, they often repeat entries.

Oh great, it's Balatro's Wheel of Fortune card as a Service (WoFaaS)

It could be genuinely useful for testing HTTP clients if it had a wider array of failure modes.

Some ideas:

- All the different HTTP status codes

- expired/invalid TLS cert

- no TLS cipher overlap

- invalid syntax at the TLS and/or HTTP level

- hang/timeout

- endless slowloris-style response

- compression-bomb

- DNS failure (and/or round-robin DNS where some IPs are bad)

- infinite redirect loop

- ipv6-only

- ipv4-only

- Invalid JSON or XML syntax

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

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

:)

:)

> Rate Limit: 10 requests per minute per IP

I understand that one wants some rate limiting so that others don'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.

Also could it be that the limit isn't enforced against the origin IP address but against the whole Cloudflare reverse proxy?

Mate, it's a joke, not a serous service. The only silly thing here is going off on a tangent about the rate limit.

10 requests per minute per IP is plenty enough to play around with and have a little fun. For anything more than that you could (should!) host it yourself.

So it is just purposefully made to be less useful? Is that part of the joke?

The rate limit still pretty surely isn't applied per IP.

If it helps you, think of the rate limiter as the "no" final boss.