101–110 of 178 posts
>s you browse the web, that list changes as Chrome learns and enables autoplay on sites where you play media with sound during most of your visits, and disables it on sites where you don’t. What about disabling autoplay even without sound? Unwanted autoplay videos burn through battery even while muted.
> 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…
For me (and relevant to TFA) this is what is often missing from such learning engines; an option to manually intervene when necessary. It's hubris to assume that the heuristics will always get it right, and I would have to imagine there's valuable data in seeing what manual corrections a User makes, so I'm not sure why it's not included more. A .conf file, the "add/remove" weight as mentioned before, just some way for the user to correct the heuristics when they get it wrong. And they will get it wrong, and frequently do.
Earlier quoted context omitted.
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.
Google Spreadsheets is where it often fails to work perfectly - hard to get it to take me to the spreadsheets homepage if I don't remember exactly which sheet I want to open.
> 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.
It would be much nicer if the various plugins I use to control that behaviour wouldn't stop working every 4 months due to another youtube redesign (whether in UI or Backend on the Client).
Earlier quoted context omitted.
Youtube is the worst, because not only does it autoplay, but for the first 2s or so it's faffing around with JavaScript so no matter what you do in that time it will subsequently start playing. Like, it'll show up as "playing" and you pause it, then leave the tab, and like a second later the video will start despite your having paused it. (for the record, at least half the time I open a youtube video I don't want it…
i'm not sure if this is something on my end or google's, but i've noticed that in the past few weeks whenever I open a youtube video in a new tab (staying in the current tab), it won't play until i switch to the new one.
Earlier quoted context omitted.
Seems to be this blob: https://github.com/chromium/chromium/blob/b67034891a23389825...
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?
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/+/80... contains a lot of related files, including 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.
> As you browse the web, that list changes as Chrome learns and enables autoplay on sites where you play media with sound during most of your visits, and disables it on sites where you don’t. This way, Chrome gives you a personalized, predictable browsing experience. Predictable in a user application is the same result from the same action every time. UX changing based on opaque logic and heuristics is anything but p…
My bet is that they did this to not break Youtube. I mean it makes sense (you don't want video sites to not work) but it's also such a hacky sort of thing
I don't get why they couldn't make this a permission thing like a mic. Ask the website to allow autoplay.
Earlier quoted context omitted.
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…
Yes, as an artist the whole point is to keep exploring and creating. But unfortunately you still have to do things like pay bills and go to the toilet just like "the others".
This stuff goes alongside and is complementary to the creative work. None of it is present in my mind when I'm working on a painting because I'm in the zone. But if you want to do something with your work other than letting it sit in storage you have to do the other bits too. Thinking you shouldn't have to do any of this extra stuff is prima-donna-ish in my opinion.
I don't think the artist is evil, it does sound like particularly annoying stuff for him to have to deal with. But as an individual user I personally never want any sound or video autoplaying on a website, ever, for any reason. Give me a button to click. For extra non-hatred, don't use a dark pattern.
I understand that creators might say "if you're on my site you're there for the full experience". This is what everyone who ever builds anything thinks though, that their thing is the exception, it really is ok just in this one case. No sorry, this is the internet, all someone has done to end up at your site is click a link, they might not know what it is, maybe they're listening to an amazing album on their great sound system via their computer and don't want it interrupted by bleeps. They might be at work, or surfing in bed with somebody asleep next to them.
I guess the new Chrome policy will be ok for most people but it's going to be yet another annoyance for me. I seem to never fit into the way AI/ML does its predictions and rather than save me a click it usually ends up making me click more as I try to tell it how wrong it is and then try to coerce it into doing what I want. I'm going to hate the future.
>s you browse the web, that list changes as Chrome learns and enables autoplay on sites where you play media with sound during most of your visits, and disables it on sites where you don’t. What about disabling autoplay even without sound? Unwanted autoplay videos burn through battery even while muted.
Now a lot of "GIFs" aren't in GIF format, they're videos with no sound, and that makes a lot of sense because it's 2018 and we've learned some things about compression and video since 1987.
If silent videos didn't autoplay consistently, people would keep using actual GIFs, using way more bandwidth for the same purpose.
Preroll (IMA3) integration with an HTML5 video player is a really tricky dance when you’re trying to support mobile/desktop browsers with a resilient and consistent video player experience. Autoplay has been one of the most difficult differences to manage across browsers. There’s no browser api that tells you if autoplay is supported, and you won’t get meaningful errors when you try to autoplay when you can’t. Ultima…