"To what purpose are powers limited, and to what purpose is that limitation committed to writing,
if these limits may, at any time, be passed by those intended to be restrained?"
-- Chief Justice John Marshall, Marbury v. Madison, 1803
As Hal noted below, we’re making progress on the civil liberties front. However:
Yesterday, in the Viacom v. Google litigation, the federal court for the Southern District of New York ordered Google to produce to Viacom (over Google’s objections):
all data from the Logging database concerning each time a YouTube video has been viewed on the YouTube website or through embedding on a third-party website
The court’s order grants Viacom’s request and erroneously ignores the protections of the federal Video Privacy Protection Act (VPPA), and threatens to expose deeply private information about what videos are watched by YouTube users. The VPPA passed after a newspaper disclosed Supreme Court nominee Robert Bork’s video rental records. As Congress recognized, your selection of videos to watch is deeply personal and deserves the strongest protection.
The Logging database contains:
for each instance a video is watched, the unique “login ID” of the user who watched it, the time when the user started to watch the video, the internet protocol address other devices connected to the internet use to identify the user’s computer (“IP address”), and the identifier for the video.
Google correctly argued that “the data should not be disclosed because of the users’ privacy concerns,” citing the VPPA, 18 U.S.C. § 2710. However, the Court dismissed this argument with no analysis, stating “defendants cite no authority barring them from disclosing such information in civil discovery proceedings, and their privacy concerns are speculative.”
This is the sort of thing I hope would be overturned on appeal. I can understand that Viacom thinks it’s protecting copyrighted material and looking for violators, but treating everyone like a criminal isn’t the way to go about this, as the recording industry can now attest.
Comments
Commenting is not available in this weblog entry.
<< Back to main