How Diablo III's Always-On Internet Requirement Makes It A Better Game 
Back From Hell: The First Seven Days Of Diablo III 
Which Hardware Works Best With Diablo III? 
Nine Compelling Diablo III Features That Didn't Make The Final Game 
Blizzard Apologises For Diablo III Launch Mess, Delays Real-Money Auction House 
How I've Been Playing Diablo III, You Know, Aside From Sporadically 
It’s easy to sit back and scoff at “review bombing”, as we saw last week when Blizzard released a broken Diablo III. Flooding Amazon to give zero stars to something others have called 10/10, sure, that’s not a legitimate review. And people staging a sit-in aren’t there to legitimately patronize a public accommodation, either. But a sit-in is a legitimate form of protest. And I think a review bomb is, too.
Less than two weeks from its launch, Blizzard’s Diablo III is already a financial success (despite the fact that they might not be totally clear on how to measure it.
In your basement, cuddled up next to your cat, on a mountain and now on a tablet.
In addition to launch-time connectivity woes, Diablo III has also been hit with claims of hacked accounts and missing items, adding a layer of confusion and worry to an already confusing, worrisome launch.
Last week’s rough launch of Diablo III neatly illustrated the biggest problem with the game’s ‘always-on’ internet requirement. It was a reminder that consumers have lost a portion of their ownership of the game, that we no longer have complete control even over whether or not our game will start.
