-
Website
http://avc.com/ -
Original page
http://www.avc.com/a_vc/2009/06/the-watch-later-project.html -
Subscribe
All Comments -
Community
-
Top Commenters
-
ShanaC
1239 comments · 73 points
-
daryn
216 comments · 15 points
-
kidmercury
835 comments · 104 points
-
howardlindzon
207 comments · 71 points
-
Charlie Crystle
205 comments · 36 points
-
-
Popular Threads
-
Top Tracks of 2009
14 hours ago · 49 comments
-
Top 10 Records Of 2009
1 day ago · 73 comments
-
Getting Computer Science Into Middle School
6 days ago · 281 comments
-
Open APIs and Open Standards
1 week ago · 207 comments
-
Thoughts on Blackberry Fail
4 days ago · 77 comments
-
Top Tracks of 2009
you save videos to playlists, each playlist you generate is an RSS feed which you can sync to your itunes and presto!
A couple notes:
Everything is public in L8R, since the source was initially public (in order to avoid registration, I uses the global rss feed for the 'l8r' tag). I went the simple route, which leaves everything except consuming/converting the bookmarks, to the client.
Also, in addition to the website and boxee, your L8R stream is also available as RSS, which can be opened in iTunes or any other client that supports it. There may be a bug with this right now, as I tweaked a few things to be boxee specific during development, but I'll give it some love tonight.
Similarly for things I'd like to listen to, such as an episode of a podcast to which I'm not subscribed, I use a _listen tag. Delicious provides feeds for tags…
Both of those feeds run through a Yahoo Pipe (video or audio), which cleans things up a bit. I subscribe to those Pipe feeds in iTunes (or Canola, etc.) to create my own custom channels. I've even set up a custom podcast channels for some close friends, so when I hear something I think they'll like, all I have to do is tag the MP3 for them, and it appears in their player of choice!
Also have the offset in the bookmark so if I started listening to something I can resume later. Just like what I do with podcast on my iPhone, but stored in the web. That way I can continue later on any of my devices.
Boxee offers the first thing you want right now
What I would really like though, is an integrated cloud app that takes all my links that I save and be able to scan through them easily on the screen like PicLens or the iPhone does for photos. These links might come from a variety of sources, including Twitter, email, blogs etc but currently bookmarking and accessing them is pain. None of the services such as Delicious or Magnolia really works for this, nor does Google Reader.
What would be cool is a Touch screen iMac and the ability to scan queued videos or weblinks easily like PicLens or the iPhone. Now that would be sweet.
This is how additional "layers on the stack" drive value in the underlying applications.
This has been really cool to see unfold in real time.
Opening a boxee account now...
I hope to add new features as I have time, including a web interface for viewing and managing your queue. Another killer feature would be the ability to share your queue. When developing Boxqueue, I had a decision to make: Do I make the feed public and viewable by everyone, or do I make it private, so that only the user can view it. I went with the private route (or privacy through obscurity, as there can be no "private" feed without authentication), because I wanted the ability to automatically remove items from your queue.
However, I think it would be great if Boxee offered OAuth or some other sort of authentication on RSS feeds. That way, I could share a public view of my queue with the rest of the world, but I could also have a private view that removed the videos after I watched them. (Note: I plan to add an option to toggle whether or not a video is removed from your queue, so you can share your queue if you like).
This sharing aspect could also come into play when adding items to a queue. A site could set up a public bookmarklet/extension, which members could use to add interesting videos to a single feed. Individuals could then watch the videos submitted by all members!
One of the biggest technical challenges for Boxqueue and sites like it is how to get at the data for videos across various sites. Each site has its own method of embedding a flash video on a site, and the techniques used by Boxqueue might not always discover the video, even though the video plays just fine in a browser. This is where open standards and APIs are useful. Boxqueue works great with YouTube because I leverage the YouTube Data API to load the canonical information about a video. Vimeo doesn't offer an API per se, but if you view source on any of their video pages, you can find very useful information embedded in the metadata (along with some ascii art)! If you are a small site looking to share your videos across the web, providing this information in an easy to parse manner is very helpful.
This concept of an API can also apply higher up the stack. Once a video is added to your queue, Boxee's player controls may not always work with the video. This means you're stuck watching a video you can't pause or play! It'd be great if there were a standard way for videos to indicate where their play/pause/ff/rewind buttons were, so that regardless of the video source, any player could control them. HTML5's "video" tag has support for a "controls" attribute, but it could go deeper and offer support for individual control types (maybe the "video" tag could contain a "control" subelement, with standard "rel" parameters for each control type).
Anyway, these were just a few of my thoughts when working on Boxqueue. I hope the site proves useful to you and your readers. Thanks again for the link!
Having some way to do simple folders or tagging is going to be valuable otherwise you end up with the current Kindle problem where once you start adding more than books, like articles you want to read the simple list view by recent become tedious to manage.
As for pricing if it really worked seamlessly I would expect the bookmarking and online viewing pieces to be free or add supported and would pay to have access on various distributed points. ie. $20 a year to have the App on Boxee, $5 a year to have it on iPhone, etc...
Giving the TV viewer a "web remote" to access on a PC, tablet, phone that controls VOD/DVR/L8R-style viewing is likely the only way to make great strides in managing million of files for TV. We're gonna need a two screen solution.
For Boxee right now - it might make sense for them to hook up with mike robertson's mp3tunes. Its locker does video too, and offers "side loading" which actually makes copies of the online files you find.
But you're right on the mark (in regards to viewing experience) where you talk about what the "watch later" tool should do and that no one has "nailed it" yet. You previously talked about how Tivo has similar capabilities but that there is too much friction. What that ultimately comes down to is C.S.S. aka convenience, speed and simplicity. An application that can convey C.S.S. in the best way will ultimately gain the most traction because it appeals to all audiences despite their preferences in videos and experience in technology. Something that is hardcore enough for the tech savvy yet something that average web users can pick-up without much thought.
Right now watching video is a lot like having a car with only manual transmission and a 4 cylinder engine, but racing enthusiasts and people who just like driving want something more convenient, speedier and simpler to pick up. Therefore, the best application is one that can turn a world with only manual transmissions and 4 cylinder engines into one with automatics and 6 cylinders or more. Therefore, a video bookmarking app should be convenient when cruising the web and allow bookmarking from as many sources as possible. It should be speedy in how it saves and collects videos, whether it's only one video or multiple ones. Finally, it needs to be simple enough so that anyone can use it but its features need to be powerful enough yet conveniently organized for the user.
I think we've got a good combination for you. Out of your 4 requirements we've got 2 set-up and the other 2 waiting in the wings. But the first step is to get the first 2 requirements right because if those two are wrong that's a ton of wasted development on something unusable.
Twitter says that it will shut down for maintenance tonight. Can you, please, talk to them to postpone it. Many are concerned with shutting down the twitter-feed from Tehran and that it can have demoralizing effect on the demonstrators.
Thanks!
Definitely would need something that makes adding a video to the queue as simple as a command-D (ala Delicious) or a right click. Any more effort and I'll simply be too lazy to use it.
The key "desires" of consumers around "play later" are right in our wheel-house.
We have been hard at work on a platform delivering "play later" leveraging our three key consumer-centric benefits of "Content, Control and Community." It's great to see this emerge and to see so many people tinkering with different aspects of the solution. We're set for launch this summer.
Let's keep the conversation going here. We are looking forward to hearing what people want on their "wish list."
Matt
they publish their APIs so you can develop plugins.
There's a plugin I use on XBMC which allows me to do just that (playing sequentially or random a playlist)
With two mouseclicks I can watch on a mobile phone and sync my iphone and furthermore, there's sharing among family and friends.
(It's easy to use in on your mobile phone because it's designed very phone-friendly.)
I currently use a few different methods, such as bookmarking the links in Firefox, sometimes in a bookmarks folder named after the current date (not a good way I feel, as it doesn't let you know later what pages were in that list), sometimes save the links from that bookmark folder in a text file (with some links labeled with a tag system of my own), save that text file both on my hard disk and in my email (so I can access it from anywhere), sometimes save to my Delicious page, have checked out some web services for bookmarking, and so on.
All in all, it's a hotchpotch of methods, and I find none of these methods entirely satisfactory or efficient and convenient enough. Of course, I've not fully evaluated the pros and cons of them yet - that is an ongoing exercise. So I was interested in your Watch Later idea and will follow this thread. If I come up with any idea that I find more useful I'll mention it here in the comments.
Thanks, Vasudev.
Have you tried instapaper for posts you want to read later?
This particular subject has gone back and forth over the past few years. We've had a "user queue" for a long time, which has elements of what you are talking about (http://blog.mefeedia.com/index.php?s=queue - recently renamed to just "watch"). I think this is what you are alluding to, rather than search or tag feeds.
User queues are useful, depending on the type of video. Three good examples would be:
1. Serial video - i.e. users want to know when the latest episode of Lost is available and "queue" it to watch later. This is where the Subscribe/Queue mechanism works best.
2. Rapid playlisting, such as one might do in a video search for a topic of high interest to you.
3. Friends' recommendations where you can queue up everything that is recommended by friends (i.e. from Twitter, FF, YouTube, FB, etc...)
However, for a lot of user videos or viral videos (which, i would argue, is still the majority of mainstream video consumption right now), this isn't as useful as that is typically more of a "watch now" experience rather than a "watch later".
Based on what we have seen, search feeds (and to some extent, tag feeds) work great for queuing. Recent news and events are great applications of this. For example, having a constant, auto-updating search stream of new videos on the Iran Elections is very conducive to a lean-back experience where you can flip from video to video.
There are a lot of variations on this, of course... i am looking forward to the continued discussion.
and options, but basically it just bookmarks the thing so you can go
back to it later. It's that on steroids.
http://www.ideashower.com/support/read-it-later/
-- Dan Weinreb