I keep a long list of these I can contribute. The authors need to take more advantage of fuzzy attribute matching. Really go after those patterns you see frequently from Mailchimp and other major newsletter vendors first!<p><pre><code> [class*="mc_embed_signup"]
[id*="mc_embed_signup"]
[class*="FreeNewsletter" i]
[class*="inline-newsletter"]
[class*="newsletter-article"]
[class*="newsletter-form"]
[class*="newsletter-signup"]
[class*="newsletter-tout"]
[class*="newsletter-widget"]
[class*="NewsletterCard" i]
[class*="NewsletterSignup" i]
[class*="newssignup"]
[id*="SignupForm" i]
[id*="signupWrapper" i]
</code></pre>
CSS isn't so simple anymore though, with CSS-in-JS we're moving away from deterministic class name. We can still target other attributes with CSS though, which I don't see used in these lists nearly enough, for example data attributes:<p><pre><code> [data-title*="Mailchimp"]</code></pre>
Website owners are desperate to capture your attention, they have a few seconds to do so. What they don't realize is that beong annoying is also what causes people to only stay for a few seconds on their site. For me it is a good sign of someone who cares more about advertisement than content so it makes me close the page 99% of the time.
Actually I think that a lot of newsletters of professionals i am interested in are worthy and these are edge cases. I will be more worried not seeing these because they were filtered out by some plugin. I would say that if a site has a harassing newsletter then the whole site is probably not worth my time.
This by far is by biggest pet peeve of reading online: an article can't even be shown in full. It has to be broken up into disembodied sections, with ads, newsletter signups, or a block of links appearing every few paragraphs.<p>Fortunately, the NYT appears to have scaled back on this. I'm finding that I can do "Print to PDF" on the majority of articles (excl. interactive stories) and the layout is very clean with no interruptions.<p>If that changes, I still have the option of going to FF's "reading view" and Print to PDF from there.
Personally I use the "No, Thanks" extension.<p>It costs a bit of money. Daniel Kladnik, the developer, provides you with an invoice so you can deduct it as a business, or ask your boss to pay.<p><a href="https://www.no-thanks-extension.com/" rel="nofollow">https://www.no-thanks-extension.com/</a><p>Note that I haven't compared it to Fanboy's Annoyance List mentioned in the article. Ages ago, I just wanted a no-configure option.
Most of what I do in a browser is read documents. News articles, blogs, those kinds of things. So I just turn off everything using umatrix BT default. CSS, JS, everything except first party images. It works very well. I'd rather scroll through broken formatting to get to the meat I'm trying to get to than tolerate a nonstandard UI just to read a document.<p>I use some web apps (like HN or github) and so I change settings for those sites. My rule of thumb is if your site isn't a web app you I don't need anything but HTML. Every so often I get third party images or other media that I want to see, so I turn it on. And every so often I get a page that I am only expecting a document but instead get a blank page, indicating to me that they require scripts to be on to receive a text document. I immediately as a rule close them. If you need to see where my cursor is or whatever just for me to read what you have to say I'm not interested in reading what you have written.