from the crash-override dept

If you follow video game news as I do, you probably came across a fascinating and somewhat thrilling series of speculative stories revolving around a game called Spintires, which is being sold through the Steam platform. The driving game had been selling for some time, and selling fairly well, when all of the sudden it stopped working. Just like that, the game was crashing all over the place. Some sites, including this later-updated Gamasutra post, began digging into a wellspring of conspiracy theories about purposeful sabotage by the developer over money disputes with the publisher.

There may be something rotten in the state of Spintires, as the game's players have taken to Reddit and its official forum recently to complain about alleged "time bombs" hidden in the code by the game's developer that are rendering it unplayable.

The reason that a conspiracy theory like this found purchase rather than being laughed away was the rocky history between the developer of the game, Pavel Zagrebelnyy, with the game's publisher, Oovee Game Studios. Just a week before the crashing of the game began, Zagrebelnyy had been participating in interviews with sites and offering up less than flattering comments about Oovee.

"They owe me a s***load of money according to our contract," Pavel tells me in a new interview. "But I don't have any leverage because my judicial skills are zero. I haven't had a meaningful communication with Oovee for many months (maybe a year)."

Oovee, in the same post, acknowledges that it has been late in paying Zagrebelnyy, but promises that this will be corrected. A week later, the game of Zagrebelnyy's that Oovee published is suddenly broken and unplayable. At that point, Oovee released a statement, acknowledging that the crashes were a widespread issue and stating that those crashes were "date-related." The internet took that statement and ran with it, extrapolating it into a tale in which Zagrebelnyy had inserted time-bomb bits of code into the game that could be weaponized to cause it to crash on certain days or within certain date-ranges if he were so motivated, say by a lack of being paid by the publisher.

But that speculation and the conspiracy theory behind it then crashed upon comments from Zagrebelnyy and Oovee, which acknowledge to the theorists that, naaaah, it's just another case of anti-piracy efforts fucking things up for all the legitimate customers.

Zagrebelnyy gave the following response:

"Well, I dont understand who and why started the rumours of sabotaging - apparently they are based on reverse engineering Spintires code? Anyways, publisher (Oovee) have the source codes so they know (they should) I didn't sabotage Spintires - there is no such code! But there is in fact a time-related bug (a self-check uses time functions to see if game wasn't cracked by pirates) which was not fixed in time (because we have little to no communicating with Oovee.)"

And Oovee:

"We are aware of recent press speculation relating to sabotage of the spintires game by the lead developer Pavel. We wish to express our displeasure at this speculation and totally refute these and other recent allegations. It is a shame that some press are reporting this without talking to us, and even saying in some articles they are yet to talk to us. The situation on the bug is that we became aware of a major bug last week that caused the game to stop for some users."

And so another conspiracy theory falls, this times at the hands of faulty DRM. I'll put this here so nobody has to in the comments: never blame malice when incompetence is just as likely. Or maybe just blame DRM always and for everything. You're going to be right a decent amount of the time.

from the damaged-whose-reputation? dept

By now you've probably already heard about how the local Fox affiliate here in the Bay Area of California last week broadcast what it apparently believed were the names of the four pilots on the Asiana Air plane that crashed on landing at San Franciso Airport a week ago.

Almost everyone I've spoken to about this is stunned that no one realized these were obviously fake, racist names. You could maybe see one of them getting through, but all four? And it's not like this is in an area without a large Asian population. Nearly 25% of the population in this region is of Asian heritage. You'd think someone would have caught that these were fake before it went on air. But, no one did. If you haven't seen the video of the newscaster reading out those names, it's really quite incredible:

As you might imagine, KTVU quickly apologized, blaming the National Transportation Safety Board (NTSB) who it insisted had confirmed the names. At first the NTSB insisted that it had nothing to do with it, saying that "we do not release names" ever. However, a few hours later, the NTSB was forced to issue a statement apologizing, and saying that a summer intern, who was acting way, way, way outside the scope of his authority, had confirmed the names:

Earlier today, in response to an inquiry from a media outlet, a summer intern acted outside the scope of his authority when he erroneously confirmed the names of the flight crew on the aircraft.

The NTSB does not release or confirm the names of crewmembers or people involved in transportation accidents to the media. We work hard to ensure that only appropriate factual information regarding an investigation is released and deeply regret today's incident.

Appropriate actions will be taken to ensure that such a serious error is not repeated.

Of course, the NTSB has also said that the names "originated" with KTVU and that the intern was "trying to be helpful." Either way, the end result was pretty clear: KTVU (and, to some extent, the NTSB) were quickly mocked widely online.

Asiana said Monday that it will sue a San Francisco TV station that damaged the airline's reputation by using bogus and racially offensive names for four pilots on a plane that crashed earlier this month in San Francisco.

Yes, the use of those names was racist and offensive. And, yes, it was absolutely ridiculous that it made it on the air. But it's almost as ridiculous to then file a lawsuit over such a thing. Asiana is going to have one hell of a time proving any "damage" to the airline's reputation from that report, as opposed to, I don't know, the actual crash landing. It seems that Asiana's reputation is already hurt, but not because of any fake names, but rather for its inability to properly land an airplane.

The whole reason the names became a story was that basically everyone who didn't work at KTVU knew they were fake and offensive names. No one actually thought that they were real. There was no damage done to Asiana from those names being used. The damage was to KTVU's credibility (not to mention the credibility of whoever hires summer interns at the NTSB). KTVU and the NTSB have both apologized, and Asiana should focus on making sure its pilots can land their planes rather than suing over this.

from the how's-that-working,-then? dept

We've been suspicious of whether or not "driving while yakking" laws actually do any good. There are already laws against reckless driving, and picking out specific driving distractions doesn't seem likely to change things, since people just switch to other distractions. A study back in 2006 found that driving while yakking laws don't make the roads any safer, and a brand new study has apparently surprised researchers in showing no impact whatsoever on crash data even as studies show that fewer people are holding phones to their ears while driving (thanks Chirag). Now, there could be plenty of reasons for this -- such as that people are just switching to ear pieces which can be just as dangerous. Or it could be that common claims about driving while yakking leading to more accidents are wrong. Or it could be more complex, with other variables having an impact, but which is hidden in the data. Either way, it certainly seems worth investigating more seriously. If the goal is better road safety, then we should make sure that the laws actually lead to that result. If they don't, then it's important to understand why not.