- From: Daniel Appelquist <notifications@github.com>
- Date: Tue, 19 Jun 2018 04:29:58 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 19 June 2018 11:30:25 UTC
How can this be used for evil and how can the API design mitigate these risks? I firmly believe that notifications are an extremely useful web feature and this proposed extension looks to make them even more useful. However, notifications have also been getting a very bad reputation recently due to their overuse and abuse. For example, requesting permission to send push notifications on first page load is arguably an antipattern. Allowing notifications to put interactive UI into users' notification "drawers" has the potential to exacerbate this problem as people misuse this feature to grab attention or to deliberately mislead people in phishing type attacks. What in the API design or other normative requirements can help to mitigate against these potential issues? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/284#issuecomment-398366735
Received on Tuesday, 19 June 2018 11:30:25 UTC