mihar

Yep.

Hey, good questions.

A.) You can't download the video, because videos are owned by YouTube and their creators. We just overlay the audio and play the original videos. You can embed the resulting videos though.

B.) Every video has a one-pager with a permalink, like on YouTube.

I agree. Less useful for you, more useful for someone who likes HAML, SASS and CoffeeScript.

I agree that this not an optimal start point for someone who just heard of Backbone.js.

I do think, though, that if someone will still be a bit confused how to stitch things together after reading and poking around for a while, this sort of skeleton could provide just enough insight.

I released this as something that seemed useful to me and in that context should be useful to at least someone else.

If you're unfamiliar with the Ruby world, the usefulness somewhat disappears, but that's said in the prerequisites.

Agree. But I doubt any beginner in web development will be touching Backbone.

It's one thing to prompt the user when you start recording and another to need to go to chrome://flags.

Permissions for privacy invading features should IMO have a unified interface like they have in the OS like Mountain Lion.

It works better as in "is supported on more platforms". But here we were solving the Chrome problem specifically.