Save HTTP 418!

[Bytewave]

Programmers, web developers, coffee brewers and internet goers, rise! There is a cause we must stand for, a cry for help! The IETF wants to take away our beloved 418 client response code to be "repurposed"!

The 418 status code is vital in the detection of networked teapots. Repurposing it would cause teapot detection to lose semantic meaning! I'm not sure about the rest of you, but the thought of losing the most vital status code to HTCPCP to whatever purposes this new chair plans to use it for is unbearable for me! I cannot stand to lose such a vital status code implemented in a great number of software projects!

Please, fellow programmers. Stand for the protection of HTTP 418 I'm a teapot. Stand for semantically-correct teapot identification. Stand for the joy, humor, and excitement 418 brings into your lives!

Or just stand for the meme.

http://save418.com/

also, hey there. long time no see.

[Timmy]

The importance of this status code to both developers and end-users cannot be underestimated. Removing it is 406 Not Acceptable.

#Save418

[Bytewave]

Update: It appears IETF is taking strides to mark HTTP 418 as Reserved! This could grant us the victory we need! Hooray!

[JamminR]

Though I agree with the importance, I feel I must present another side.
I've not researched what the IETF wishes to re-purpose 418 for; however, I might be more amiable towards the re-purpose if it were going towards, say, a 'honey pot' status.
Some might argue 418 Honey Pot might draw more flies to the internet. I feel though, if properly implimented, it could be a great upgrade to what, I believe, is less used.
Tea pots today just aren't as popular in the millennial age. Fortunately, perhaps a 418 Honey Pot would help bring awareness of our diminishing honey bee population to more.