It seems like SoundCloud is more like the Vimeo for audio. They provide free and paid versions just like Vimeo. I don't think I've seen the YouTube for audio yet.
I'm sorry but I don't see how reddit fits into this equation. It's laughable to compare the work that went into building Curiosity or Ubuntu with reddit.
Worth noting that Reddit doesn't have terribly many employees, so it can't represent too much waste even if all its employees were Nobelists. And given that Swartz was able to do so much after leaving Reddit, can we say that Reddit was a waste - even if we ignore the benefits to its actual users and all the enabled communities?
Ah the Leaderboard ;) The idea is really simple. People who are frequent watchers get rewarded with points and they show up at the top of the Leaderboard.
Really cool, and awesome implementation. I'm really digging the smooth transition on the infinite scroll. Also, the design and UI much better than the default bootstrap I've slapped on my app.
And I would always lean to the side of trust in people, I wouldn't expect you or most people here to abuse it.
Its a little bit of a pet hate, the suggested linking to JavaScript files in another persons repository. The worst was the HTML5 Shim, for a long time they suggested linking directly to their svn repo, fortunately they don't now. It was about the same time people started thinking about using the google cdn for javascript libraries and so people just did it thinking they were helping their page load times when in fact they were compromising the security of their users and themselves.
Using Google CDN places no more trust in Google than using Google Analytics or AdSense. Unless your site handled sensitive data or is mission critical, I believe it's reasonable to trust Google not to do anything malicious.
It's worth noting that the same issue exists with Chrome extensions. I wonder how strong a Google password the authors of popular Chrome extensions have.
Just thinking about this, what's needed is some kind of trusted public cdn that you can send files to but cannot change so that library writers can point towards a cdn hosted version of the library without running one themselves and removing security vulnerability.
I suspect that JS that didn't depend on the page-load to trigger it would work too. I had never considered looking at JS-enabled pages though. When I wrote my bookmarklet, I just needed to view static documentation.
Edit: I found a page with only on-click JS events, and they didn't work. Oh well...