However, not responding to this thread or future thread about this topic does not mean we'd reconsider our position. I'm going to stop responding to this thread at this point because none of the use cases presented either here or elsewhere are compelling, and none of the privacy or security mitigations you've presented here and I found elsewhere are adequate.
It seems to me that such a suppression / distribution mechanism is best left for the underlying operating systems / web browsers to handle. That's a very serious breach of the said user's privacy. Also, who is such a service supposed to know what other device user might be using at any given point? We're definitely not going to let a website know all the devices a given user might be using at any given point. For starters, there is no guarantee that the user won't immediately come back to the device. That doesn't seem like a strong enough use case for this API. In the same vein, the development team behind WebKit - which is the browser engine for Apple's Safari - has provided a negative stance, stating that: While the reaction from web developers has obviously been positive, Mozilla has shot down the API as harmful, citing "opportunity for surveillance capitalism" and the fact that a malicious site could utilize the API to maximize the device's compute resources without the user consenting or knowing about it. The developer-facing notification will now be triggered for global signals such as interaction with other apps instead of only the current browser window.
However, it is certainly more controversial due to the introduction of support for an idle detection API.Ĭhrome 94 will offer more signals to developers to understand when a user is idle. Since Google is shifting to a four-week release cycle instead of its previous six-week cadence, and the fact that this build comes just three weeks after Chrome 93, the feature-set this time around is relatively smaller. Today, Chrome 94 will be released to the general public. Chrome 93 rolled out to the Stable channel last month with support for WebOTP on desktop, and deprecation of the 3DES cipher suite in Transport Layer Security (TLS).
0 kommentar(er)
