51–60 of 114 posts
Earlier quoted context omitted.
Do you mean ads in the sense of "please buy brand X coffee" or in the sense of "please try some of this machine's delicious coffee"?
just stuff that emphasizes the brand of coffee that's in the machine. It's ridiculous (obviously an ad to buy that brand at home too, which I safely won't since I like my specialty coffee). We need coffee machines that shut up and serve coffee and don't do brand ads.
Earlier quoted context omitted.
I still love that people actually went through the effort to "implement" it.
Any links to APIs that implement a 418 HTTP response code?
It will happen often if you try to make a call to their API through Google sheet scripts.
Some previous discussions on this status specifically: https://hn.algolia.com/?q=418 Some fun ones: - Discussion on the status itself: https://news.ycombinator.com/item?id=24206899 - NPM proxy users receiving ERR 418 I'm a teapot: https://news.ycombinator.com/item?id=17175960 - Reserve the 418 status code: https://news.ycombinator.com/item?id=15004907
Earlier quoted context omitted.
I come from a country with rather _interesting_ views on what should be allowed online. 451 is used often enough that I've seen it in the wild more than once (and consider yourself lucky if you haven't encountered it...).
I get those every so often from US websites that doesn't want to deal with the GDPR.
I guess it's been about a generation since I implemented this as an easter-egg in a RESTful API service I built. It was quite the joke then, but now with IoT "smart" teapots and whatnot being so popular, it's not so funny now.
Earlier quoted context omitted.
I still love that people actually went through the effort to "implement" it.
Any links to APIs that implement a 418 HTTP response code?
What response should a printer give if you asked it to send a fax, but you have a base-model printer that doesn't support sending faxes. From the perspective of the printer, I know what you want (i.e. not a 404) and you've asked for it correctly (i.e. not 400 or 401 or 403), but I can't do it, and this does not indicate an error on my part (not a 500 or 503). Thus, 418: Unsupported Device.
Perhaps this too much of an overlap with 404 (I don't have that resource) and 501 (I can't do that verb to that resource), which I assume is why there's not a huge need for it. But if we're going to have 418 exist and receive browser support anyway, it might as well have a useful meaning rather than just exist as a joke.
This interpretation is fully in keeping with the non-joke meaning of the original RFC, as a teapot is a device that does not support brewing coffee.
I'm personally of the opinion that 418 shouldn't be considered a joke response, but would actually useful as 418 "Unsupported Device". What response should a printer give if you asked it to send a fax, but you have a base-model printer that doesn't support sending faxes. From the perspective of the printer, I know what you want (i.e. not a 404) and you've asked for it correctly (i.e. not 400 or 401 or 403), but I can…