3 ms·

Google does a number of things like this that give Chrome based browsers more power for Google based websites. Another example is the *.google.com cookies, the

Google does a number of things like this that give Chrome based browsers more power for Google based websites. Another example is the *.google.com cookies, they are not deleted when you go to clear browsing history -> clear cookies. Also a recent version of Chrome implemented "no autoplay audio or video" as a feature, but YouTube and Google music are on a whitelist pre-built into the Chrome browser.

kbenson 8y ago
> Also a recent version of Chrome implemented "no autoplay audio or video" as a feature, but YouTube and Google music are on a whitelist pre-built into the Chrome browser. They use the media engagement index[1] to gather global statistics to generate global average user preferences to determine if a domain get's to autoplay. It is not something manually defined through someone's decision about a specific domain. This global list is only used until the user has enough interactions with the site in question to allow chrome to use local MEI data to auto-whitelist the domain. It will likely allow youtube to autoplay, both initially because of the global data but also continuing oin after individual usage data is acquired, but that makes sense and is exactly as you would expect and want out of a system like this. It should also let a competitor auto-play after enough usage is detected, and continue to do so per-user after local data is collected for that instance of chrome. It will stop random domains from having video pop-ups that auto-play, or in page auto-playing, and it will also prevent domains that initially allow auto-playing from doing so later on if you stop the auto-playing enough that the local chrome instance learns your preferences. 1: https://developers.google.com/web/updates/2017/09/autoplay-policy-changes https://developers.google.com/web/updates/2017/09/autoplay-p... 2: https://bugs.chromium.org/p/chromium/issues/detail?id=843427#c2 https://bugs.chromium.org/p/chromium/issues/detail?id=843427...

kbenson 8y ago

> Also a recent version of Chrome implemented "no autoplay audio or video" as a feature, but YouTube and Google music are on a whitelist pre-built into the Chrome browser. They use the media engagement index[1] to gather global statistics to generate global average user preferences to determine if a domain get's to autoplay. It is not something manually defined through someone's decision about a specific domain. This global list is only used until the user has enough interactions with the site in question to allow chrome to use local MEI data to auto-whitelist the domain. It will likely allow youtube to autoplay, both initially because of the global data but also continuing oin after individual usage data is acquired, but that makes sense and is exactly as you would expect and want out of a system like this. It should also let a competitor auto-play after enough usage is detected, and continue to do so per-user after local data is collected for that instance of chrome. It will stop random domains from having video pop-ups that auto-play, or in page auto-playing, and it will also prevent domains that initially allow auto-playing from doing so later on if you stop the auto-playing enough that the local chrome instance learns your preferences. 1: https://developers.google.com/web/updates/2017/09/autoplay-policy-changes https://developers.google.com/web/updates/2017/09/autoplay-p... 2: https://bugs.chromium.org/p/chromium/issues/detail?id=843427#c2 https://bugs.chromium.org/p/chromium/issues/detail?id=843427...