Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

New autoplay policy in Chrome

blog.google

Post reply on HN
Print view View original

11–20 of 178 posts

Re: New autoplay policy in Chrome

#11

Post by makomk »

Amelorate wrote: post #9
gcb0 wrote: post #2

summary: google allow 800 of the international youtube domains to autoplay, plus some 200 other publishers to pretend they are neutral.

My interpretation of the article was that chrome ships with a blocklist of websites that have annoying autoplay features, but will automatically remove websites from that blocklist that you usually start by playing their videos, and automatically adds websites to the blocklist if the first thing you do is pause the video. Youtube probably is not on the blocklist, but it will add youtube to your personal blocklist if…

Other way around, as I understand it - they have a whitelist of sites that are allowed to play audio without interaction, everything else is blocked by default. (This is implemented in a way that completely breaks audio in a bunch of older web-based games and interactive audio experiences, too.)

Re: New autoplay policy in Chrome

#14

Post by geofft »

panic wrote: post #12

Bret Victor's response: https://twitter.com/worrydream/status/993167096992288771

I genuinely do not understand the artist in the replies who says this has destroyed their work. Can't the website require you to click/tap once to start its thing, without negative impact? I feel like I must be missing something. (There's a mention about not updating code for existing work, which might be it?)

Re: New autoplay policy in Chrome

#16

Post by rocqua »

Why does this system 'learn'. I wouldn't mind a prompt much like desktop-notifications are now. Ask me if a site can auto-play.

If google want this on-by-default on youtube, I wouldn't mind. As an upside, this would make it obvious they favor their own product.

Re: New autoplay policy in Chrome

#18

Post by sanxiyn »

> Chrome does this by learning your preferences... This way, Chrome gives you a personalized, predictable browsing experience.

In my experience, "learning" and "predictable" do not go together.

Re: New autoplay policy in Chrome

#19

Post by drewg123 »

crystaln wrote: post #10

The best way to improve autoplay is to disable it. chrome://flags/#autoplay-policy

Which, sadly, does not actually work for me. I've had it disabled since it first appeared and it has barely made a difference. At least for the news site that play unwanted video. The best I've been able to do in Chrome is to block anything that looks like a CDN using Privacy Badger.

Re: New autoplay policy in Chrome

#20

Post by _neil »

geofft wrote: post #14
panic wrote: post #12

Bret Victor's response: https://twitter.com/worrydream/status/993167096992288771

I genuinely do not understand the artist in the replies who says this has destroyed their work. Can't the website require you to click/tap once to start its thing, without negative impact? I feel like I must be missing something. (There's a mention about not updating code for existing work, which might be it?)

The artist in question has hundreds of pieces of work, many of which he may not have easy (if any) access to anymore. It would take a non-trivial amount of work to fix.

But I think he’s also expressing doubt about creating art/work on the web in the future because of things like this.

Post reply on HN