They might be able to make requestable the connection requests to outside sources (which I expect is something many extensions use, even those without data collection), but whether those requests relate to data collection is not something that can be determined programmatically.
Yes, all access to outside sources is blocked by default and users are asked on a per URL basis with the author manually requesting each URL access including a reason – with occasional manual validation from Mozilla staff.
Agreed, it should be this way. But I guess it would break most applications that rely on data collection (and I am saying that with a voice of sarcasm).
They should do manual testing to confirn/deny this, in a mystery customer sort of way.
They have the Recommended Extensions program, where they do that for a subset of the available extensions.
https://support.mozilla.org/en-US/kb/recommended-extensions-program
They should make it a requestable permission.
I’m not sure if that would be viable technically.
They might be able to make requestable the connection requests to outside sources (which I expect is something many extensions use, even those without data collection), but whether those requests relate to data collection is not something that can be determined programmatically.
Yes, all access to outside sources is blocked by default and users are asked on a per URL basis with the author manually requesting each URL access including a reason – with occasional manual validation from Mozilla staff.
Agreed, it should be this way. But I guess it would break most applications that rely on data collection (and I am saying that with a voice of sarcasm).
Calm down guys you’re asking for an actual feature, now… this is gonna need like five years of extensive study and testing.