News for hackers. Stuff that matters.

A comment on Stack Overflow Outage Postmortem. Parent comment

Re:Stack Overflow Outage Postmortem by OJFord on Wednesday July 20, 2016 @06:25PM (#12133006)
It was in a multiline code block, so it just had a tonne of horizontal scroll.

See the edit: http://stackoverflow.com/revisions/38484433/2

[ Parent | on HN ]
Re:Stack Overflow Outage Postmortem by hinkley on Wednesday July 20, 2016 @09:07PM (#12133816)
If he had used tabs instead of spaces this wouldn't have been a problem.
[ Parent | on HN ]
Re:Stack Overflow Outage Postmortem by scrollaway on Wednesday July 20, 2016 @11:40PM (#12134471)
Or at the very least, trim whitespace on save :)
[ Parent | on HN ]
Re:Stack Overflow Outage Postmortem by skeletonjelly on Wednesday July 20, 2016 @07:41PM (#12133443)
Still hasn't killed as many characters as GRRM
[ Parent | on HN ]
Re:Stack Overflow Outage Postmortem by skeletonjelly on Wednesday July 20, 2016 @07:40PM (#12133436)
Good find! Where did you see this? Or was it in the comments via Nick Craver?
[ Parent | on HN ]
Re:Stack Overflow Outage Postmortem by OJFord on Thursday July 21, 2016 @02:57AM (#12135222)
The article said:

    > The malformed post contained roughly 20,000 consecutive
    > characters of whitespace on a comment line that started
    > with -- play happy sound for player to enjoy. For us,
    > the sound was not happy.
So I just searched:

    https://www.google.co.uk/search?q="play+happy+sound+for+player+to+enjoy"+site%3Astackoverflow.com
[ Parent | on HN ]
Re:Stack Overflow Outage Postmortem by GnarlyWhale on Thursday July 21, 2016 @12:40PM (#12138056)
"deleted 20507 characters in body"

Hahaha

[ Parent | on HN ]