Reviews for Wingman Jr. Filter
Wingman Jr. Filter by Zephyr
Response by Zephyr
Developer response
posted 5 years agoI would definitely like to port this to Chrome, too; however, the methodology I'm using here simply doesn't exist in Chrome. I'd wanted to make this plugin for quite a while, and the confluence of TF.js and the WebRequest filtering API that became available in FF57 (specifically browser.webRequest.filterResponseData) are what made it possible.
The key API browser.webRequest.filterResponseData to filter inbound requests does not exist in Chrome, or the extension would probably port with no changes. Unfortunately, this has been a long standing request (since 2011!) for Chromium and there hasn't been a definitive path cleared for it (see https://bugs.chromium.org/p/chromium/issues/detail?id=104058). Additionally, with the recent changes being contemplated for "Manifest V3" the blocking versions of the similar, existing API's are being restricted and it's been causing quite a firestorm regarding e.g. ad blockers (See https://bugs.chromium.org/p/chromium/issues/detail?id=896897&desc=2#c23). Given that, it is unlikely to see this particular API or a different variant get supported by Chrome anytime soon.
However, others have take a different approach, trying to scan by element instead. Indeed, there is an ongoing effort as a Chrome extension with a similar goal - check out (https://github.com/purify-ai/geacc-crx). However, I did not take this approach as the primary method because I think it is difficult to reliably hook the images in this way for *pre*-filtering. (Note that webRequest also has some holes, with one important one being the handling of the first page of Google Image search results.)
Regarding reuse, as you can see the license is quite open, so feel free to use the code and/or the model. However, I do appreciate you reaching out as I'm curious to see where people would like this project to go. Let me know if you have further thoughts on the Chrome front! (Update: I created a GitHub issue: https://github.com/wingman-jr-addon/wingman_jr/issues/2)
(Update: I stated FF47+, should be FF57+ for filterResponseData())
The key API browser.webRequest.filterResponseData to filter inbound requests does not exist in Chrome, or the extension would probably port with no changes. Unfortunately, this has been a long standing request (since 2011!) for Chromium and there hasn't been a definitive path cleared for it (see https://bugs.chromium.org/p/chromium/issues/detail?id=104058). Additionally, with the recent changes being contemplated for "Manifest V3" the blocking versions of the similar, existing API's are being restricted and it's been causing quite a firestorm regarding e.g. ad blockers (See https://bugs.chromium.org/p/chromium/issues/detail?id=896897&desc=2#c23). Given that, it is unlikely to see this particular API or a different variant get supported by Chrome anytime soon.
However, others have take a different approach, trying to scan by element instead. Indeed, there is an ongoing effort as a Chrome extension with a similar goal - check out (https://github.com/purify-ai/geacc-crx). However, I did not take this approach as the primary method because I think it is difficult to reliably hook the images in this way for *pre*-filtering. (Note that webRequest also has some holes, with one important one being the handling of the first page of Google Image search results.)
Regarding reuse, as you can see the license is quite open, so feel free to use the code and/or the model. However, I do appreciate you reaching out as I'm curious to see where people would like this project to go. Let me know if you have further thoughts on the Chrome front! (Update: I created a GitHub issue: https://github.com/wingman-jr-addon/wingman_jr/issues/2)
(Update: I stated FF47+, should be FF57+ for filterResponseData())