3 ms·
How about a notification when some new component is added? That's fairly common standard procedure for getting permission without being deceptive.
by TuringTest 9y ago
How about a notification when some new component is added? That's fairly common standard procedure for getting permission without being deceptive.
- cbcoutinho 9y agoI would argue it's almost always obfuscatory, if not deceptive. How many emails/updates do we all get with something along the lines of `We've updated our terms, read them here!`. This extension could have easily found its way into one of those updates
- Vinnl 9y agoThe question then is how to avoid alert fatigue [1]. "Component" is also a fairly ill-defined term, I think. [1] https://en.wikipedia.org/wiki/Alarm_fatigue https://en.wikipedia.org/wiki/Alarm_fatigue
- TuringTest 9y agoA good strategy is to bundle them, so that users can review a bunch of alerts when they're ready for the task. Release Notes of a new version is a good place to place that bundle. People concerned with security do set aside time for such task.