The Hypertext Transfer Protocol Status Code 483 (I'm Not a Freezer)

73 points by rbanffy 9 hours ago on hackernews | 46 comments

stop50 | 9 hours ago

Couldn't he submit it on april 1st?

[OP] rbanffy | 9 hours ago

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 ;-)

bricss | 9 hours ago

Only freezers 30 years old and older will survive, tho :D

ForHackernews | 7 hours ago

Try writing your own jokes next time.

throw-the-towel | 9 hours ago

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:

    HTTP 418 I'm A Teapot
    I'm-Not-A: freezer;teapot;radio

sgarland | 9 hours ago

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.

cyanydeez | 9 hours ago

needs more dry; just remove the second I'm and it's clearer.

rzzzt | 8 hours ago

421 Misdirected Request works equally well.

basilikum | 8 hours ago

This is a proposal to add a new HTTP status code. 418 is not a HTTP status code but a HTCPCP status code.

k0morebi | 8 hours ago

Should be "I'm a little teapot" short and stout is implied

ivanjermakov | 8 hours ago

Isn't consistent for "I'm not a teapot" though.

pocksuppet | 7 hours ago

For compatibility with header splitting, the delimiter should be a comma, The following header:

    I'm-Not-A: freezer, teapot, radio
is equivalent to:

    I'm-Not-A: freezer
    I'm-Not-A: teapot
    I'm-Not-A: radio
even in cases where the client, server, or some intermediate proxy doesn't know the I'm-Not-A header.

jagged-chisel | 5 hours ago

This is unwieldy. Now my server has to list everything is is not.

It's not a quasar, nor a toaster, nor a tree, a pipe, a microwave transmitter, a microwave oven, a plush spider, an actual arachnid, a whale, a motorscooter, a motorcycle, an automobile, an apricot, a grape, raw sugar ...

TeMPOraL | 4 hours ago

> radio

That response would be a lie, though. If it runs on electricity, it's most definitely a radio of some sort.

[OP] rbanffy | 4 hours ago

Depends on how well shielded though. What level of emission would be the minimum required for being classified as a radio?

quink | 8 hours ago

When the main compression algorithm the device supports is making the data have a temperature of 4 degrees Celsius.

hjahre | 7 hours ago

It's the algorithm that runs the fridge or freezer compressor, right?

[OP] rbanffy | 3 hours ago

Cooling would happen at expansion, so you compress the data, run it through an external heat exchanger for it to cool down to outer loop temperature, then expand it before you inject the cold data in the internal coils.

These data compression and expansion circuits can be cascaded and are perfectly suited for data flow architectures.

theandrewbailey | 8 hours ago

Perhaps HTTP 416 Range Not Satisfiable could also be extended when a client requests a temperature that the server cannot produce.

russfink | 8 hours ago

Might not be a freezer, but the Intro is AI, according to Pangram.

TZubiri | 8 hours ago

Came here to post the same thing, not only is it derivative over HTTP 418 Teapot, but it's generated with AI.

I'm amazed how people think they are contributing anything by being a meat proxy. In the cases of serious proposals it's hard to disprove, but in the case of a joke, it's just ridiculous on its face.

I get that there was a fridge hack, but there's also no jokes regarding that, it's just a bland HTTP 418 like RFC but with teapots replaced with Fridges

woadwarrior01 | 7 hours ago

Incidentally, isn't outsourcing one's judgement to Pangram, also a case of being a meat proxy? :D

TZubiri | 7 hours ago

If you can't see what's different between spamming synthetic text as being one's own, and incorporating 2 bits of entropy from Pangram into my analysis, I don't know what to tell ya.

TeMPOraL | 4 hours ago

Who ever believes ratings from Pangram? Might as well report `sha256(text) % 5 == 0`, it's just as principled way of telling text is AI generated.

fancyfredbot | 4 hours ago

I tested your suggestion but it's detecting only 20% of my entirely AI generated test corpus. Very poor performance.

woadwarrior01 | 3 hours ago

> incorporating 2 bits of entropy from Pangram into my analysis

So, you're admitting that it's entropy. :)

acheron | 5 hours ago

Hn guidelines:

Please don't complain about tangential annoyances. They're too common to be interesting.

tangotaylor | 5 hours ago

Also:

> Please don't put generated text in HN posts. Write your text yourself—HN is for sharing between humans. For the same reason, please don't automate posting.

This is definitely a gray area (AI in linked articles but not on HN itself) that HN will need to reckon with someday.

I really wish the mods would automatically pangram-scan submissions that reach the frontpage and let users filter them if they want to...

In the meantime, I'm building a browser extension that adds a visible mark to HN links flagged by Pangram as AI-generated. That way I won't waste my time reading them, or if I do read them at least I'll know what I can expect. The idea is to have an open index of pangram results for HN articles, which the extension downloads, giving the user the option to mark (or even remove) articles that exceed a threshold of their choosing. Pangram credits are expensive, though.

YoshiRulz | 3 hours ago

I don't think your link is related to what I described in my comment. That project classifies articles as being _about_ AI or not. Being LLM-authored is orthogonal to that. Case in point, this article we are commenting on now is happily listed there.

r4ndomname | 7 hours ago

This is something I’ve been thinking about for a long time, particularly in the context of critical infrastructure providers such as hospitals. However, I always got stuck on the fact that anyone could return such a status code to deter attackers, which would ultimately render the indicator meaningless.

captn3m0 | 52 minutes ago

People said the same thing about the Evil Bit, but that worked out well! It’s just unfortunate that the fridges were not filtering on the Evil Bit, they would have been safe otherwise.

JdeBP | 7 hours ago

M. Banffy, you are very naughty. (-:

That said, is this truly a 4xx error? It seems to be a server problem, not a client problem, that the server is not a freezer.

Will revision 01 put more detail into §11 and §12?

[OP] rbanffy | 7 hours ago

I suppose we can iterate over the problems this would solve. It's not lost on me that we might want to reverse it into a positive assertion, as in code 418, but it might night to be split as in "I'm an air-conditioner", "I'm a heat pump", "I'm a refrigerator", "I'm a freezer", "I'm a cryogenic freezer", and further qualifications.

pocksuppet | 7 hours ago

This is just HTTP 418 with s/teapot/freezer/ and a run through a slop machine. A good April Fool's joke is not just copying someone else's joke and switching a couple of words around.

gliptic | 7 hours ago

This is nonsensical so I'm thinking LLM generated.

> A server MUST NOT return 483 merely because:

> * its operating temperature is below ambient temperature;

Why would it return `I'm Not a Freezer` because it's cold?

tintor | 7 hours ago

Server operating in freezing temperature is not the same as server controlling a freezer.

gliptic | 7 hours ago

Yes, but that would make sense if the header was "I _Am_ a Freezer", then it should NOT return "I Am a Freezer" just because the server is merely cold. Now it's admonishing against the opposite of what someone might think to do.

[OP] rbanffy | 3 hours ago

The intent is for it to be used as an error state, when it’s unable to comply with a command. If an attacker runs a blind scan over a network looking for freezers via a common temperature manipulation API, a refrigerator - or an oven, heat pump, or air conditioner that shares the same API - can confidently return a pertinent and informative status code so that the attacker does not retry the call.

mort96 | 6 hours ago

What's the point of this? Isn't this just a less funny, less well-written derivative of the HTCPCP joke?

Over on Reddit they call this phenomenon "your joke but worse": https://www.reddit.com/r/YourJokeButWorse/

binaryturtle | 5 hours ago

The only HTTP status code that matters:

999 <Bleep> Off

:-)

[OP] rbanffy | 3 hours ago

We could also have a 666 for when the server runs directly on metal without an OS.

jagged-chisel | 5 hours ago

Right up there with the evil bit. Amusing, and useless.

apapapp | 4 hours ago

Does anyone find this sort of crap funny? Nerd humor at its worst.

InvisibleUp | 3 hours ago

If taken as an actual HTTP code, this has significant overlap with 422 (Unprocessable Content) and HTTP 501 (Not Implemented).