Photo of worker adjusting a wireless access point.

Worker adjusting the wireless access point outside my window.

Featured Tag: Wireless

Main Tags
art blogging learning mac movies other politics science tech wireless

The PF HYPER Blog

Sunday, March 21, 2010
 
Viacom vs. YouTube

Google and Viacom (owner of MTV, BET, Paramount, and more) are fighting it out in court with Viacom contending that Google is no longer a "safe harbor" under the 1998 Digital Millennium Copyright Act and must do more to ferret out and remove copyrighted material -- like Viacom's. Viacom is supporting its case with some old emails supposedly proving that Google relaxed its copyright policies after its 2006 YouTube purchase and that it knew very well that YouTube was a pirate haven of illegal video goods. Let's not forget to mention the "sour grapes" component here: Viacom wanted to buy YouTube too and Google beat them out.

Whatever Google authorized in the past, in recent times they have added content ID tools to help companies identify and find pirated content on YouTube. They've done this to such a degree that they've fallen somewhat afoul of the Electronic Frontier Foundation.

One issue that has surfaced is Viacom "continuously and secretly" uploading its own stuff to YouTube (self-pirating?). (Viacom disputes this and claims it only happened a few times.) From the YouTube blog:

For years, Viacom continuously and secretly uploaded its content to YouTube, even while publicly complaining about its presence there. It hired no fewer than 18 different marketing agencies to upload its content to the site. It deliberately "roughed up" the videos to make them look stolen or leaked. It opened YouTube accounts using phony email addresses. It even sent employees to Kinko's to upload clips from computers that couldn't be traced to Viacom. And in an effort to promote its own shows, as a matter of company policy Viacom routinely left up clips from shows that had been uploaded to YouTube by ordinary users. Executives as high up as the president of Comedy Central and the head of MTV Networks felt "very strongly" that clips from shows like The Daily Show and The Colbert Report should remain on YouTube.
via youtube-global.blogspot.com

The Law Librarian Blog has a nice summary of points around these issues and links to articles in the last paragraph. Although I agree with Law Librarian that "neither party to the suit has any lock on legal or moral purity," if I had to choose a side to cheer, it would be Google. Although both companies are looking at revenues and bottom lines, Viacom is trying to control content distribution in a media market that arguably should be moved towards more sharing. YouTube on the other hand may not be perfect but it is involved in sharing content globally at no direct cost to producers. For me, that's very much a move in the right direction.

Posted via web from Peter's posterous

Labels: , ,


Sunday, November 01, 2009
 
Fluid for Wave: Instructions on building an app
I use a Fluid app to engage with Google Wave. The TC Wave has links to how to do this but the TC Wave is becoming harder and harder to navigate and find things. So here's the blog post with links to how to integrate Fluid and Wave and Growl.

Download Fluid then drop by Guillermo Rauch's devthought blog for how to create the app (plus a link to a very nice Wave icon to use for your Fluid app). Then if you're interested in Growl notifications when new messages arrive at your waves, install Growl and then add this script to your Fluid app. (Guillermo's page describes how to install a script in a Fluid app.) Growl notifications only work when your Fluid Wave app is open. 

I'm happy with the Fluid Wave app performance and I've had no serious problems. It can be slow but no slower than Firefox (3.0.15). I have heard Chrome is snappier but I don't think Google has released an official Mac OS X Chrome yet.

Please add any useful links about Fluid, Growl, Wave etc.

Posted via email from Peter's posterous

Labels: , ,


Wednesday, August 01, 2007
 
There's a spectrum auction around the bend and maybe we'll get lucky
The FCC will be auctioning off old TV spectrum in 2008 and they are hard at work today creating a set of rules for the auction. Past spectrum auctions are dominated by really big companies with lots of money (and lobbyists) and this auction will be no different except there's a new kid on the block named Google. And Google thinks the FCC should require openness:
  1. Open applications: consumers should be able to download and utilize any software applications, content, or services they desire;
  2. Open devices: consumers should be able to utilize a handheld communications device with whatever wireless network they prefer;
  3. Open services: third parties (resellers) should be able to acquire wireless services from a 700 MHz licensee on a wholesale basis, based on reasonably nondiscriminatory commercial terms; and
  4. Open networks: third parties (like internet service providers) should be able to interconnect at a technically feasible point in a 700 MHz licensee's wireless network.
Read the full post at the Google Policy Blog.

Yesterday the FCC voted to require 1 and 2. Sad not to have 3 which would have really opened up the spectrum but any openness is welcome. Of course, enforcement of the openness will be another issue.

Washington Post has a good article about the whole situation, Susan Crawford reports on the decision, and Paul Kapustka at GigaOm has a good summary of what happened yesterday.

Given that AT&T is happy about the decision (see the Kapustka link), it may be (as Susan Crawford feels) unenforceable.

Labels: , , , , , ,


Tuesday, March 13, 2007
 
Google Home Glitches
My personalized Google home page is experiencing some technical difficulties as is my wife's. Some of the feeds - Word for the Day, for example - aren't loading properly. Word is in really tiny text, smaller than any of the other feeds. Feed headings don't load at all in some instances, leaving a blank space. Or, they load but the link to the source is broken. Very odd.

A browser reload fixes it all. Are the G servers getting overloaded? Maybe resources have shifted to the new Google Doc pay service leaving the rest of us suffering.

Anyone else having problems?

Labels:



Powered by Blogger