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

81–90 of 178 posts

Re: New autoplay policy in Chrome

#81

Post by Jach »

benjaminjackman wrote: post #44
geofft wrote: post #14

Earlier quoted context omitted.

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?)

So I tried to explore the site as a firefox user, this is the type of stuff I get: Big warning and messages to install Google Chrome [1][2] without even then attempting to give it a shot in firefox for some demos from what I can tell (I may be mistaken, perhaps firefox is breaking still). Given the impressive amount of work they put into the site, it's unfortunate a few lines of feature detection and polyfills weren'…

Yeah I tried using Firefox too on one of the sites, it didn't go well. No content, enabled JS, a brief menu with some sound effects popped up, then the whole page changed into an invalid HTTPS cert page as if I triggered a redirect or a script tried to load a resource or something else, apparently they're trying to use a github-domain-only cert and I'd have to add an exception. I left at that point.

The artist reaction makes him come across as a primadonna. It's not like there aren't thousands of art projects made from Java applets that either flat out don't work anymore or require an absurd amount of manual steps to get working. The effort he'd need to make to keep things working (which is generally a given for so much of software) is quite a bit less than those artists who banked on the Java (or hell, even Flash) horse.

Re: New autoplay policy in Chrome

#82

Post by stringlytyped »

always_good wrote: post #54
sanxiyn wrote: post #18

> 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.

Reminds me of fuzzy matching systems like Alfred that will try to learn which key combos you use to launch each app instead of trying to offer you predictability. But "fi " never launches Firefox anymore because of that one time you accidentally launched Finder instead. And since you keep accidentally launching Finder that way, it never learns that you want Firefox. So you try "f " but you accidentally launch Flux. A…

Yes! Spotlight does the exact same thing. Drives me crazy.

Re: New autoplay policy in Chrome

#84

Post by 07d046 »

always_good wrote: post #54
sanxiyn wrote: post #18

> 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.

Reminds me of fuzzy matching systems like Alfred that will try to learn which key combos you use to launch each app instead of trying to offer you predictability. But "fi " never launches Firefox anymore because of that one time you accidentally launched Finder instead. And since you keep accidentally launching Finder that way, it never learns that you want Firefox. So you try "f " but you accidentally launch Flux. A…

And then there's Chrome, where you can start typing something in the URL bar, and it comes up with some results immediately, but in the milliseconds before you select a result it changes to something "better" so you go to the page instead. Infuriating.

Re: New autoplay policy in Chrome

#85

Post by Theodeus »

Jach wrote: post #81
benjaminjackman wrote: post #44

Earlier quoted context omitted.

So I tried to explore the site as a firefox user, this is the type of stuff I get: Big warning and messages to install Google Chrome [1][2] without even then attempting to give it a shot in firefox for some demos from what I can tell (I may be mistaken, perhaps firefox is breaking still). Given the impressive amount of work they put into the site, it's unfortunate a few lines of feature detection and polyfills weren'…

Yeah I tried using Firefox too on one of the sites, it didn't go well. No content, enabled JS, a brief menu with some sound effects popped up, then the whole page changed into an invalid HTTPS cert page as if I triggered a redirect or a script tried to load a resource or something else, apparently they're trying to use a github-domain-only cert and I'd have to add an exception. I left at that point. The artist reacti…

The artist in question has been pioneering online interactive experiences for years, and through his work (and possibly directly) helped shape the APIs and prompt browser adoption of new standards used.

If you get a "use chrome" message, it's most likely not because the artist is evil, but rather that the experience used tech only available in chrome at the time the work was done.

As an artist, the whole point is to keep exploring and creating. It's not the same as a 9 to 5 where you maintain a company website etc. Going back and adjusting the flow for each experience would be the equivalent of asking pavers to go back and add a bit of plastic to each section of concrete they've laid down for the last five years.

I think the strong reaction comes from the fact that this change was sprung with very little, if any, warning.

Re: New autoplay policy in Chrome

#86

Post by [deleted] »

chipperyman573 wrote: post #40
bastawhiz wrote: post #37

Earlier quoted context omitted.

This has already been possible. You can disable sound for all websites in chrome://settings/content/sound Then, you can enable sound manually for each site in the site settings panel.

Wow, I never knew this! I will definitely be doing it now. Does anyone happen to know if this will overwrite this new learning setting?

[deleted]

Re: New autoplay policy in Chrome

#87

Post by kowdermeister »

flukus wrote: post #78
Jyaif wrote: post #5

accurate summary: If you don’t have browsing history, Chrome allows autoplay for over 1,000 sites where we see that the highest percentage of visitors play media with sound. As you browse the web, that list changes as Chrome learns.

Not that this would be surprising, but does that mean chrome is collecting user data?

It always did.

Re: New autoplay policy in Chrome

#88

Post by gumby »

I just gave up and basically always have the sound off. I occasionally turn up the volume manually for something specific.

Unfortunately this does nothing for moving images (moving ads).

Re: New autoplay policy in Chrome

#89

Post by Sylos »

Gaelan wrote: post #46
nightcracker wrote: post #22

> This way, Chrome gives you a personalized, predictable browsing experience. > predictable What could possibly be more predictable than disabling autoplay altogether? Google says it enabled autoplay for 'over 1000 sites', but we all know Google only cares about one thing and that is playing more ads on YouTube.

Cynicism aside, YouTube is a typical example of a good use for autoplay. A user clicking a link to YT almost always wants to watch the video. "Predictable" probably wasn't the right word for them to use, but I think this is a reasonable move by Google.

Even with that in mind, blocking it on all sites with those few whitelisted would be simpler and more predictable.

Re: New autoplay policy in Chrome

#90

Post by Sylos »

flukus wrote: post #78
Jyaif wrote: post #5

accurate summary: If you don’t have browsing history, Chrome allows autoplay for over 1,000 sites where we see that the highest percentage of visitors play media with sound. As you browse the web, that list changes as Chrome learns.

Not that this would be surprising, but does that mean chrome is collecting user data?

When you use Chrome Sync, Google gathers and evaluates your entire browsing history.

You can forego it by enabling end-to-end-encryption, but since they require a second password for that, the percentage of Chrome Sync users who use this, is probably close to 0%.

Post reply on HN