How-To TechBiz WebApps

Migrating to the Newest Youtube API

You’ve got until August 30th, 2008 to migrate your code to the latest Youtube API. After that date, your current code base might not work.

I used 3 important coding concepts while working on migrating my Youtube Facebook App to the newest Youtube API:


The strategy pattern allows you to define common behaviors that will be shared among your set of classes. In this case, I’ve got a class for the old Youtube API, and a class for the new Youtube API. Although the URLs used for accessing the two APIs are different, I’ll define a method common to each class for accessing URLs. In this case it’s the setURL method.

In PHP I do this like so:

interface apiCalls

public function setUrl();


The factory pattern allows me to create an instance of an object for using the old API or the new API on the fly. Factory methods just return the new instance of an object.

$dynamic_fave = FaveFactory::Create(“cyphgenic”, ‘yes’, 2, ‘on’, ‘2.0’);
print $dynamic_fave->url . “\n”;

$dynamic_fave = FaveFactory::Create(“cyphgenic”, ‘yes’, 2, ‘on’, ‘1.0’);
print $dynamic_fave->url . “\n”;

If you take a look at the code I’ve got and compare the old version with the new one, you can also see that I’ve cleaned up the nested if-else statements with arrays.


      if ($showUploaded == 'on') {
        $method   = "youtube.videos.list_by_user";
      } else {
        $method   = "youtube.users.list_favorite_videos";


      $h_method['on'] = "youtube.videos.list_by_user";
      $h_method['off'] = "youtube.videos.list_by_user";
      $method = $h_method[$this->showUploaded];

Below are the links to the bits of the code that I had to migrate. I just use one particular method, setUrl() as an example.

You might be wondering why two classes for the old and new API. If any new features need to be coded, or bugs need to be fixed in either API, I can do so within a particular class, and not add more obfuscation to the code. The two classes don’t violate the DRY principle because each models a particular thing.

film TechBiz

Youtube Censors Won’t Censor Full Length Chic Flicks

Youtube’s censors hate geeks. You can’t watch the Matrix because it’s been removed, but ya, you can jack off all you want to all of Jane Austen’s books turned into movies. To me this is such a joke, but I think there’s an explanation:

You can no longer see a lot of the scenes from the Matrix on youtube:

Youtube hates geeks! No Matrix for you!


If it’s a chic flick like Pride and Prejudice or Persuasion? Guess what – you still can see the whole film in its entirety.


The makers of Merchant Ivory type films see their films on Youtube as advertising… maybe there are a few die hard cultural conservatives who see it as reviving a long-gone era of classism and good manners. The owners of the Matrix, Warner Bros., see films on Youtube as cutting into their profits. They probably hate all the radical lefty politics in it, too.

Can any insiders confirm this?

film TechBiz

Follow up to Full Movies on Youtube

In my last post, I talked about finding full feature length movies on Youtube. The only genre where I can watch a movie from beginning to end is historical fiction. Movies like Elizabeth and Pride and Prejudice are on youtube in their entirety. My only guess for the reason why is this: Historical Fiction movies don’t really make bank, so the studios don’t feel threatened by their “dead” movies being on youtube. Instead they see it as free advertising.