gmusicapi

Talk about bad journalism. That is not true. Google's All Access music streaming has _never_ been blocked by flash DRM restrictions. The raw MP3 streams have been available ever since its inception, as it has been included in Simon Weber's python google music API implementation [1] for about 5 months (which is a few weeks after All Access was announced). From that API it has been implemented in those 3rd-party apps like GMusic and Cloud Play. So, the only "bad guy" here is Google for not making an iOS app sooner. [1] https://github.com/simon-weber/Unofficial-Google-Music-API

I see non-sanctioned access like this as a huge boon to both the service and its users: it enables easy marketing, community-supported apps, easy research on what features users want, etc. I also think the fear of abuse is mostly unwarranted. If somebody wanted to steal your content or abuse your platform, they'd figure out a way to do so -- with or without an unofficial api (especially if all that's needed is http scraping). (disclaimer: I maintain https://github.com/simon-weber/Unofficial-Google-Music-API)

Google's authentication schemes can be incredibly confusing, and they're something I've had to deal with while building an unofficial client to Google Music [0]. Here are two things worth knowing (that are somewhat covered by the article): * aside from OAuth, any method of client auth is basically equivalent to SSO (ie, your entire Google account). As noted in the article, this includes app-specific passwords * SSO is not meant for programmatic access. If you want code to have access to SSO credentials, it's easiest to use some other auth service, and then "upgrade" to SSO (the linked blog post describes one way of doing this) [1] [0] https://github.com/simon-weber/Unofficial-Google-Music-API [1] http://nelenkov.blogspot.com/2012/11/sso-using-account-manag...