Considering 418 is the positive assertion, suddenly reversing that would break backwards compatibility; additionally, it adds ambiguity by listing multiple entities it is not, leaving the receiver to potentially assume that it is, for example, a microwave.
EDIT: missed the positive part remaining, sorry. I maintain that the ambiguity issue stands.
Might not be a freezer, but the Intro is AI, according to Pangram.
This is an anti-pattern. A better, future-proof solution would be to extend HTTP 418 with a header stating just what the server is not:
Considering 418 is the positive assertion, suddenly reversing that would break backwards compatibility; additionally, it adds ambiguity by listing multiple entities it is not, leaving the receiver to potentially assume that it is, for example, a microwave.
EDIT: missed the positive part remaining, sorry. I maintain that the ambiguity issue stands.
This is a proposal to add a new HTTP status code. 418 is not a HTTP status code but a HTCPCP status code.
needs more dry; just remove the second I'm and it's clearer.
Should be "I'm a little teapot" short and stout is implied
421 Misdirected Request works equally well.
Perhaps HTTP 416 Range Not Satisfiable could also be extended when a client requests a temperature that the server cannot produce.
When the main compression algorithm the device supports is making the data have a temperature of 4 degrees Celsius.
Couldn't he submit it on april 1st?
I tried at the time of the fridge hacks in Europe, but submission was closed.
They can still hold approval and publish it on April 1st.
But, then, there is no guarantee humanity will survive that long ;-)
Only freezers 30 years old and older will survive, tho :D