search

WICG / idle-detection

A proposal for an idle detection and notification API for the web
Other
68 stars 22 forks source link

Describe alternative permission models considered #27

Closed reillyeon closed 4 years ago

reillyeon commented 4 years ago

The choice of whether to use the "notifications" permission has been discussed on #21 and #26. This adds sections to README.md explaining alternatives that have been considered.

reillyeon commented 4 years ago

CC @tomayac

subversivo58 commented 4 years ago

I don't see how the delay can mitigate a possible "cooperation" between sites, there are several ways to reach the user and bombard him with content (ads) when he is online ... this is a direct relationship between "site and client" and a long delay detrimental to the legitimate use experience and well applied by the API.

The user always has the option of not using a website / service that is being "abusive".

I find an "own flag" extremely beneficial ... this brings information and choice to the user. In this principle, the user has "granular" control over something that incorporates their privacy.

I don't believe that "consent fatigue" should be an API concern ... this "fatigue" is directly associated with the number of APIs they use.