Activity

• By them
• On them

• 
  1 day ago

  Peter Kirn likes Resolume Avenue 3 Introduction
• 
  3 days ago

  Peter Kirn likes Alpha Rainbow
• 
  12 days ago

  Peter Kirn commented on embedded vimeo vids keep crashing browser (safari, firefox 3 on

  Confirmed here, as well. Multiple sites (possibly all WordPress, but...) and the current build of Flash. Crashes tested in FF3 (Mac, Windows), Opera 9 (Mac), IE8 (Windows)...
• 
  22 days ago

  Peter Kirn likes Building and Using a Reaktor Grain Delay in Kore 2
• 
  22 days ago

  Peter Kirn likes Cranford Rose Garden Time-lapse at Brooklyn Botanic Garden
• 
  1 month ago

  Peter Kirn likes Peter Dines' tutorial on scripting and modulation in Kontakt 3
• 
  3 months ago

  Peter Kirn subscribed to Create Digital Motion: Visualist and VJ Community
• 
  3 months ago

  Peter Kirn likes topography
• 
  4 months ago

  Peter Kirn likes Webcam: motion detection, Watereffect
• 
  4 months ago

  Peter Kirn commented on Flash object timeline

  I'm sorry; I should have rephrased that. What I was trying to say is, if the API isn't *deep* enough, developers wind up just replicating what the site does already. And I will argue that, if you go and make an API, the ideal would be for developers to come along and provide a way of looking at and interacting with your content that you didn't think of. Now, obviously, that can't be methods that don't have *some* life somewhere on the site ... backend or otherwise. And it doesn't mean you "crippled" the site; it just means someone else might think of something you haven't yet in terms of how you look at the content and the data associated with it. Nothing's there that isn't already there, it's just that they would provide a different way of seeing what's there. And I'd say our job as developers is to take those methods and provide some view of that content that gives the content new usefulness beyond what it already has, that extends the site. But before I overcomplicate what I was saying, I'm with pixelsumo -- if you can open up the player itself, then I think developers can provide some very meaningful stuff. And it doesn't have to be complicated... just setting the playhead is really what I think we're looking for here. And that could be hugely powerful. Playhead position isn't the easiest example... another one would be how you take the data you've queried from Vimeo and try to give people a different view of what people are posting. So, for instance, you might want to go beyond just getting a list by tag, and try to triangulate tag information with what people like, when activity happened, etc. Right now, I think I could probably use the advanced APIs and put my money where my mouth is and build something that lets you, say, look at a 3D cluster of video thumbnails by tag, like, friend, other interconnections between videos. But there's another problem -- I need to be able to differentiate private from public information. And it looks like there isn't a graceful way to do that, beyond doing the query and getting an error message. (If I'm correct about that.) I'm not meaning to lecture here; I'm just saying -- I'm really excited about Vimeo for the long haul. So I'm enthusiastic about, even if it's just one simple method, anything that allows us to do something that interacts with the community beyond what the site does already, absolutely. Peter

Open Requests