I'm not a weed, noooooo...

GitHub really needs to step up its CORS game.

I am calling GitHub's official API. APIs are not supposed to have any CORS restrictions.

Why?

Cuz they are supposed to be called by people building various apps, and it does not make sense to limit the source of the network requests

Their API allows CORS requests from everywhere, what do they need to "step up"?

Besides the tree of these and those comments, do you have any other links to relevant subjects/writings?

@muratbuffalo Your graph has left the building. http://imgur.com/a/kKkjC

I'll append this with a link to https://www.hioscar.com/ as a great exaple of how simple it can be.

Watchlisted — they have an amazing hacker potential that could make a dint in the triade of Last.fm, Rdio and Spotify, what can I say for HypeMachine, Exfm, 8tracks and all the other youngsters...

There still isn't much to go on with speculation. It is safe to assume though Twitter won't be going near music-distribution — their tap into the existing infrastructure of Digital Music is a great example of "new way of building", which is frankly: "not inventing the bicycle all over again".

I'm wishful.

It's actually in Standby: https://music.twitter.com/ (there is already a HN submission for it — https://news.ycombinator.com/item?id=5539041)