- From: Marcos Cáceres via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Jun 2024 05:11:23 +0000
- To: public-device-apis-log@w3.org
> The link you've provided contains code that detects then uses the API. This pattern is necessary due to lack of implementation, not because of non-use. This is true. But it's also being used for feature detection. There are examples of usage, but those should be looked at in the context of replicating notifications, replicating a gamepad, or if they would be blocked by [interactions started without a gesture](https://chromestatus.com/feature/5644273861001216). I added Chrome's abuse mitigation details to the report (as more evidence that . > Can you provide more meaningful evidence for your statement: Actually, all the case do the feature detection, but do then then try misuse the API (all cases prevented by Chrome): * https://ajhales.co.uk * https://acidentedetrabalho.advogadotrabalhistamf.com.br/ * https://www.infirmier.cloud/ * https://www.kloesterl-apotheke.de/ * https://www.centersvet.com/ * https://m.uwin777.bet/ * https://shop.pluspunkt-apotheke-schwedt.de/ * https://www.centrsvet.by/ And so on... basically check any of the sites and they all get blocked from using the API by Chrome. You will see:  There's also things like: * https://warelawfirm.com/ :  has disabled it self from pretending to a notification. And just silly uses: * https://itradeit.in/ - where tapping anywhere causes a vibration. And straight up abuse cases like:  * https://www.satcomglobal.com/ God... the more one looks, the worst it gets with this thing... -- GitHub Notification of comment by marcoscaceres Please view or discuss this issue at https://github.com/w3c/vibration/issues/33#issuecomment-2159806634 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 June 2024 05:11:24 UTC