2 ms·
Obfuscated code plus these permissions isn't helping me trust you. As a Chrome extension developer, I can tell at a glance that many of these permissions are no
by Sephr 11y ago
Obfuscated code plus these permissions isn't helping me trust you. As a Chrome extension developer, I can tell at a glance that many of these permissions are not necessary to implement the functionality as described.
"permissions": [
"<all_urls>",
"activeTab",
"alarms",
"background",
"browsingData",
"chrome://favicon/",
"clipboardWrite",
"contextMenus",
"cookies",
"declarativeContent",
"fontSettings",
"gcm",
"identity",
"idle",
"notifications",
"pageCapture",
"power",
"proxy",
"sessions",
"storage",
"system.cpu",
"system.display",
"system.memory",
"system.storage",
"tabCapture",
"tabs",
"topSites",
"tts",
"unlimitedStorage",
"webNavigation",
"webRequest",
"webRequestBlocking"
]
Definitely not taking any chances installing this.
- motoboi 11y agoAsking full privileges is a way of avoiding changing them on a update. If you change permissions on a update, chrome will ask for user interaction. That being said, if you don't plan to broad the scope of an app or extension in the future, there is no point. This technique is applied on a lot of android apps too.
- Sephr 11y agoYeah, it's okay to do this as long as the developer explains in the app/extension overview that the permissions are for planned features.