webextensions
AdNauseam
webextensions | AdNauseam | |
---|---|---|
36 | 40 | |
561 | 4,393 | |
1.2% | - | |
8.3 | 0.0 | |
4 days ago | 28 days ago | |
Bikeshed | JavaScript | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
webextensions
-
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
-
For your next side project, make a browser extension
Somewhat tangentially, I've been pushing for a popup/overlay API that allows to specify the position and size, and doesn't require any origin permissions.
https://github.com/w3c/webextensions/issues/307
AdNauseam
-
YouTube's Ad Blocker Crackdown Is Getting Harder to Dodge
It does not actually clicks on the ads. It sends the request to ad server but does not execute any response from the server, so it's safe to run
https://github.com/dhowe/AdNauseam/wiki/FAQ#how-does-adnause...
- AdNauseam: uBlock Origin fork silently clicking ads on behalf of users
-
AdNauseam: uBlock Origin fork silently clicking ads
>https://github.com/dhowe/AdNauseam/wiki/FAQ#how-does-adnause...
>AdNauseam 'clicks' Ads by issuing an HTTP request to the URL to which they lead. In current versions the is done via an XMLHttpRequest (or AJAX request) issued in a background process. This lightweight request signals a 'click' on the server responsible for the Ad, but does so without opening any additional windows or pages on your computer. Further it allows AdNauseam to safely receive and discard the resulting response data, rather than executing it in the browser, thus preventing a range of potential security problems (ransomware, rogue Javascript or Flash code, XSS-attacks, etc.) caused by malfunctioning or malicious Ads. Although it is completely safe, AdNauseam's clicking behaviour can be de-activated in the settings panel.
Isn't this easily detectable? XHRs are easily detectable through various headers, so it's trivial to filter out the fake traffic from this extension. Failing that, thanks to ad fraud there's a whole industry of bot/ad fraud detection firms using browser fingerprinting and behavioral analysis to detect fake ad clicks. I have no doubt that an extension that's "clicking" on every ad using XHR is going to get detected and filtered.
- Noiszy: A browser plugin that creates meaningless web data – digital “noise.”
-
Subreddits have proposed a blackout from June 12-14. Third party users should join them and avoid Reddit during that period.
I'd think it's infeasible for advertisers to regularly audit third-party apps on reddit's behalf to make sure the ads they're paying to display aren't being requested but cosmetically hidden or even shadow-clicked. I'm sincerely curious if there are any example platforms that do this with their API; I can't find anything after a search.
-
take your daily medicine guys
What is your opinion on AdNauseam?
-
uBlock Origin/Ad Nauseam and YouTube
Please use this page to report issues or ask questions about Ad Nauseam. This specific issue has already been addressed:
-
Lifelong Chrome user switching to Firefox, are there any extensions that are a MUST on the browser?
Other than that, Libredirect and AdNauseam to be pretty neat. Allows me to avoid using certain sites directly and when I do, I mess with their ads engagement enough. A bit petty, but I'll take what I can get.
- The vast majority of us are being tracked with surveillance tech. These are the systems you need to know about
What are some alternatives?
graphql-jit - GraphQL execution using a JIT compiler
uBlock - uBlock Origin - An efficient blocker for Chromium and Firefox. Fast and lean.
nyxt - Nyxt - the hacker's browser.
anti-adblock-killer - Anti-Adblock Killer helps you keep your Ad-Blocker active, when you visit a website and it asks you to disable.
h264ify - A Chrome extension that makes YouTube stream H.264 videos instead of VP8/VP9 videos
bypass-paywalls-firefox - Bypass Paywalls for Firefox android
SingleFile-MV3 - SingleFile version compatible with Manifest V3. The future, right now!
block - Let's make an annoyance free, better open internet, altogether!
obelisk - Go package and CLI tool for saving web page as single HTML file
Never-Consent - Never consent to any GDPR consent management platform
Fenix - ⚠️ 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
privacypossum - Privacy Possum makes tracking you less profitable