This reminds me so much of “Gryzzl” on Parks and Rec.
“We just want to learn everything about you, collect all your data and watch everything you do”
New autoplay policy in Chrome
41–50 of 178 posts
Re: New autoplay policy in Chrome
#42The best way to improve autoplay is to disable it. chrome://flags/#autoplay-policy
I block video content distribution sites at the source, via my router.
Ditching Chrome is another excellent and recommended option.
Re: New autoplay policy in Chrome
#43Earlier 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?)
Adding a "click to start the experience" button changes the experience. In particular, some users might not see the button if it's subtle, and be unimpressed or think the site is broken. And if the button is not subtle that's bad too. It's also annoying to have to do such a change to your art for a single browser. Overall I think the artist's frustration is understandable, but I agree "destroyed" is perhaps too stron…
Do we really have to pander to people who can’t find a play button?
How do these people function at crosswalks or in elevators?
Re: New autoplay policy in Chrome
#44Bret 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?)
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't placed in there, because maybe then this could be a `sed -i /install google chrome/install Firefox/` fixup.
(I say that on the presumption that firefox is now able to handle the multimedia stuff which has been my personal experience with it, though not quite at the same level as the artist, just some pitch shifts and hand rolled synth stuff).
1: https://imgur.com/a/4rMgv7g 2: https://imgur.com/a/j90myrD
Re: New autoplay policy in Chrome
#45Most of the word I'd like to use doesn't fly here.
But what part of "No, never" does Google not understand?
Nuke Chrome, Android, Youtube, and Web search.
Re: New autoplay policy in Chrome
#46> 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.
Re: New autoplay policy in Chrome
#47Updated "being eaten" preferences for sheeps from wolf.
Wolf only does this by learning sheep' preferences.
Of course keeping sheeps happy is wolf's first priority.
Re: New autoplay policy in Chrome
#48This broke my accessibility extension for Chrome that lets users control the browser with their voice instead of hands.
Since voice isn't counted as a "gesture" the user can't say "play" to start a a video.
It's not just autoplay it's any sort of dynamic (js initiated) playing of media.
Re: New autoplay policy in Chrome
#49I think it would be better to just disable autoplay on all websites, and then let me manually enable it.
I pretty much continue to install Adblock so I can kill the auto-play elements on websites that just should not autoplay.
Re: New autoplay policy in Chrome
#50On a 1366x768 screen, that blog was painful to read. The header and top menu stuff take up about the top 1/4 of the window (and only folds away near the bottom of the page), and the "related articles" takes the bottom 1/4. Clicking the button to hide related helped some.
My autoplay desires are pretty simple. If the site's Youtube, Vimeo, or another site that exists purely for video, I expect videos to autoplay. It'll annoy me anywhere else. I'd be fine with a whitelist. What I like the least about their new implementation is that the behavior of the browser will change on its own. I don't like my software trying to predict me or changing its behavior without an explicit command to do so.