Blocking Autoplay Videos on TechCrunch via uBlock Origin
Technical filter implementation to disable intrusive JW Player and Connatix video embeds.
1Intrusive Media Playback Issues
TechCrunch articles currently feature autoplaying videos embedded directly within the content flow. Simply hiding the visual element is insufficient because the JW Player instance continues executing in the background. This consumes unnecessary system resources and bandwidth, necessitating a more robust technical intervention to stop the underlying scripts from loading entirely.
2Identifying Video Vendor Infrastructure
The site utilizes JW Player for primary content and Connatix for floating advertisement players. These services rely on external script libraries that trigger automatically upon page load. By targeting these specific third-party domains, users can effectively sever the connection before the media player initializes, preventing both audio playback and background processing.
3Required Browser Configuration
This solution is specifically designed for the full Manifest V2 version of uBlock Origin on Firefox. Users must access the Dashboard and navigate to the My filters tab to apply the changes. The uBO Lite version lacks the necessary granular control over network requests required to block these specific script domains.
4Network Blocking Implementation
The filter set includes specific network rules targeting content.jwplatform.com, ssl.p.jwpcdn.com, and connatix.com. By applying these rules restricted to the techcrunch.com domain, the browser prevents the initialization of the video player scripts. This ensures that the media components are never fetched from the server, effectively silencing the autoplay behavior during article navigation.
5Cosmetic Rule Application
Beyond blocking the network requests, cosmetic rules are employed to remove the empty containers left behind by the blocked players. The selectors techcrunch.com##.wp-block-techcrunch-jw-player-embed and techcrunch.com##.jw-player-inline-promo target these specific DOM elements. This cleanup ensures the article layout remains visually consistent without leaving awkward gaps or broken placeholders on the page.
6Vendor Dependency Risks
While the cosmetic rules will likely persist even if TechCrunch changes its video provider, the network rules are vendor-specific. If the site switches to a different video platform, the existing filters will fail to stop the new player. Users would then need to identify and block the new script sources to maintain functionality.
7Browser Extension Compatibility
The distinction between full uBlock Origin and uBO Lite is critical for this implementation. The full version allows for complex rule sets that combine network blocking with cosmetic filtering. Because uBO Lite operates under more restrictive browser API limitations, it cannot execute these specific script-blocking commands, rendering this method ineffective on that version.
8Maintaining Optimal Browsing Performance
Implementing these filters provides a cleaner reading experience by eliminating unwanted media noise. By preventing unnecessary script execution, users reduce their browser's memory footprint and data usage. Regularly auditing custom filter lists remains a best practice for power users looking to maintain control over their web environment and mitigate intrusive site behaviors.
Original article: Hacker News: Front Page — Blocking Autoplay Videos on TechCrunch via uBlock Origin