Pop ups. unders, autoplay, videos, etc

[JoeWras]

I don't mind paying for it with ads. I even like some of the ads (except denture grip and incontinence).

What I don't like are the constant readjustments of the screen which cause unwanted clicks, and which yank the text away from you.

Some sites have simply gone "a bridge too far" and are repelling me.

[rbmrtn]

For chrome there is an extension that may help HTML5 autoplay

https://chrome.google.com/webstore/d...ndpkolai?hl=en

[tfudtuckerpucker]

I thought I had the problem solved by blocking media elements with Ublock origin. I was wrong. Cnet's autoplay started blathering this morning. Gaak. So I found another Chrome extension- "Silent Site Sound Blocker". This mutes all web sites, except those you whitelist. So far, so good. I know I can use the mute button, but that's annoying.

[jimbee]

Quote:

Originally Posted by imoldernu So here's the thing: When I go to an article, I like to quick scan the text to see if I'll be interested, instead of watching a five minute video that I won't be interested in.... (Aside) "Am I the only one who still reads?" The Ad Blockers, and in the case of Chrome, extension "disable HTML5 autoplay" just don't work. "error encountered - Details are in the Developer Console... " Really...

I also prefer to read rather than watch a video. If you want to try Firefox, here is the setting to block html5 video autoplay. It works ok for me.

Finally: Mozilla adds working HTML5 Video autoplay blocking to Firefox - gHacks Tech News

[imoldernu]

Don't enjoy beating a dead horse, but the problem is growing worse... just in the past few weeks.
For those who use Chrome, the "Disable html5 Autoplay" extension doesn't work in most news websites.
A secondary problem is getting worse... and that is that there is a time delay that starts the "videos" a minute or so after you have begun reading an article.

For those who are using the "Mercury Reader" extension or the "IRead" extension, when the video begins to download, the website may/will "freeze", asking you if you want to "wait", or kill the page. Waiting doesn't work, so you have to kill the page. This effectively means you can't use the "reader" extensions.

This started on a few of the better know news websites, but has now extended to more, less popular sites.

The problem that I see, is that the sites don't really benefit from more ads being seen. For some of the news sites, it may be a way of forcing pay subscriptions. not for this puppy...

...end of rant

[bUU]

People work so hard to avoid advertising that I think eventually the value proposition to the service provider from all advertising will be pretty insignificant. Many of the most invasive measures are an attempt to retain some semblance of value, if not real value. So every bit of advertising supported content we get now, no matter how annoying the advertising that slips through is, is content we should be sheepishly grateful for. Collectively, we are no longer doing our part to truly participate in paying for the content we consume.