NSFW! archived.moe

[MonfGeiger]

added the nsfw tag because this websites also archives nsfw content in various boards like /b/ /h/ /d/ and so on; this happens on chrome/firefox as well with violentmonkey/greasemonkey and default ublock origin test settings

Test link: https://archived.moe/* (adding wildcard to show that it happens on every subsequent board-archive link)

was trying to find an old thread that had content I wanted to save myself, but this happened; wat do?

[jspenguin2017]

Did you just installed Violentmonkey or installed Violentmonkey then Script? I can't reproduce it and I see in the log that generic solution is triggered.

[jspenguin2017]

I thought my contribution guideline is clear enough, I'll start to ban people who don't read.

[MonfGeiger]

Didn't see that firefox was removed on the accepted browser-issue talk list, so I redid this on chrome with latest dev version of ublock origin, china list, ublock filter list, adblock warning removal list, and ublock script with violentmonkey (had it installed a month ago, took a bit to set ccleaner to stop deleting the script from violentmonkey)

apparently, despite the error you posted, it does work on chrome; but again, firefox is no longer an option to discuss concerning issues with ublock protector anymore?

[jspenguin2017]

@MonfGeiger The error crashes the detection script, that is expected and is good. FireFox users are no longer allowed to open issues here, if you insist on using FireFox, please head over to AAK-Cont.

[uBlock-user]

Avoid using FF, it will only create far more trouble for you aside from anti adblock issues, as its WebExtensions are heavily filled with bugs.

[MonfGeiger]

guess ill stick with chrome, report any issues, and hope the fixes translate to firefox, or switch filters

[jspenguin2017]

@uBlock-user Actually, it seems that FireFox's problem is not with the support of WebExtension, but with security policies, it follows the standard closely even if there is a good reason to not to, which creates incompatibility with uBlock Origin. There is a workaround in development in AAK-Cont repository, but it will either require another extension to break the security policy or a hacky way to patch some window properties.

[jspenguin2017]

@uBlock-user You got to toss code quality and performance out of the window if you want to support every browser. You got to use all sort of hacks to make things work on FireFox and Greasemoneky.
There are 2 ads server white listing that gone into uBlock filter after the breakage on FireFox... I probably should override that...