I like returning 418 instead of 404 or 403 on the files the script kiddies are hunting for on my web servers. I’m sure it does nothing but I’d like to think I’ve wasted some of their time at least once.
420 is still avalable. Not sure what you would put there (“Server too high?”) and given the controversy over 418 I think its best to leave that one blank instead of making a weed joke.
I like returning 418 instead of 404 or 403 on the files the script kiddies are hunting for on my web servers. I’m sure it does nothing but I’d like to think I’ve wasted some of their time at least once.
I’m glad that error exists.
I’m pretty sure it exists because of RFC2324 hyper text coffee pot control protocol
Fun fact, first webcam was a series of updating stills of an actual coffee pot so some engineers would know if there was coffee made.
Technically, all video is a series of updating stills.
True, but most streaming media now is a bunch of stills with the changes for each individual frame between them.
True, but webcams still just deliver raw frames (or compressed frames in the case of MJPEG).
With that, plus image recognition, plus a control system, you could use rfc2324 to implement the digital control side
Though I think I’d use weight, temperature, and flow sensors for easier service implementation
And then plug those values into a image generation service to give users a visually intuitive way to see if there’s cooffe or not!
Necessity is the mother of invention
You had one chance to use 420 and you squandered it.
HTTP 418 is the “I’m a teapot” code
Oh I get plenty of chances to use 420. But I think you might be missing the joke. 😁
420 is still avalable. Not sure what you would put there (“Server too high?”) and given the controversy over 418 I think its best to leave that one blank instead of making a weed joke.
There was an attempt by Twitter at one point to use “420 Enhance Your Calm” as a code to indicate you’re being rate limited.