Closed BooBerry closed 5 years ago
ameshkov
commented
7 years ago @arantius
I'm working on making something called Greasemonkey that runs user scripts manage to exist in a FF57+ world.
Cheers!
How it goes? I reckon this is the WebExt branch: https://github.com/arantius/greasemonkey/tree/webbymonkey
seba2282
commented
7 years ago @jspenguin2017 In last time I can't mount your script on Edge + Tampermonkey. What did you make with scripts. If I uninstall Tampermonkey, I see new tab with txt your script in Edge. If I have Tampermonkey, script isn't loading and install... Earlier worked medium....
BooBerry
commented
7 years ago Yeah, it is, I'll post a link here once the first alpha is out.
Oh? Is it listed on Git yet?
jspenguin2017
commented
7 years ago @seba2282 I wrote it in ECMAScript 8, Edge probably haven't caught up yet.
ameshkov
commented
7 years ago Oh? Is it listed on Git yet?
Not yet, I don't like to publish anything until it's at least partly ready.
arantius
commented
7 years ago How it goes? I reckon this is the WebExt branch: https://github.com/arantius/greasemonkey/tree/webbymonkey
Exactly. It's functional, minimally. You can install and use it for some real use cases. Most recent change has been adding API support, but new async incompatible versions of them.
seba2282
commented
7 years ago @jspenguin2017 Ok. Sorry, I write it, but I see future Adguard with dedicated filter with list and scripts Protector Team Adguard. Don't Angry on my opinion. 😊
There's been multiple topics on the forums about this lately, so it I thought it might be time to post something about it here.
It doesn't look like Anti-Adblock Killer (both the filter list and userscript) is a viable solution to any new Anti-Adblock mechanisms as AAK development has slowed down considerably (e.g. 1 or 2 updates in 6+ months time - no filter updates since December). There's a fork of AAK called Adblock Protector, but it's focus seems to be using it alongside uBlock Origin. This may mean the filter list likely has rules uBO supports (e.g. different syntax).
Perhaps it's time Adguard has it's own dedicated Anti-Adblock solution(s) in place? (Okay, yes, I already know there's active Anti-Anti-Adblock happening in the filter lists as they're reported and reproduced, but this is something dedicated to just this).
At the very least, there can be an Anti-Adblock filter. While it'd make sense to merge such rules into other filter lists (English, Spyware, Annoyances) users may not know that there's Anti-Adblock rules present, hence the potential need for a specific filter just for this. Could use AAK as a starting point, or just start with something completely new.
The benefit to this approach is, the use of a userscript alongside the filter list may not be needed at all. I say may not because of the Adguard browser extensions. This might be a situation when a Adguard team-developed userscript could be an option for those with a script manager (e.g. Tampermonkey) alongside the Adguard browser extensions. Ultimately, it all depends what the Adguard browser extensions are capable of supporting. However, Adguard for Windows, Adguard for Mac, Adguard for Android, etc. should be able to use only a filter without any userscripts needed.
So here's what came to mind in a nutshell;
1) Have a Adguard team-developed Anti-Adblock filter list that covers all languages and all sites (not language-specific) that users can enable and have some peace of mind knowing there's some form of Anti-Anti-Adblock happening. This can support everything required for working rules, without the need of an additional userscript.
1a) If need be for the Adguard browser extensions, an additional userscript that can be added to the user's script manager (e.g. Greasemonkey, Tampermonkey, etc.). If the browser extensions don't require this, skip it completely!
2) New forum section under Filter Rules called Anti-Adblock issues (or something like this) where users can report sites where they encounter Anti-Adblock. Require direct URLs, Adguard they're using (Windows, Mac, Android, browser extensions, etc.), browser(s) they're using, screenshots if possible, enabled filters they're using, etc.
That's basically it. Thoughts?