4 ms·

Can we find this auto-generated list of enabled/disabled sites anywhere? Can it be edited manually? Will Chrome notify why a particular site did/didn't auto-pla

Can we find this auto-generated list of enabled/disabled sites anywhere? Can it be edited manually? Will Chrome notify why a particular site did/didn't auto-play a video? I like Inbox's recent behaviour that explains why it deems a particular email important - it would be good if this sort of explanation was more prevalent with publicly-available ML systems.

asddddd 9y ago
Seems to be this blob: https://github.com/chromium/chromium/blob/b67034891a2338982544a9c524ef1394803f985d/chrome/browser/resources/media/mei_preload/preloaded_data.pb https://github.com/chromium/chromium/blob/b67034891a23389825...
- askvictor 9y ago
  Gah. A blob with no info about it. Looking a little further, it appears to be a ProtocolBuffer file, but would a bit of documentation hurt?
  - tgsovlerkhgsel 9y ago
    An early version of the proto I found is: https://chromium.googlesource.com/chromium/src.git/+/5d9089080ea5fb0e348bb28f7a396d1181476f0f/chrome/browser/media/media_engagement_preload.proto https://chromium.googlesource.com/chromium/src.git/+/5d90890... So the proto is a red herring, it's basically just a container for a blob in some other format. https://chromium-review.googlesource.com/c/chromium/src/+/803994 https://chromium-review.googlesource.com/c/chromium/src/+/80... contains a lot of related files, including https://chromium-review.googlesource.com/c/chromium/src/+/803994/9/tools/media_engagement_preload/make_dafsa.py https://chromium-review.googlesource.com/c/chromium/src/+/80... which explains the format. I'm surprised that there isn't a plain text version of the list checked in somewhere, but maybe I just missed it.
joosters 9y ago
Also, I wonder where chrome stores the user’s autoplay history? Will it be cleared when wiping history? Cookies? Or is it never wiped, leaving a record of visited sites in its storage?

asddddd 9y ago

Seems to be this blob: https://github.com/chromium/chromium/blob/b67034891a2338982544a9c524ef1394803f985d/chrome/browser/resources/media/mei_preload/preloaded_data.pb https://github.com/chromium/chromium/blob/b67034891a23389825...

askvictor 9y ago
Gah. A blob with no info about it. Looking a little further, it appears to be a ProtocolBuffer file, but would a bit of documentation hurt?
- tgsovlerkhgsel 9y ago
  An early version of the proto I found is: https://chromium.googlesource.com/chromium/src.git/+/5d9089080ea5fb0e348bb28f7a396d1181476f0f/chrome/browser/media/media_engagement_preload.proto https://chromium.googlesource.com/chromium/src.git/+/5d90890... So the proto is a red herring, it's basically just a container for a blob in some other format. https://chromium-review.googlesource.com/c/chromium/src/+/803994 https://chromium-review.googlesource.com/c/chromium/src/+/80... contains a lot of related files, including https://chromium-review.googlesource.com/c/chromium/src/+/803994/9/tools/media_engagement_preload/make_dafsa.py https://chromium-review.googlesource.com/c/chromium/src/+/80... which explains the format. I'm surprised that there isn't a plain text version of the list checked in somewhere, but maybe I just missed it.

joosters 9y ago

Also, I wonder where chrome stores the user’s autoplay history? Will it be cleared when wiping history? Cookies? Or is it never wiped, leaving a record of visited sites in its storage?