Sam writes "A former Ubisoft exec believes that Sony will not be able to combat piracy on the PlayStation 3, which was recently hacked. Martin Walfisz, former CEO of Ubisoft subsidiary Ubisoft Massive, was a key player in developing Ubisoft's new DRM technologies. Since playing pirated games doesn't require a modchip, his argument is that Sony won't be able to easily detect hacked consoles. Sony's only possible solution is to revise the PS3 hardware itself, which would be a very costly process. Changing the hardware could possibly work for new console sales, though there would be the problem of backwards compatibility with the already-released games. Furthermore, current users would still be able to run pirated copies on current hardware." An anonymous reader adds commentary from PS3 hacker Mathieu Hervais about Sony's legal posturing.

MyNoSQL has up an interview with Ryan King on how Twitter is transitioning to the Cassandra database. Here's some detailed background on Cassandra, which aims to "bring together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model." Before settling on Cassandra, the Twitter team looked into: "...HBase, Voldemort, MongoDB, MemcacheDB, Redis, Cassandra, HyperTable, and probably some others I'm forgetting. ... We're currently moving our largest (and most painful to maintain) table — the statuses table, which contains all tweets and retweets. ... Some side notes here about importing. We were originally trying to use the BinaryMemtable interface, but we actually found it to be too fast — it would saturate the backplane of our network. We've switched back to using the Thrift interface for bulk loading (and we still have to throttle it). The whole process takes about a week now. With infinite network bandwidth we could do it in about 7 hours on our current cluster." Relatedly, an anonymous reader notes that the upcoming NoSQL Live conference, which will take place in Boston March 11th, has announced their lineup of speakers and panelists including Ryan King and folks from LinkedIn, StumbleUpon, and Rackspace.

KingofGnG writes "The classics, by definition, never go out of fashion, let alone if they are the graphic adventures of past decades. The preferred tool of true adventurers is ScummVM, software that works as an interpreter between data files of such adventures and modern operating systems. 6 months after the release of version 0.12.0, developers have now delivered a new main release of the virtual machine, which includes novelties both for the interface and supported games."

Brett Glass writes "Feel like you're stuck with a no-win choice between expensive cable modem service and slow DSL for Internet? Currently using satellite, with long latencies that make it impossible to do VoIP or interactive gaming? One of America's best kept secrets, so it seems, is the wide coverage of WISPs — terrestrial (not satellite or cellular) wireless broadband Internet providers. The linked article gives an overview of WISPs and provides a handy map showing their nationwide coverage (more than 750,000 square miles of the continental US — and only about one third of the WISPs in the US are on the map so far). Most WISPs are small, independent, consumer-friendly, and tech savvy, making them a better choice than big, corporate ISPs who can't even tell a penny from a dollar."

Gamasutra reports that Jolt Online Gaming is teaming up with Activision to revive the Zork franchise in the form of a casual, browser-based MMO. The Legends of Zork website provides some basic background information: "The Great Underground Empire has recently fallen and the land is in disarray. The Royal Treasury has been sacked. The stock market has collapsed, leading even mighty FrobozzCo International to fire employees from throughout its subsidiaries. A craze of treasure-hunting has swept through the remnants of the Great Underground Empire. The New Zork Times reports that trolls, kobolds and other dangerous creatures are venturing far from their lairs. Adventurers and monsters are increasingly coming into conflict over areas rich with loot. It's a dangerous time to be a newly-unemployed traveling salesman, but it's also a great time to try a bit of adventuring." Gamasutra also has a brief interview with Jolt's CEO, Dylan Collins. There's no word yet whether or not players are likely to be eaten by a grue.

snydeq writes "Powering down servers to conserve energy is a controversial practice that, if undertaken wisely, could greatly benefit IT in its quest to rein in energy costs in the datacenter. Though power cycling's long-term effects on server hardware may be mythical, its effects on IT and business operations are certainly real and often detrimental. Yet, development, staging, batch processing, failover — several server environments seem like prime candidates for routine power cycling to reduce datacenter energy consumption. Under what conditions and in what environments does powering down servers seem to make the most economic and operational sense, and what tips do folks have to offer to those considering making use of the practice?"

Technologizer writes "Apple's new MacBook is a significantly different machine than its predecessor — a slicker laptop at a higher price point. But does it carry a large price premium over similar Windows PCs? I did a painstaking spec-by-spec comparison versus three roughly comparably-configured Windows machines, and came to the conclusion that the value it offers for price paid is not out of whack with the Windows world." The article uses the phrase "Mac tax," which one commenter points out is a recent Microsoft marketing canard.

TristanBrotherton writes "Cloud computing seems to be a good choice for startups like ours, looking to scale easily with users. (We're providing a series of Web services, assets, and Web applications to users of our mobile client.) There are the obvious choices of Google, Amazon, and smaller shops like EngineYard. The biggest issue we have in choosing cloud computing to run our applications is trust in their robustness. If the provider goes down, we suffer. In traditional hosting environments we mitigate this with multiple sites / vendors. It's not really feasible to host on multiple compute services, so I wondered if a better option might be to set up a small (perhaps two servers) origin infrastructure in a traditional manner at a datacenter, running our applications, but then send excess load, or in the event of our origin servers failing, all load, to compute services. This would give us the best of both worlds. Has anyone done this, or had experience in designing Web applications to scale seamlessly across both environments? Is there particular load-balancing hardware we can use to do this?"