persistent-serviceworker
uBlock
persistent-serviceworker | uBlock | |
---|---|---|
8 | 2,992 | |
20 | 43,126 | |
- | - | |
2.8 | 9.9 | |
4 months ago | 11 days ago | |
JavaScript | JavaScript | |
- | 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.
persistent-serviceworker
-
How to keep a serviceworker (background.js) alive in a chrome extension
Here you go persistent-serviceworker.
-
[AskJS] Do specification authors and implementers listen to developers in the field?
The ServiceWorker becoming inactive in 5 minutes per MV3 is a debacle. Workarounds exist and the code to implement keeping the ServiceWorker persistent, e.g., to stream live radio station from the ServiceWorker to the client winds up not saving any resources - we have to keep something running to keep the service worker running. You would be hard-pressed to count how many issues in the wild have been filed in multiple source code repositories just on that lack of functionality - for years now, e.g., Need help to understand and use this #2.
-
[AskJS] What are the worst case scenarios for programmatically setting arbitrary Web pages (Origins) as Client or WindowClient of a ServiceWorker?
There are workarounds which involve using an iframe https://github.com/guest271314/persistent-serviceworker/tree/main/chromium_extension_web_accessible_resources_iframe_message_event or window.open() https://github.com/guest271314/sw-transfer-stream or and offscreen document https://github.com/guest271314/offscreen-webrtc with WebRTC - however that involves loading an entire HTML document, and each has its own deficienfies - with all of the Window features that we do not really need just to transfer data between the Web page I have control of and the ServiceWorker I have control of.
-
Transfer ArrayBuffer from ServiceWorker to Web page
One approach for your requirement is to append an iframe with src set to an HTML document listed in "web_accessible_resources" to an arbitrary document and use postMessage() from the Web page to the iframe, then from the iframe to the MV3 ServiceWorker, see https://github.com/guest271314/persistent-serviceworker/tree/main/chromium_extension_web_accessible_resources_iframe_message_event.
-
How to have background:persistent in V3?
See https://github.com/guest271314/persistent-serviceworker
-
Manifest 3 limitation with background.js
Yes, it is possible to keep an extension or non-extension ServiceWorker persistent, active indefinitely https://github.com/guest271314/persistent-serviceworker.
-
Confirming isolation of cross-domain iframe (chrome extension context)
If you host the HTML for and use
"web_accessible_resources"
in manifest.json the</code> can communicate directly with MV3 <code>ServiceWorker</code>. </p> <p>To keep MV3 <code>ServiceWorker</code> persistent see <a href="https://github.com/guest271314/persistent-serviceworker">https://github.com/guest271314/persistent-serviceworker</a>.</p> </div>
-
Manifest v3: how to mitigate the timeout of the service worker?
I utilize "web_accessible_resources" with an , where chrome.* API's are exposed, and does not become inactive.
Some workarounds to keep MV3
ServiceWorker
active Persistent ServiceWorker.
uBlock
- Apr 24th is JavaScript Naked Day – Browse the web without JavaScript
- Mobile Ad Blocker Will No Longer Stop YouTube's Ads
-
Some notes on Firefox's media autoplay settings in practice as of Firefox 124
Check out uBlock Origin's per site switches [1]
[1]: https://github.com/gorhill/uBlock/wiki/Per-site-switches#no-...
-
Brave's AI assistant now integrates with PDFs and Google Drive
If ads, in particular on YouTube, are the problem, anything Chromium-based is probably only going to get worse and worse (see [1] and [2]). So that basically leaves you with Firefox and Safari.
I work for Mozilla (speaking for myself, of course), so I'll leave you to guess which I'd recommend :P
[1] https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...
[2] https://arstechnica.com/gadgets/2023/09/googles-widely-oppos...
-
X.org Server Clears Out Remnants for Supporting Old Compilers
https://github.com/gorhill/uBlock
Or if on mobile, it is well worth it to look up adblock options for the browser you use.
-
Mozilla thinks Apple, Google, Microsoft should play fair
What are the compelling advantages of Chrome nowadays?
Chrome is working to limit the capabilities of ad blockers:
https://www.malwarebytes.com/blog/news/2023/11/chrome-pushes...
Whereas a compelling advantage of Firefox is that uBlock Origin works best in Firefox:
https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...
Advertising networks have often been vectors for malware. Using an ad blocker is an important security measure. Even the FBI recommends ad blockers:
https://www.malwarebytes.com/malvertising
https://theconversation.com/spyware-can-infect-your-phone-or...
https://www.ic3.gov/Media/Y2022/PSA221221?=8324278624
-
Brave Leo now uses Mixtral 8x7B as default
> It allows for 30,000 dynamic rules
That is not what we mean by dynamic filters. From https://developer.chrome.com/blog/improvements-to-content-fi...
> However, to support more frequent updates and user-defined rules, extensions can add rules dynamically too, without their developers having to upload a new version of the extension to the Chrome Web Store.
What Chrome is talking about is the ability to specify rules at runtime. What critics of Manifest V3 are talking about is not the ability to dynamically add rules (although that can be an issue), it is the ability to add dynamic rules -- ie rules that analyze and rewrite requests in the style of the blockingWebRequest permission.
It's a little deceptive to claim that the concerns here are outdated and to point to vague terminology that sounds like it's correcting the problem, but on actual inspection turns out to be entirely separate functionality from what the GP was talking about.
> Giving this ability to extensions can slow down the browser for the user. These ads can still be blocked through other means.
This is the debate; most of the adblocking community disagrees with this assertion. uBO maintains a list of some common features that are already not possible to support in Chrome ( https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b... ) and has written about features that are not able to be supported via Chrome's current V3 API ( https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as... ). Of particular note are filtering for large media elements (I use this a lot on mobile Firefox, it's great for reducing page size), and top-level filtering of domains/fonts.
- uBlock Origin – 1.55.0
-
In 2024, please switch to Firefox
> "Its happened before"
> That's not an argument
It's a subheading to "2. Browser engine monopoly". The subsection's purpose is describing how bad things were during the IE monopoly to reinforce that it's something to be avoided.
> in fact you could counter-argue that IE left a lot of technical debt
That would be agreeing with the article, unless I understand what you mean.
> On top of that, the internet was very different back then.
In a way that now makes it harder for truly new competing engines to pop up due to increased complexity of the web.
> I'm still not convinced, why would I change my browser?
The points made in the article are:
* Increased privacy, opposed to willingly giving your data to an ad-tech company
* Helps avoid a browser engine monopoly which would effectively let Google dictate web standards
* It’s fast and has a nice user interface
Onto which I'd add:
* Content blockers work best on Firefox (https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...), doubly so when Manifest V3 rolls out
* Allows more customization of interface and home page
* UX improvements, like the clutter-free reader mode, aren't vetoed to protect search revenue as with Chrome (https://news.ycombinator.com/item?id=37675467)
-
Ask HN: Is Firefox team too small to do serious security tests?
Advertising networks are vectors for malware:
https://www.cisecurity.org/insights/blog/malvertising
https://www.malwarebytes.com/malvertising
https://theconversation.com/spyware-can-infect-your-phone-or...
So if you're concerned about security then you want the browser with the best ad blocker.
uBlock Origin works best in Firefox:
https://github.com/gorhill/uBlock/wiki/uBlock-Origin-works-b...
What are some alternatives?
developer.chrome.com - The frontend, backend, and content source code for developer.chrome.com
VideoAdBlockForTwitch - Blocks Ads on Twitch.tv.
offscreen-webrtc - Offscreen document <=> WebRTC Data Channel <=> Web page
Spotify-Ad-Blocker - EZBlocker - A Spotify Ad Blocker for Windows
playwright-dotnet - .NET version of the Playwright testing and automation library.
bypass-paywalls-chrome - Bypass Paywalls web browser extension for Chrome and Firefox.
sw-transfer-stream - MV3 ServiceWorker => ReadableStream => Web page
duckduckgo-privacy-extension - DuckDuckGo Privacy Essentials browser extension for Firefox, Chrome.
ServiceWorkerFullVideoBuffer - A service worker that buffers a full video, so when the video tag ask for ranges, these can be satisfied. Play + pause = buffer the whole video.
ClearUrls
captureSystemAudio - Capture system audio ("What-U-Hear")
AdNauseam - AdNauseam: Fight back against advertising surveillance