Blu-Ray To Allow Users To Make 'Copies' -- With Lots Of Strings Attached

from the asterisk dept

"Beginning next year, studios and other content holders will be required to give consumers the ability to make one copy of any Blu-ray Disc they buy," says the article (via Engadget). Sounds great -- movie studios and others finally realizing that people should be able to freely back up DVDs they legitimately purchase. The devil, of course, is in the details. While discs will have to support this "managed copy" feature, it will require new hardware, and there's no mandate that DVD player manufacturers include support for it at all. The copy, as you'd expect, is all DRM'ed up, and in order to make the copy, the Blu-ray player will have to connect to an "authorization server". This is the sort of model that's caused lots of problems in the past, when companies decide to pull the plug on the servers, rendering the feature useless. But the biggest potential problem with the feature is that movie studios and others will be free to charge whatever they wish for it. That means this really isn't a backup or a copy at all, it's simply the distribution means for the latest incarnation of the entertainment industry's favorite business model: getting people to pay for the same content over and over. That's why the studios want to block things like Real DVD -- not because they'll increase piracy, but because they cut off the only business model the studios can see for digital content.

Carlo Longino is an expert at the Insight Community. To get insight and analysis from Carlo Longino and other experts on challenges your company faces, click here.

36 Comments | Leave a Comment..

Much Ado About Nothing: The Rise And Fall Of HuddleChat

from the harping-on-huddlechat dept

If you've heard of HuddleChat at all, you already know about its demise. Put together by a few Google engineers in their spare time, the web chat application was used to showcase Google's newly-announced App Engine offering. There was just one problem: it was nearly identical to 37Signals' Campfire, a well-known SaaS web chat application. 37Signals gave some petulant quotes to ReadWriteWeb about the situation, and shortly thereafter Google pulled the app down.

As Om Malik has pointed out, this is all a bit ridiculous. AJAX/Comet chat is a fairly simple feature to implement. If my fellow participants in the Web 2.0 economy are counting on earning their keep via a collective conspiracy to make our jobs look harder than they are, we're all in deep, deep trouble. There's additional potential irony here, too, given that 37Signals has been accused of ripping off others' work to create Campfire in the first place.

But while this incident may prove portentous to the long-term prospects of the 37Signals business plan, it's hard to see how it could mean anything for Google. Breathless declarations that "many in the developer community [will] view Google App Engine as a Xerox machine for copycat product developers" are downright laughable. Google's decision to kill HuddleChat makes good PR sense, but it's inconceivable that many cost-conscious, Python-friendly startups would give up on App Engine over this minor blog imbroglio. As in many other respects, Amazon Web Services will likely provide the relevant template for these issues, and so far AWS has wisely avoided getting dragged into policing its users' apps.

Of course there's a lot of speculation that App Engine will include a free offering, and for that reason it may attract more troublesome users than EC2 currently does. But even if Google finds itself obligated to fight more griefers, phishers and spammers than Amazon does, it seems certain that they won't waste their time arbitrating squabbles over who called dibs on which trivial featureset. Sadly, that will remain for the courts to decide.

Tom Lee is an expert at the Insight Community. To get insight and analysis from Tom Lee and other experts on challenges your company faces, click here.

7 Comments | Leave a Comment..