That is some mean-spirited internetting right there.
From the title I was hoping it was a 500 page that git blames the backtrace and tells the user who specifically messed up.
That's a fascinating idea, even if it's not made public to the end user. Getting the git blamed stacktraces mailed to the dev team would be interesting!
Hahaha! It's definitely evil, but a funny evil.
Looks like it thinks my iOS chrome is safari. The demo does not look at all like a chrome Internet connection error screen