This was done because we plan to expand support to more music services, and when we push out updates requiring new permissions, the extension gets disabled on everyone's devices and requires a blind acceptance of new permissions. This is unideal for our users who already have their music service supported.
However, multiple users have raised concerns about asking for access to all web pages, as it technically allows us to have access to all of their data or manipulate any websites they are on. While we are obviously not doing that, it is an understandable concern.
Solution
Now that we have a list of likely next music services to support (check the list of music service requests in the Issues tab), let's simply enumerate the permissions required for those music services now. That way we can remove the wide-ranging permissions request while still avoiding disabling the extension for everyone as we push out support for these music services.
Describe the bug Right now, we declare the following permissions:
in the following files:
This was done because we plan to expand support to more music services, and when we push out updates requiring new permissions, the extension gets disabled on everyone's devices and requires a blind acceptance of new permissions. This is unideal for our users who already have their music service supported.
However, multiple users have raised concerns about asking for access to all web pages, as it technically allows us to have access to all of their data or manipulate any websites they are on. While we are obviously not doing that, it is an understandable concern.
Solution Now that we have a list of likely next music services to support (check the list of music service requests in the Issues tab), let's simply enumerate the permissions required for those music services now. That way we can remove the wide-ranging permissions request while still avoiding disabling the extension for everyone as we push out support for these music services.