Glad to hear it's working well for you - if you'd like to discuss cases that don't work quite right please feel free to post over at https://github.com/wingman-jr-addon/wingman_jr/issues Thanks!

(Update: Not only did Umbrella123 need to change those settings but also use the unreleased branch of code. I'll see if I can get a release out there soon...)
(Update 2: Release 3.3.3 is out with the fix!)

Possibly! If you look in the review below by kitsunesan, you'll notice that they had the same problem. I entered a bug for this and they were able to help me track down the problem. By any chance are you running Linux / Ubuntu 22.04? What we found was that the prediction library was producing slightly different results with the same input across different calls, which caused the addon's self-checks to fail and ultimately to restart. I was hoping to squeeze a thing or two more in to the next release as per Drago's review below but if we have multiple folks reporting crashing issues like this I'd like to get a release out there sooner rather than later. You can see the issue details over at https://github.com/wingman-jr-addon/wingman_jr/issues/185
If you're able to either update your review with further platform information or add it into to the posted issue, I'd definitely appreciate it as it'll help me debug any issues there. Thanks!

(Update: fix in release 3.3.3!)

Thanks for the feedback kitsunesan!
I've gotten scattered feedback about this as well. If you're able, can you please post a few more details on https://github.com/wingman-jr-addon/wingman_jr/issues/185? If not, can you maybe add a few more details here about what you see? I'm assuming Firefox is giving the "Keep tabs hidden?"-style prompt but let me know if there is more going on here.

Drago,

(Update: v3.3.4 hopefully addresses the character issue you're seeing - let me know!)

Thanks again for the detailed review! You've got a lot to unpack here, so let's dig in. I've been looking at this off and on but I'm finally able to respond with at least some notes.

Recognition of naughty GIFs: yes, this is an area for improvement. I reviewed the page listed and how the addon was scanning. There might be some smaller secondary issues with the GIF animation frames as the frames are quite heavily "incremental", but the primary issue I saw was just that the content was scanned as expected but not flagged. Unfortunately, this isn't just a problem here, dealing with scanning animation is I believe a much harder problem in general academically. I've entered an issue here (https://github.com/wingman-jr-addon/model/issues/6) but sadly I don't have a quick fix on the way for you.

Video scanning: So it sounds like this is working more or less as designed- there would only be a small red V in the plugin area for the block; however, the experience just isn't very good.
Two potential usability ideas: 1) Add some sort of a setting to only scan up to a certain amount of video and then assume the rest is good. The truth is that video sees a lot of images even at the lower sampling rate and the chances of some section erroneously getting flagged is high, especially with the model not being trained on video. 2) Add better notification about what happened. Users should be able to understand that the video was blocked. I try to do this to a certain extent but unfortunately it's not possible (?) to insert the Wingman Jr block logo in the video. Maybe this could use another pass.
Let me know if either of these sound helpful. Tracking here: https://github.com/wingman-jr-addon/wingman_jr/issues/188

Cloudflare: unfortunately, I'm already caching the DNS results from Cloudflare (at least within the lifetime of the addon running), so the obvious improvement is already done.

Special characters: your feedback with the exact webpage is helpful! I'm not quite sure how to fix it yet, but I can reproduce the issue rather than just guessing, and I have an idea of what I can try. Tracking here: https://github.com/wingman-jr-addon/wingman_jr/issues/186

Thanks for the feedback, and I hope the addon works well for you.

Thanks Simon! I hope you enjoy using it and please let me know if you run into any issues.

Hello! Thanks for the detailed report. For those interested in the end result only, there was a bug that seems to have affected private mode primarily and I have a minor bug fix release 3.3.1 rolling out to correct the issue.

Now for the more technical details.

As a fellow developer, I could see where you would get the impression that the two use cases you described (image reveal, and I'm assuming "view image" is the recently moved function "open image in a new tab") are not supported because they were broken on this site. Fortunately, both are generally supported. The way the code actually works largely bypasses DOM mutation observers and instead drops directly down to the connection itself (webRequest filtering). While this can have issues, it is generally robust to DOM types of issues like you describe.

When I took a look at your report, I was able to reproduce the issue in private mode - but it appears to have more to do with a subtle JS quirk than with either of those two cases per se. See the root cause (with original reported issues linked) here: https://github.com/wingman-jr-addon/wingman_jr/issues/180 I'm still not 100% sure what is triggering the differentiation in behavior, but apparently something with the assignment to the captured variable fails under some conditions, so I've pulled it.

At any rate, when you get a chance and 3.3.1 is out, would you be willing to give it another shot and see if your issue is resolved? (Do note you may wish to bump up the zone manually to untrusted for vndb.org for best results.) I'm glad to hear that it sounded like it was working well for you on other sites, so if I'm able to turn this around into a positive review, I'd appreciate a second chance. Thanks!

Cranky, thanks for the thoughtful review - I appreciate you taking the time to give more detailed feedback. I'll be thinking about your requests here. As a starting point, there is a GitHub issue open regarding the small image scanning - feel free to join the conversation at https://github.com/wingman-jr-addon/wingman_jr/issues/157
I hope you enjoy the addon, and feel free to leave further feedback using the "Feedback" link in the addon as well.
(Update: Issue around custom images for silent mode - https://github.com/wingman-jr-addon/wingman_jr/issues/166)

Thanks! At this time, no - but it's definitely something I've considered and if you'd like to talk about it please leave some comments over at the GitHub issue I have for that exact feature: https://github.com/wingman-jr-addon/wingman_jr/issues/40 Look forward to discussing this with you further.

Hey thanks! If you happen to be a programmer, you may be interested to know that I have the model released independently over at this repository: https://github.com/wingman-jr-addon/model

Thanks! I appreciate you leaving a review. Let me know if you have any bug reports or feature requests using the feedback link in the addon or over at https://github.com/wingman-jr-addon/wingman_jr Hope it continues to work well for you!

You're most definitely welcome!

Regarding that bug: that is, as far as I know, a limitation of the underlying webRequest API. I do not believe that there is a way to hook that when the URL is visited directly via that API, and I haven't looked into other API's to try to do so. I hadn't set up a dedicated repository with issues for just the plugin yet, and you gave me a great reason to do so! I'm now tracking your bug/request over here: https://github.com/wingman-jr-addon/wingman_jr/issues/1
(UPDATE: I'm wrong! You can do this with the "main_frame" webRequestType. Watch issue for more details.)
(UPDATE 2: Issue has a proposed fix, slated for next release!)
(UPDATE 3: Fixed in latest release!)

Regarding the model: I'm actually not using nsfwjs for this. It's currently a MobileNetV2 finetune on a dataset built from scratch. The underlying model itself is on four categories: safe, questionable, racy, and explicit; the plugin blends those into the number you see presented. If you're interested in further discussion on exposing model internals etc. please post a GitHub issue and we can continue there.

Thanks for taking the time to review the addon and give some feedback!

I 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())

Yes, it is open source! (See details here: https://addons.mozilla.org/en-US/firefox/addon/wingman-jr-filter/license/) I do not have the source in a standalone repository (it is in a repo with other source I do not wish to open at this time), but you can download the XPI file by going to the addon to enable it and right-clicking and "Save Link As". The XPI file can simply be changed to a .zip extension and opened up to see the source.
Let me know if you have any questions; hopefully the source is short and easy to follow.

(UPDATE: I now have a GitHub here - https://github.com/wingman-jr-addon/wingman_jr)

Thanks for the kind words - I'm glad it seems to be working well for you! Got any feature requests?