Look up absurdly specific HTTP 7xx error codes to share with your team as developer humor
Use the formal RFC structure as a template for writing your own joke technical specification
Add a humorous 7xx status code to developer-facing API error responses when the bug is clearly the caller's fault
Reference the code list when writing blog posts or talks about HTTP status codes to add comic relief
| joho/7xx-rfc | openwrt/packages | naereen/badges | |
|---|---|---|---|
| Stars | 4,540 | 4,494 | 4,605 |
| Language | Makefile | Makefile | Makefile |
| Setup difficulty | easy | hard | easy |
| Complexity | 1/5 | 4/5 | 1/5 |
| Audience | developer | ops devops | developer |
Figures from each repo's GitHub metadata at analysis time.
This repository is a joke proposal written in the style of an official internet standards document, known as an RFC. Real RFCs define how things on the internet should work, and HTTP status codes are one example: the 400 series covers client errors and the 500 series covers server errors. This project proposes a fictional 700 series of status codes meant to describe situations that are actually the developer's fault. The list reads like a comedy catalog of software development disasters. Proposed codes include 701 (Meh), 725 (It works on my machine), 726 (It's a feature, not a bug), 778 (Off By One Error), and 799 (End of the world). There are whole categories for predictable caching problems, syntax errors written in a hurry, errors caused by the developer being in various states of caffeination or otherwise, and errors that are really somebody else's problem, such as 784 (Management, obviously) and 782 (QA). The document is written with the same formal language and structure as a real RFC, complete with terminology definitions, a table of contents, author contact information, and references to actual standards. That straight-faced presentation against absurd content is most of the joke. The project was started at Railscamp, a community gathering for developers in Australia and New Zealand. The source is maintained as a Markdown file and converted into proper RFC formatting using a tool called mmark. The repository includes a Makefile so that running a single build command produces the formatted output. It is licensed under Creative Commons Attribution-NonCommercial-ShareAlike 4.0, meaning it can be shared and adapted freely for non-commercial purposes with attribution.
A joke internet standards document proposing a fictional HTTP 700-series of status codes for errors that are clearly the developer's fault, written with the same straight-faced formal language as a real RFC.
Mainly Makefile. The stack also includes Markdown, mmark, Makefile.
You can share and adapt this for non-commercial purposes as long as you credit the original authors and share under the same license.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.