Firefox Remains Only Browser Supporting uBlock Origin
I'm surprised to see Firefox standing alone as the only major browser still compatible with uBlock Origin, a popular ad blocker. This development comes after Google Chrome and Microsoft Edge announced they're abandoning support for the extension. It's not every day you see a browser taking a stance that's so clearly at odds with the rest of the industry.
The writing's been on the wall for a while now - with Microsoft Edge soon to lock out uBlock Origin and other ad-blocking extensions that run on Manifest V2 architecture, it was only a matter of time before the other browsers followed suit. But what's interesting is that Firefox is choosing to go against the grain, at least for now. I'm curious to see how this plays out, especially given the potential implications for users who rely on uBlock Origin to block ads and trackers online.
What's driving this decision, and what does it mean for the future of ad blocking on the web? It's clear that the relationship between browsers, ad blockers, and website operators is more complicated than ever. As someone who's been following this space for years, I've seen the balance of power shift back and forth - but this latest move by Firefox has me wondering what's next. Will other browsers follow Firefox's lead, or will they continue down the path of limiting ad blocker functionality?
Introduction to uBlock Origin
uBlock Origin is a popular browser extension that's widely used for its ability to block ads, trackers, and malware. It's significant not just because of its popularity, but also because it's still supported by Firefox, despite being based on Chromium's Manifest V2 architecture. This is notable because other browsers, like Chrome, have announced plans to phase out support for Manifest V2 extensions in favor of Manifest V3.
The fact that Firefox still supports uBlock Origin is a major draw for many users. As one user put it, "This is officially Firefox's killer app. I will never go back to Chrome so long as uBlock Origin is supported on Firefox." Mozilla has confirmed that they have no plans to drop support for uBlock Origin, with a representative stating "Our support for uBlock Origin isn't going anywhere." This commitment to supporting popular extensions is a major factor in Firefox's appeal, and it's likely a key reason why many users choose to stick with the browser.
From a technical standpoint, uBlock Origin's architecture is based on Chromium's Manifest V2, which provides a lot of flexibility and power for extension developers. To install uBlock Origin on Firefox, you can use the following command in your terminal:
firefox https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/Then, click the "Add to Firefox" button to install the extension.
It's worth noting that uBlock Origin's popularity and significance can be measured in part by its user base and the number of blocks it performs. With millions of users worldwide, uBlock Origin is one of the most popular ad blockers available, and its ability to block ads, trackers, and malware has made it a essential tool for many internet users.
The Shift Away from Manifest V2
I've been following the developments around Manifest V3 and the community's reaction to the changes. The fact that a user has created a custom Chrome extension using Claude code to replace seven standard extensions is telling. It highlights the desire for flexibility and control that some users feel is being taken away by the limitations imposed by browsers like Chrome and Microsoft Edge.
This shift away from Manifest V2 is not just about the technical changes, but also about the values that browsers are prioritizing. I think the move towards Manifest V3 underestimates the friction that users will experience as their favorite extensions are limited or broken. The fact that a user has gone to the trouble of creating a custom extension to replace seven others suggests that there is a significant need for this kind of functionality.
The community reaction to these changes has been mixed, but the creation of custom extensions like this one shows that users are willing to go to great lengths to maintain their current workflow. As browsers continue to evolve and impose new limitations, I wonder how many users will be driven to create their own custom solutions. Will we see a proliferation of custom extensions, or will users eventually adapt to the new reality? The fact that one user has already found a way to work around the limitations is a testament to the ingenuity of the community, but it also raises questions about the long-term sustainability of this approach.
I'm left wondering what the future holds for ad blockers and other extensions that rely on the old manifest. As browsers continue to tighten their grip on what is allowed, will we see a new wave of innovation in the extension ecosystem, or will users be forced to adapt to a new reality with limited options? One thing is certain: the shift away from Manifest V2 will have significant implications for users and developers alike, and it will be interesting to see how this plays out in the coming months.
Practical Implications for Users
I think the real test of Claude's code will be in how widely it's adopted by developers and users. One user has already created a custom Chrome extension using the code, which is a promising start. This extension replaced seven standard extensions they previously used, which is a significant reduction in overhead. What's interesting is that this user was motivated by the limitations on ad blockers in other browsers like Chrome and Microsoft Edge. This suggests that users are looking for ways to work around these limitations, and Claude's code may provide a viable alternative.
What I'm not sure about is how sustainable this approach will be in the long term. While it's great that users have the option to create custom extensions, it's unclear how many will have the technical expertise to do so. Additionally, the fact that one user was able to replace seven extensions with a single custom one raises questions about the complexity of the existing ecosystem. I think it's possible that we'll see a proliferation of custom extensions, which could lead to a new set of problems around maintenance and support.
The community reaction to Claude's code has been largely positive, but I think it's also important to consider the potential risks. If users start relying on custom extensions to work around browser limitations, it could create security vulnerabilities or compatibility issues. On the other hand, it could also drive innovation and push browser developers to rethink their approach to extensions. I'm curious to see how this plays out, and whether Claude's code will be a catalyst for change in the browser ecosystem.
One thing that's certain is that the next few months will be crucial in determining the trajectory of Claude's code. Will we see a wave of custom extensions that challenge the status quo, or will the limitations of the approach become apparent? I'm inclined to think that the outcome will be somewhere in between, with both positive and negative consequences emerging. Ultimately, the question on my mind is: what will it take for custom extensions to become a mainstream phenomenon, and will browser developers be willing to adapt to this new reality?
Conclusion
Firefox didn’t pick this fight—it just wasn’t part of Chrome’s power grab. Microsoft locking out Manifest V2 in Edge isn’t just a technical shift; it’s a calculated move to make ad-blocking harder for users who actually want it. And outside Firefox, there isn’t much left. DuckDuckGo bowed to Chromium’s rules, Apple never bothered, and the few remaining non-Chromium browsers treat uBlock Origin like a security risk instead of a feature.
For now, Firefox is the last browser where uBlock Origin works like it’s supposed to. But how long that lasts is anyone’s guess—Mozilla’s been bleeding ground for years, and the pressure to align with Chromium’s restrictions isn’t going away. If Firefox ever falls in line, there won’t be another browser left to switch to.