"The feature expands on existing functionality already available in Chrome's Safety Check feature, which revokes camera and location permissions from websites you don't visit anymore. The company tacitly admits that browser notifications, as designed, might have been a bad idea, saying that its own data shows users receive a high volume of notifications, but rarely interact with them. Less than 1% of all notifications receive any interactions from users, notes Google."
"Still, the tech giant believes some notifications can be helpful, which is why it won't revoke those for installed web apps - only for the sites where there's low user engagement and high volume of notifications sent. This change alone could push spammy websites that push a lot of notifications to reconsider how many they want to send alerts, so they won't lose access entirely. Unwanted notifications have been an issue facing consumers for years."
"Google says it will inform users when it's removing notification permissions, allowing users to change the setting back, if they prefer. If users would rather Google didn't intervene, they can also opt to turn off this auto-revocation feature altogether, the company notes. The feature had been in testing ahead of today's official launch. Google found that these changes didn't significantly impact the total number of"
Google will roll out a Chrome feature that automatically disables browser notifications for websites with low recent user interaction on Android and desktop. The feature builds on Safety Check's revocation of camera and location permissions for sites no longer visited. Google data shows a high volume of notifications but under 1% user interaction. Notifications for installed web apps will be preserved, while high-volume, low-engagement sites face auto-revocation. Users will be notified when permissions are removed, can restore settings, or can opt out of the auto-revocation feature. The feature was tested before launch.
Read at TechCrunch
Unable to calculate read time
Collection
[
|
...
]