71–80 of 146 posts
Earlier quoted context omitted.
Now. I didn't know about the RFC. This is so good. I hope we can continue to advance this field with good humor, and good coffee.
There are quite some RFC with humor, most prominently probably RFC1149 and its extension RFC2549
IP over Avian Carriers with Quality of Service https://www.rfc-editor.org/rfc/rfc2549
Earlier quoted context omitted.
This 418 stuff reminds me of a previous job where we had some arguments about putting emojis in our applications. I was against it and a coworker was for it. Like putting rocket ship emoji when an operation succeeds. My main argument was that if you put things like that in your applications then people start having opinions about it and they want to discuss it and add more to certain places or remove from other place…
We just had a work party and they invited the whole staff. I was outraged they didn't do a proper controlled A/B test. Management will never know if having fun together was a good use of their money. Idiots.
All those small discussions were essentially pointless and they happened often enough that I was getting annoyed by them.
Like, sometimes we would be showing "in development" stuff to clients and then they would interrupt and mention something like "nice rocketship emoji" and I am like "can you just focus on what I am showing you"
I've always wondered if you were to have an actual networked Teapot, when would it be appropriate to send 418.
I am sure there are some networked teapots already.
If someone wanted to send a "brew tea" request (via POST?) to an actual teapot, then 418 would not be suitable, you'd want something else, no?
Earlier quoted context omitted.
There are definitely missing codes, which is why sometimes the WebDAV status additions get used in purported RESTful APIs—which is semantically wrong, but often carries a lot of helpful meaning. For example, things like 422: Unprocessable Content or 423: Locked are really helpful to convey meaning, but not available in plain HTTP.
> 422: Unprocessable Content I honestly would have thought 400 Bad Request would cover that? Might be too generic though. Is "422" "ok, I admit it's formatted correctly, but I can't process it for some higher-level reason than syntax"? (Just reading through 4xx codes, and I think I need to use 410 Gone a lot more often. Does anyone know if search engines treat 404 and 410 differently?)
Usually in one of these threads, someone links the iiNet coffee cam. Here you go: https://coffeecam.iinet.net.au/coffee/history/
The coffeecam was cute, acb - the one primarily responsible for the coffeecam - also had American candies for sale around it (at least when I worked there at Hay Street)
Earlier quoted context omitted.
Disagree. We gotta have fun.
I counter-disagree. It is so easy in life to have fun. There's so much fun everywhere. If you're so starved for fun then this won't do it for you either. The higher the scale the more likely your easter egg becomes not an easter egg. I also think the supermajority of engineers prefer fun entirely outside of work, hence why open source can feel so lonely and without corporate funding would probably shrink to a patheti…
"I think that it's extraordinarily important that we in computer science keep fun in computing. When it started out, it was an awful lot of fun. Of course, the paying customers got shafted every now and then, and after a while we began to take their complaints seriously. We began to feel as if we really were responsible for the successful, error-free perfect use of these machines. I don't think we are. I think we're responsible for stretching them, setting them off in new directions, and keeping fun in the house. I hope the field of computer science never loses its sense of fun. Above all, I hope we don't become missionaries. Don't feel as if you're Bible salesmen. The world has too many of those already."
Vim implemented this: `:call err_teapot()`.
Why would a text editor have a way to produce HTTP error codes? I don't get it
vim scp://seanhunter@somehost.example.com:1234/.vimrc
^ ...which believe it or not works just fine if I have ssh access to that host.
..and I think http is supported for stuff like webdav, although I can't think of ever using http directly in vim like that. Given it's built-in it's useful for things like updating plugins etc. Once you've made the leap to thinking having net support like that built in is worthwhile, it makes sense for vim to have the wherewithall to test the responses for different status codes etc so plugins and scripts which use that network functionality can test the different failure cases.
I think since it is I am a teapot not you are a teapot It should be a 5xx code because clearly it's a server side issue.