4 ms·
> Consider the whole web hostile. That has been the model since the beginning. The problem is that web developers and browser developers have a greater interes
by wang_li 9y ago
> Consider the whole web hostile.
That has been the model since the beginning. The problem is that web developers and browser developers have a greater interest in doing their thing than in protecting end users. Thus the introduction of cookies, javascript, iframes, etc. It's been a continuous curve of increased scope inside tbe browser. Now we have web assembly, workers, websockets, local storage, etc. and no good way for the end user to actually observe any of this shit. Browser developers are reinventing the operating system, but poorly.
- guelo 9y agoYou make me think of the travesty of web video. Flash video worked fine, and Flash blockers worked well and gave users the control of when to play video. Flash blockers were some of the most popular plugins. Then, for reasons that users didn't care about, the web was "improved" to build video into JavaScript APIs. But somehow they failed to add user's top requested video feature: autoplay control. Now we're stuck with publishers using increasingly user-hostile autoplay video with no user control.
- Santosh83 9y agoYes. Flash was made click to play by default and all seemed to be fine, then we got HTML5 video. I still can't manage to block some videos on popular news sites from autoplaying each time I visit an article page. Even with media.autoplay.enabled set to FALSE in Firefox's configuration.
- zAy0LfpBZLC8mAC 9y agoI very much cared about proprietary software with loads of vulnerabilities hoggin the CPU being replaced by something more sensible. That browsers don't implement any effective autoplay control still is idiotic (but then, the solution is simple: deactivate all codecs, and use youtube-dl for a better and ad-free user experience anyway).