[kylekampy]

I know the permissions are overbearing. The reason it requests permissions for all sites instead of just the supported players is because of the way Chrome updates extensions. If I were to go that route and at some point add another player (which happens often), Chrome would disable the extension for everyone until they re-approve the changed permissions.

I believe there is a way to do it dynamically and allow the user to choose which players they want to allow access to, and then accept the changed permissions. However a majority of my user base will not care, and would actually prefer the one click install ease of use. At least that's my reasoning.

For those of you really concerned, you can download the source and modify manifest.json to change where the contentscript is injected for peace of mind. https://github.com/kkamperschroer/Musicality

[willnorris]

Chrome forcing the user to re-approve the extension when it tries to access more data is a feature, not something to work around. That alone is reason enough for me to say "thanks, but no thanks"

[kylekampy]

I agree with you. As a privacy-conscious user of Chrome extensions, I'm glad Chrome does things this way. There are too many horror stories out there.

I'll continue to look into ways I can deal with this without blindly asking for everything. I haven't found a good solution yet, but that doesn't mean there isn't a better way to do it out there.