Re:Some notes on Firefox's media autoplay settings in practi...
by nine_k on Saturday March 30, 2024 @09:36AM
(#39874738)
Back when Opera was a worthy browser, around 2000, it had various bandwidth-saving and CPU-saving controls. In particular, it had buttons to prevent loading of large images, and IIRC for gif autoplay.
Re:Some notes on Firefox's media autoplay settings in practi...
by gevz on Saturday March 30, 2024 @10:07AM
(#39875037)
Vivaldi is worthy successor and have those toggles built-in.
Re:Some notes on Firefox's media autoplay settings in practi...
by rjzzleep on Saturday March 30, 2024 @02:38PM
(#39877449)
and with such a slow GUI that you couldn't run in on those low performance devices even with those toggles enabled...
Re:Some notes on Firefox's media autoplay settings in practi...
by EasyMark on Saturday March 30, 2024 @10:27PM
(#39880797)
what? I use vivaldi on a nine year old desktop and its fine.
Re:Some notes on Firefox's media autoplay settings in practi...
by palmfacehn on Saturday March 30, 2024 @10:59AM
(#39875490)
Send a HEAD request. If the file size is over the threshold, don't load it without user consent.
Re:Some notes on Firefox's media autoplay settings in practi...
by cqqxo4zV46cp on Saturday March 30, 2024 @01:21PM
(#39876706)
A perfect idea for the people who almost certainly aren’t using “cheaper hardware devices”.
Re:Some notes on Firefox's media autoplay settings in practi...
by mariusor on Saturday March 30, 2024 @05:00PM
(#39878614)
I wonder why nobody introduced a "Accept-Max-Size" request header?
Chrome is toying with custom accept header[1] types but they're used by servers to request information from clients, which is completely missing the point in my opinion.
[1] https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_ne...
Re:Some notes on Firefox's media autoplay settings in practi...
by contravariant on Saturday March 30, 2024 @09:58PM
(#39880645)
Pretty sure this is part of uBlocks standard features.
Honestly it's getting a bit too noticeable how a full-featured adblocker is converging on just a way to let the user take back control over the user agent.
But this is more a rant for modern webdev practices I'm not sure much can be done to circumvent it from a browser perspective.