Google Chrome 94 is here and it has introduced a controversial idle detection API. For those people that do not know what idle detection API is, well basically Chrome can be asked by a website to report when a user of the site has a site open and is idle on the device. The issue that people have with this is that this particular feature can be used to report when the user is not using a computer at all.
Good thing is that website or web application will prompt you to allow it to use this feature like when a site/application wants to use your microphone or web camera. Developers are on board with this feature since it can provide them with more telemetric data on how users are interacting with their website/application but there are some that are strongly voicing against this.
Tantek Çelik, Mozilla Standards Lead, commented on GitHub, saying:
As it is currently specified, I consider the Idle Detection API too tempting of an opportunity for surveillance capitalism motivated websites to invade an aspect of the user’s physical privacy, keep long-term records of physical user behaviors, discerning daily rhythms (e.g. lunchtime), and using that for proactive psychological manipulation (e.g. hunger, emotion, choice)…
Thus I propose labeling this API harmful and encourage further incubation, perhaps reconsidering simpler, less-invasive alternative approaches to solve the motivating use-cases.
Others who have spoken against this feature are people from the WebKit development team inside Apple. Ryosuke Niwa, an Apple software engineer who works on WebKit said:
That doesn’t seem like a strong enough use case for this API. For starters, there is no guarantee that the user won’t immediately come back to the device. Also, who is such a service supposed to know what another 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. That’s a very serious breach of the said user’s privacy. It seems to me that such a suppression/distribution mechanism is best left for the underlying operating systems/web browsers to handle.
Of course, technology itself as always can be used for good or for bad and time will tell if this feature has brought good stuff or it has paved another brick in surveillance and privacy manipulation. As said for now option will prompt for agreement and let's hope that it will be used for good causes from this day into the future.
“0xC1900209, Incompatible software is blocking the upgrade process. Uninstall the application and try the upgrade again.”This error message comes under the umbrella of the Windows 10 pre-upgrade validation using Setup.exe. And for you to identify the incompatible app, you need to grab a Windows 10 install image using the Windows Media Creation tool to download the suitable Windows 10 version and mount it. After that, execute the setup.exe file that’s located in the root folder of the Windows 10 install image. Once you execute the setup file, the upgrade wizard will give you a list of incompatible apps. Once you have determined which software is not compatible with the Windows Update, there are two options you can try to resolve the Windows Update error 0xC1900209 – you can either try to update the conflicting software or uninstall it. For more details, follow the given options below.
CHKDSK [volume [[path] filename]] [/F] [/V] [/R] [/X] [/C] [: size]]Note: In the command given above, “[/F]” will try to fix the system errors while “[/R]” will be the one to fix the bad sectors.