Avoiding your own Logies leak moment

Melbourne newspaper the Herald Sun told the world who had won the Gold Logie before it had even been announced. It's hardly the world's most serious data breach, but it was easily avoidable.

Melbourne newspaper the Herald Sun told the world who had won the Gold Logie before it had even been announced. It's hardly the world's most serious data breach, but it was easily avoidable.

This morning, a war of words seemed to be breaking out over who was to blame for "leaking" the result of Australia's top award for television.

"At no time did the Herald Sun publish the name of the winner on its website, iPad app or in Twitter," the newspaper reported. "A link to an embargoed story naming the winner was momentarily created and published by Google."

However, Google pointed the finger back at the Herald Sun, cheekily tweeting a link to information on the Robots Exclusion Standard and the robots.txt file that would have prevented the news story from being indexed against the newspaper's wishes.

On this week's Patch Monday podcast, web developer Dave Hall, principal engineer at Technocrat, explains how robots.txt and another file, sitemap.xml, could have prevented the Herald Sun's problem, and speculates about what went wrong.

These files should be part of every well-run website, he says.

You'll also hear how Herald Sun editor Simon Pristel had already admitted on radio station Triple M that it was all down to a technical glitch at the newspaper's end. The speculation that Google was somehow inside the Herald Sun's systems came from the Triple M presenters.

To leave an audio comment on the program, Skype to stilgherrian, or phone Sydney 02 8011 3733.

Running time: 22 minutes, 21 seconds

Newsletters

You have been successfully signed up. To sign up for more newsletters or to manage your account, visit the Newsletter Subscription Center.
Subscription failed.
See All