Thanks for the review, we appreciate it!
I believe the Github rate limit has reset, so you should be able to try again :)
Thanks Kevin - I'm flattered!
The GitHub rate limits might have reset now. Hope you get a chance to try again!
I went back to the site, but this is all I see:
Are you in any GitHub organizations?
Hmmm, ok. Chances are this is due to the fact that we have exceeded another rate limit :(
Hi Kevin, thanks so much for your feedback!
Yes, the "refresh problem" is due to our offline encoding using ffmpeg and a coffee-rescue worker. We didn't put a system to notify user when tracks are encoded and thus you must refresh as soon as they are ready.
Thanks for your vote! We didn't have enough time to give enough due diligence towards establishing some really solid performance benchmarks. That's something that we'll be rolling out, and using as a guideline towards figuring out how to further optimize various use-cases. We felt it would be better to leave detailed benchmarks out altogether (except with some mentions of theoretical gains) rather than hack together some data points that may turn out to be misleading. Instead we focused on hammering on some core use cases and making the API and implementation solid.
Definitely keep an eye on the Github repo after the competition, where we'll be updating both the module (adding more tests and such), as well as beefing up the demo site to include more performance benchmarks and example use cases so newcomers can grok the library with ease.
Mr. Dynosaur like you back.