SaaSHub helps you find the best software and product alternatives Learn more →
Webextensions Alternatives
Similar projects and alternatives to webextensions
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Fenix
Discontinued ⚠️ Fenix (Firefox for Android) moved to a new repository. It is now developed and maintained as part of: https://github.com/mozilla-mobile/firefox-android
-
bromite
Bromite is a Chromium fork with ad blocking and privacy enhancements; take back your browser!
-
ArchiveBox
🗃 Open source self-hosted web archiving. Takes URLs/browser history/bookmarks/Pocket/Pinboard/etc., saves HTML, JS, PDFs, media, and more...
-
browser_extension
A browser extension that redirects popular sites to alternative privacy friendly frontends
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
uMatrix
Discontinued uMatrix: Point and click matrix to filter net requests according to source, destination and type
-
ExtPay
The JavaScript library for ExtensionPay.com — payments for your browser extensions, no server needed.
-
uBlock-Safari
uBlock Origin - An efficient blocker for Chromium, Firefox, and Safari. Fast and lean.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
webextensions reviews and mentions
- Show HN: I made a CLI tool to create web extensions with no build configuration
-
Chrome's next weapon in the War on Ad Blockers: Slower extension updates
I've edited my comment to also include a link to the Chrome docs, but that FAQ entry also has the link to an issue in the webextensions repository indicating it's a limitation of MV3: https://github.com/w3c/webextensions/issues/112
-
There are no strings on me
Google outlawing dynamic code in Web Extensions/mv3 is a travesty of high order. There's no place I want to be able to be more alive than my agents. Yet my agents must all be dead. For shame, ye villains.
https://github.com/w3c/webextensions/issues/139
This post definitely was quite a technical explanation. The opening framing, to me, means the world.
-
Chrome Users Beware: Manifest V3 Is Deceitful and Threatening – EFF
The other big change of mv3 that gets no coverage but which is dear to me is that mv3 outlaws any kind of dynamic code. The whole app has to be statically defined. This makes it much easier to know what's running, since an extension can no longer go pull in extra code, but it greatly reduces what you can do as an extension too. Extensions have to have all behaviors predefined. I can't dial home & load my behaviors. Here's the issue, https://github.com/w3c/webextensions/issues/139
For a while it meant that userscripts didn't have any way to run. So Google introduced a new API for user scripting. But those extensions only run in "developer" mode. I'm guessing that means when devtools are open?
I agree a lot with your premise. It sure seems like Google is targeting everyone with these changes, but that better real affordances & escape hatches need to be builtin to not maim the lives of power users. It took a long long time to come up with a userscript solution, and it seems like an awful doesnt-work-for-me workaround (I use userscripts not to dev but to modify everyday experiences). Chrome just hasn't been taking their obligation to user agency seriously.
-
Firefox users may import Chrome extensions now
> the extension APIs are standardised enough that this is actually possible a lot of the time
A bit off topic, but as a co-chair of the WebExtensions Community Group[1] (WECG) I'm a bit touchy about the calling WebExtensions "standardized." A few years back the Browser Extensions Community Group[2] created a spec for WebExtensions, but it never reached a state that we'd normally refer to as a web standard. (Technically W3C community groups can only produce "Reports" and these documents are not on the standards track.[3])
FWIW, I'm very bullish about specifying and (hopefully) standardizing the WebExtensions platform. I'm especially excited about having a good chunk of dedicated time to sit with browser folks at TPAC 2023[4] and try to work out some open questions about where we're going and how we're going to get there.
[1]: https://github.com/w3c/webextensions/
-
uBlock Origin Lite now available on Firefox
While I was trying to find out what Firefox's limits are I came across this interesting issue on the W3C's webextensions repo: https://github.com/w3c/webextensions/issues/319
4 days ago the Chromium developers proposed upping the limit for certain types of declarativeNetRequest rules based on data AdGuard provided on real world rule lists.
-
Google's trying to DRM the internet, and we have to make sure they fail
Manifest v3 is used for Chrome's extensions system. The proposal appears to limit what extensions have access to, and what they can do in Chrome. It is proposed as a W3C standard by Google. It is being tracked at the W3C at https://github.com/w3c/webextensions/issues/44.
-
Manifest V2 Chrome Extension Phaseout Delayed Until 2024
Google is not even close to finishing MV3: "On the userScripts API, the proposal has been merged into the WECG but the engineering work has not started yet." https://github.com/w3c/webextensions/blob/f8f430f1904c2a6fa8...
MV2 is sticking around until at least 2024.
-
Here’s what’s going on in the world of extensions
Some, but not all, limitations are highlighted in this thread: https://github.com/w3c/webextensions/issues/72
- Firefox 109.0 released
-
A note from our sponsor - SaaSHub
www.saashub.com | 4 May 2024
Stats
w3c/webextensions is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of webextensions is Bikeshed.
Sponsored