{"id":52046,"date":"2026-05-29T13:28:57","date_gmt":"2026-05-29T17:28:57","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=52046"},"modified":"2026-05-29T13:28:57","modified_gmt":"2026-05-29T17:28:57","slug":"stopthemadness-pro-26","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2026\/05\/29\/stopthemadness-pro-26\/","title":{"rendered":"StopTheMadness Pro 26"},"content":{"rendered":"

Jeff Johnson<\/a>:<\/p>\n

\n

My Safari extension StopTheMadness Pro has a feature to protect private windows. In other words, StopTheMadness Pro stops websites from detecting private windows in Safari. I won’t explain how my feature works, but in this blog post I’ll explain how websites detect private windows.<\/p>\n<\/blockquote>\n\n

Jeff Johnson<\/a>:<\/p>\n

\n

I’m sorry to say that at this time I don’t plan to make any additions or enhancements to YouTube-specific features in StopTheMadness Pro.<\/p>\n

[…]<\/p>\n

The downsides of adding YouTube-specific features to StopTheMadness have outweighed the upsides. YouTube is an endless time sink. Even though StopTheMadness is not a YouTube-specific extension, I’ve spent more time working on YouTube than on every other website in the world combined<\/em>. Seriously. And YouTube doesn’t remain static; Google continues to change YouTube, sometimes breaking my features, requiring even more work.<\/p>\n<\/blockquote>\n\n

I generally use Downie<\/a> for YouTube videos, and it requires an insane number of updates to keep working.<\/p>\n\n

Jeff Johnson<\/a>:<\/p>\n

\n

Although DuckDuckGo doesn’t allow you to specify the number of results per page, it does have a setting<\/a> to enable infinite scroll, which is more convenient than Google’s strict division of results into pages of 10 links. The problem is that I prefer to use private windows for the majority of my web browsing, especially searches, which means that any settings would disappear when the window is closed. DuckDuckGo claims to support URL parameters for settings<\/a>, but in my testing, the parameters don’t actually seem to work reliably.<\/p>\n

As you might expect, my solution to the problem is my web browser extension StopTheMadness Pro<\/a>.<\/p>\n<\/blockquote>\n\n

Jeff Johnson<\/a>:<\/p>\n

\n

This update brings a great new feature: autoclick buttons! Specify a button on a website to be clicked automatically. For example, agree to terms and conditions, reject cookies, or close a popup.<\/p>\n<\/blockquote>\n\n

I’ll have to report back on how well this works across various sites, but it sounds great<\/a> and was successful in my initial testing:<\/p>\n\n

\n

In selection mode, manually click the button that you want to be automatically clicked.<\/p>\n

[…]<\/p>\n

StopTheMadness Pro uses CSS selectors<\/a> to autoclick buttons. In order to click a single, specific button, and not mistakenly click the wrong buttons, StopTheMadness Pro searches for a unique way to identify the button on the page. If a unique identifier cannot be found, then the autoclick feature can’t be used with the button.<\/p>\n

By default, StopTheMadness Pro attempts to find the button on the web page for 10 seconds after the page loads, and then it stops looking. <\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n