Copyright and the Real Time Microblog Phenom
May 24, 2009
Liz Gannes’ “Copyright Meets a New Worth Foe: The Real Time Web” is an interesting article. You can find it on NewTeeVee.com here. Her point is that copyright, the Digital Millennium Copyright Act, and other bits and pieces of legal whoopdedoo struggle with real time content from Twitter-like services. She wrote:
If you’re a copyright holder and you want to keep up with your pirated content flitting about the web — well, good luck. The way the DMCA is set up means you’re always chasing, and the real-time web is racing faster than ever before. Analytics services are only just emerging that will tell you where your views are coming from on a semi-real-time basis. That’s especially true for live video streaming sites such as Ustream and Justin.tv. Justin.tv, in particular, has come under fire by sports leagues for hosting camcorded streams of live game broadcasts. The company says it takes down streams whenever it is asked to. But the reality is, often the moment has passed.
In short, information flows move more quickly than existing business methods. An interesting illustration of this flow for video is Twiddeo here. Government officials have their work cut out for them with regard to ownership, copyright, and related issues.
But…
As I read this article, I thought about the problem Google has at this time with real time content. Google’s indexing methods are simply not set up to handle near instantaneous indexing of content regardless of type. In fact, fresh search results on Google News are stale when one has been tracking “events” via a Twitter like service.
As important is the “stepping back” function. On Google’s search results displays, how do I know what is moving in near real time; that is, what’s a breaking idea, trend, or Tweet? The answer is, “I don’t.” I can hack a solution with Google tools, but even then the speed of the flow is gated by Google’s existing indexing throughput. To illustrate the gap, run a query for American Idol on Google News and then run the query on Tweetmeme.com.
Two different slants biased by time. In short, copyright problem and Google problem.
Stephen Arnold, May 24, 2009