{"action":"created","issue":{"url":"https://api.github.com/repos/twolfson/google-music.js/issues/13","labels_url":"https://api.github.com/repos/twolfson/google-music.js/issues/13/labels{/name}","comments_url":"https://api.github.com/repos/twolfson/google-music.js/issues/13/comments","events_url":"https://api.github.com/repos/twolfson/google-music.js/issues/13/events","html_url":"https://github.com/twolfson/google-music.js/issues/13","id":121888040,"number":13,"title":"Move this repo into a shared space and expand into a bigger \"framework\"","user":{"login":"MarshallOfSound","id":6634592,"avatar_url":"https://avatars.githubusercontent.com/u/6634592?v=3","gravatar_id":"","url":"https://api.github.com/users/MarshallOfSound","html_url":"https://github.com/MarshallOfSound","followers_url":"https://api.github.com/users/MarshallOfSound/followers","following_url":"https://api.github.com/users/MarshallOfSound/following{/other_user}","gists_url":"https://api.github.com/users/MarshallOfSound/gists{/gist_id}","starred_url":"https://api.github.com/users/MarshallOfSound/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/MarshallOfSound/subscriptions","organizations_url":"https://api.github.com/users/MarshallOfSound/orgs","repos_url":"https://api.github.com/users/MarshallOfSound/repos","events_url":"https://api.github.com/users/MarshallOfSound/events{/privacy}","received_events_url":"https://api.github.com/users/MarshallOfSound/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2015-12-12T23:54:10Z","updated_at":"2015-12-14T00:25:39Z","closed_at":null,"body":"Copy paste from the message I sent a while back\r\n\r\nHey guys,\r\nI added both of you to this group as I think we are all \"stakeholders\" (if that is the correct word to use), in the potential for an expanded Google Play Music JS Framework that extends on what @twolfson has already done in his Google Music node package.\r\n\r\n**I have recently made a branch on my player that changes all my JS to use the Google Music node package, but I realized while testing that what I was doing had a few issues**\r\na) My code was still fragmented, some of it used this marvelous API. Whilst the rest was doing everything manually with obscure, unrecognizable selectors\r\nb) I had no control over this framework, if something broke I couldn't push out a fix in a few hours I would have to wait for either @twolfson to fix it or submit a PR and hope it gets merged\r\nc) These fixes still relied on the user updating their application, if for whatever reason they decided not too (some users are stubborn like that) they will not get the fixes...\r\n\r\n**I would like to propose the following**\r\nWe should either fork or move the Google Music node repository into a space where people who use it (Me, Radiant Player, Electron Player, Etc.) will have contributor rights to allow one of us to push fixes ASAP. This will allow changes to go out much quicker as it will take only one of us to fix everyone's applications\r\nInstead of depending upon statically released JS files we should depend on a CDN? Or the latest github release? so that updates to this framework, can be pushed independently of a version bump on our players\r\nThis proposed framework should maintain the existing functionality of the current Google Music node package but should also have add on packages that allow theming support (I have some funky JS in my repo at the moment that does this) and other things like possibly a central last.fm intergration library?\r\nWhat do you guys think of this proposal?\r\n\r\nTagging relevant parties\r\n@twolfson @jacobwgillespie @chrismou"},"comment":{"url":"https://api.github.com/repos/twolfson/google-music.js/issues/comments/164314110","html_url":"https://github.com/twolfson/google-music.js/issues/13#issuecomment-164314110","issue_url":"https://api.github.com/repos/twolfson/google-music.js/issues/13","id":164314110,"user":{"login":"twolfson","id":902488,"avatar_url":"https://avatars.githubusercontent.com/u/902488?v=3","gravatar_id":"","url":"https://api.github.com/users/twolfson","html_url":"https://github.com/twolfson","followers_url":"https://api.github.com/users/twolfson/followers","following_url":"https://api.github.com/users/twolfson/following{/other_user}","gists_url":"https://api.github.com/users/twolfson/gists{/gist_id}","starred_url":"https://api.github.com/users/twolfson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/twolfson/subscriptions","organizations_url":"https://api.github.com/users/twolfson/orgs","repos_url":"https://api.github.com/users/twolfson/repos","events_url":"https://api.github.com/users/twolfson/events{/privacy}","received_events_url":"https://api.github.com/users/twolfson/received_events","type":"User","site_admin":false},"created_at":"2015-12-14T00:25:39Z","updated_at":"2015-12-14T00:25:39Z","body":"Damn, hit a snag with rawgit.com. I could have sworn that the cache eventually expired but it turns out it doesn't:\r\n\r\nhttp://rawgit.com/faq#cdn-ttl\r\n\r\nI'm sure that if we use the non-CDN version, then we will eventually have too many users and piss people off. There are options like S3 and such but I feel like we are starting to make a mountain out of a molehill =/"}}