Let's guess what Google requires in 14 days or they kill our extension

Re:Let's guess what Google requires in 14 days or they kill ... by awinter-py on Wednesday May 13, 2020 @04:07PM (#23171221)

Disagree that G's motivation here is to reduce permission footprint, because:

- if G has the ability to automatically audit necessary permissions, they'd do it when you upload to the plugin store

- if they're doing this manually for popular plugins, then (1) they'd publicly certify safe plugins and (2) the interaction would be way more high touch

Plugins are inherently unsafe + require trusting the developer.

Could be malicious, or G may not even have a reason for this (it may be some forgotten dinosaur instinct to knock over other people's stuff when it gets too big).

[ Parent | on HN ]

Re:Let's guess what Google requires in 14 days or they kill ... by danpalmer on Wednesday May 13, 2020 @05:31PM (#23172067)

> - if G has the ability to automatically audit necessary permissions, they'd do it when you upload to the plugin store

If they added it more recently then they are just back-applying it to an already existing extension.

Alternatively, you can report plugins as requesting incorrect permissions – I've done this. Perhaps that's what's happened here, lots of reports triggering an investigation.

[ Parent | on HN ]

Re:Let's guess what Google requires in 14 days or they kill ... by ViViDboarder on Wednesday May 13, 2020 @05:25PM (#23172016)

Also, Google could just block the permission and let the extension developers deal. Even that would be less hostile because at least the developers would know what to fix.

[ Parent | on HN ]