That's a good idea. I'll fix the first one to Libre.fm and leave the security intact. I'll call to the second one a "GNU FM" scrobbler with the security wide open and the added configurable field.
I've also received some feedback that I should change the name / branding due to it's proprietary nature (Chrome, Google Music) so that it doesn't appear to be associated with Libre.fm. I'll be re-listing it as a "Google Music Scrobbler for Chrome which supports Libre.fm". Thank you all for your feedback. On Fri, Feb 10, 2012 at 11:43 AM, Rob Myers <[email protected]> wrote: > On 10/02/12 19:41, Mike Sheldon wrote: >> On Fri, 2012-02-10 at 11:13 -0800, Darryl G. Wright wrote: >>> There are 2 solutions to this: >>> >>> 1) I modify the ext to be exclusively a "Libre.fm" scrobbler >>> 2) Open it up to be able to access "all domains" essentially asking to >>> people accept the security risk. >> >> A third option would be to do both, release one extension purely aimed >> at Libre.fm for people who are only interested in using Libre.fm and are >> concerned about what the extension may access and a second one which can >> access any site for people who run their own servers (and so are likely >> to be far more aware of why those permissions are necessary). > > Yes that's a good division. People who just want it to work with > libre.fm get something that just works, people who just want to be able > to configure things to work with their server get that as well. > > - Rob. >
