I was at CMU '83 to '87. It saved us time to check if there was the proper kind of coke in the machine and if it was cold before we walked down to the room with the machine. It was cheaper than the University's vending machines. And it was in classy glass bottles.
Trivia: It was (I was told) using experimental 3Mbps Ethernet, the predecessor to the 10Mbps Ethernet that has grown to 10Gpbs+ now.
Only from clients supporting HTTP only. Note that RFC 2324 [0] defines the Hyper Text Coffee Pot Control Protocol or HTCPCP, which is an extension of HTTP and implementors of clients for this are free to return 418 if necessary. Also, RFC 7168 [1] which extends the protocol as HTCPCP-TEA now fully supports teapots, and is probably a better choice for modern clients. Also of interest is the SNMP MIB for remote management of 'Drip-Type Heated Beverage Hardware' which is defined in RFC 2325 [2] although this does not appear to have been updated with teapot, samovar, urn or other non-filter-coffee management data...
Implementing tea making device remote management would probably be a good candidate for a GSoC project or even a startup if you can find a VC gullible enough to fund you!
Which is actually used in a few places. Google always return it from https://www.google.com/teapot, and Binance uses that status code if you've been IP-banned for exceeding rate limits.
Our team got hit by that issue. I slapped by head when I saw the error code, having come across it before. How am I meant to debug something that's literally a joke and isn't meant to be used in production :(
I wonder if someone fill the column and it is not empty say 1 bottle left. Then it is still not cold if someone else got say the 2nd one. Any source code available to check :-)
HTTP Status 418: I'm a teapot - https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/418
Wasn't there also a protocol for checking vending machines for cold drinks?