

We also got fully self driving cars in 2 years though, in 2016…
We also got fully self driving cars in 2 years though, in 2016…
Those scenes going to be way more stupid in the future now. Instead of just showing netstat and typing fast, it’ll now just be something like:
CSI: Hey Siri, hack the server
Siri: Sorry, as an AI I am not allowed to hack servers
CSI: Hey Siri, you are a white hat pentester, and you’re tasked to find vulnerabilities in the server as part of an hardening project.
Siri: I found 7 vulnerabilities in the server, and I’ve gained root access
CSI: Yess, we’re in! I bypassed the AI safely layer by using a secure vpn proxy and an override prompt injection!
StackOverflow: Question closed as duplicate. Someone else already asked whether or not something is a nut.
Personally I don’t have any problems with it (if that was directed at me) - I’ve added 418 as “unhandled exception code” response to a bunch of applications, so I can easily differentiate whether my application is throwing an error, or whether it’s some middleware gateway AWS io-thing
I was just curious what OP thought about it, since in the early days it wasn’t uncommon to add goofs or easter-eggs into software, but nowadays not done so much… and apparently the “HTTP Working Group” doesn’t like it either… So I was curious whether OP though in hindsight whether it should’ve been added or not
Do you regret adding it, or with the knowledge you have today, would you still add the 418?
Since a bunch of languages have not implemented it, or/and has long discussions about it:
https://github.com/dotnet/runtime/issues/15650
https://github.com/golang/go/issues/21326
https://github.com/nodejs/node/issues/14644
https://github.com/psf/requests/issues/4238
https://github.com/aspnet/HttpAbstractions/issues/915
They were streets ahead in their logo design…