Closed comfyneet closed 7 years ago
It's in there, it's called uBlock Protector.
uBlock Protector only works with Chrome, its owner also recommends to use AAK-Cont:
You must be using Chrome, uBlock Origin, and Violentmonkey to use this project. Do not want to switch your setup? Check out AAK-Cont!
I think you should add AAK-Coont to the filter list if the browser is not Chromium-based.
AAK has an old list that's bigger than the one on AAK-Continued.
@Atavic We're working on converting all that over.
I think you should add AAK-Coont to the filter list if the browser is not Chromium-based.
I use Chromium, uBlock Origin, but Tampermonkey (not Violentmonkey) so uBlock Protector is not compatible. AAK-Cont Filter For uBlock Origin https://gitlab.com/xuhaiyang1234/AAK-Cont/raw/master/dist/aak-cont-list-ubo.txt
Wait, what happened to jspenguin2017 and the AdBlock Protector List?
Wait, what happened to jspenguin2017 and the AdBlock Protector List?
I think AdBlockProtector was renamed to uBlockProtector https://github.com/jspenguin2017/uBlockProtector https://github.com/jspenguin2017/uBlockProtector/commit/2e63db94b255ae4164512f2660783115d88886ea
AAK-Cont Filter For uBlock Origin
has new URL:
https://xuhaiyang1234.gitlab.io/AAK-Cont/dist/aak-cont-list-ubo.txt
I hope they have the decency to add in the redirection line in the filter-list (I forget exactly what the syntax is now).
ublock Protector List in combination with ublock Protector Script is only for users of Chrome + uBlock Origin + Violentmonkey
I guess the amount of users that use exactly that combination is very small.
For all other combinations with ublock Origin AAK-Cont Filter For ublock Origin + AAK-Cont Userscript For uBlock Origin has to be installed.
Violentmonkey
Not Tampermonkey? Why is that?
Not Tampermonkey? Why is that?
Ask the author of uBlockProtector: https://jspenguin2017.github.io/uBlockProtector/
"Anti-Adblock Killer Continued" claims to work with Tampermonkey: https://xuhaiyang1234.gitlab.io/AAK-Cont/ https://gitlab.com/xuhaiyang1234/AAK-Cont#installation-instruction
Author of uBlock Protector told that this script works also with Tampermonkey, but „Violentmonkey is open source and is significantly lighter than Tampermonkey", so he recommends Violentmonkey. https://github.com/jspenguin2017/uBlockProtector/issues/249#issuecomment-305502991
Thanks, I wasn't aware that Tampermonkey is not completely open source. And whatever "significantly lighter" means, for normal usage. I doubt that you can really notice a difference, except some extreme cases maybe.
I always thought UI/UX was especially nice in Tampermonkey, but Violentmonkey doesn't look too bad either. Well, then there is the icon. The Violentmonkey extension icon looks rather, well, ugly. And you can't even hide it. I'd really prefer a much more minimalist icon.
Hey guys, couldn't find a spot for this so I'll just leave this here. This site http://prompt-sys60.info/chrm/ is a new phishing site posing as microsoft support preying on google's site ad service, found it while going to lowes.com. So far non of the filters have blocked it after updating and adding all 3rd party UbO filters. Its really really convincing, so just thought this might help if one of the admins see it.
@kageimposter This is not a place for this, please report it to list maintainers. Or better yet, to Google SafeBrowsing, which is built into every major browser except for IE/Edge, and to PhishTank. I already reported this to PhishTank, and Google Safe Browsing. Please do not remove your comment since I linked to it.
To followup: Google Safe Browsing had blacklisted the entire domain prompt-sys60.info
. (PhishTank, however, did not).
Can anyone please shed some light on why Greasemonkey is not supported? I've seen this same limitation on another userscript recently. Tampermonkey in FF seems to be compatible with more userscripts.
In case of uBlock Protector, Chrome(ium) only, hence no Greasemonkey.
No longer relevant in that case, because the uBlock Protector userscript is already (or is about to be) dropped, in favor of a real browser extension on the Chrome Web Store.
The problem with Greasemonkey in general is its incompatibility with WebExt, so unless Greasemonkey gets updated it won't work anymore starting with Firefox 57. Tampermonkey and Violentmonkey for Firefox will continue to work.
@Hrxn The problem is, Greasemonkey is the only extension that runs reliably at document start, and most anti-adblock killer scripts rely on running absolutely first. Tampermonkey and Violentmonkey have race conditions in this case, which is why uBlock Protector was converted to an extension.
@RoxKilly Are you asking if Greasemonkey is supported by uBlock Protector? Not officially.
For a Greasemonkey related project: https://xuhaiyang1234.gitlab.io/AAK-Cont/
The Userscript is now replaced by an extension, there are a lot of things that cannot be done with just a filter list, so an additional script based system is required. Please note that I overrode some whitelists with the filter and I'm not sure what will happen if you don't install the extension.
AAK-Cont will try to support Greasemonkey, but for technical reasons, that turns out to be a real pain, so the Userscript there is left in a half-working state, and is no longer in sync with uBlock Protector. That project may not go very far without additional help from the community.
@jspenguin2017 I'd like to help, but I have not so much time. Definitely hope your project gets more support!
@Atavic Don't thank me, @Giwayume is the main developer downstream.
@TonyTough I knew not many people have Violentmonkey installed, but I think they can just go install it, you can have both Violentmonkey and Tampermonkey installed at the same time. Anyway, that doesn't matter anymore, since the Userscript is changed to an extension, now the supported setup covers over half of total users as Chrome and Chromium have about 54% of market share.
@jspenguin2017 Thanks for the info. Would it be possible to also use a webextension for Firefox, so that ublock Protector List + webextension can be used with Firefox?
@TonyTough I can make the extension run on Firefox, but I don't have time to maintain that version. So no.
@jspenguin2017 uBlock Protector Extension works a treat on Firefox, better than AAK Cont Script
@lain566 You just loaded the unpacked extension? That's weird, I thought Firefox doesn't have the chrome
namespace... Anyway, if you want to use it I won't stop you, but I won't officially offer Firefox support.
If you want to offer Firefox support, fork the repository, change links to point to your repository and publish it in the extension store.
Also, does Firefox extension store support automated publishing from CI server? If not, it's going to be a pain to keep it up to date.
Actually, it does, and it supported that namespace before the Chrome browser was being developed: "Chrome" was originally a term for the browser's UI, outside the area where the Web page was drawn, and in browsers from the 1990s, it was usually shaded as if it were metallic and shiny; chrome:// URLs in Firefox go to parts of the user interface, although that might be XUL-specific and no longer supported when XUL is dropped in favor of the new extension system.
@lewisje The link is about the chrome:
scheme, I'm talking about the namespace, like chrome
in chrome.runtime.onMessage.addListener()
.
It does that too, but as a nod to compatibility.
@jspenguin2017 I use Chrome as first priority browser, and Firefox to test I would like to help you develop extension for firefox, but I'm not a developer.
To be able to install uBlock Protector extension on firefox, I have used this addon
https://addons.mozilla.org/firefox/addon/chrome-store-foxified/
@lain566 I think you can register a developer account pretty easily. Although I'm not sure if CI can push to Firefox store, that can add a lot of extra work, maybe Autohotkey can help...
Also, I'm not offering Firefox support not because it's hard to port the extension over, it's because I don't want to maintain the Firefox version. If you want to forcefully install the extension in a sketchy way, go for it, but don't tell me when it blow up.
@jspenguin2017 Do you hate firefox? don't worry about that, I will not ask you for help
A little bit, it caused me a lot of headaches.
@jspenguin2017 Ok, I understand
@Giwayume So Violentmonkey has a race condition? There is no open issue about that on its issue tracker... Could you report it there?
@Hrxn
I always thought UI/UX was especially nice in Tampermonkey, but Violentmonkey doesn't look too bad either. Well, then there is the icon. The Violentmonkey extension icon looks rather, well, ugly.
I agree: Violentmonkey has some CSS bugs and on Firefox looks ugly because of default Times New Roman, but that is Times New Roman's fault. But in Firefox you can change the font to anything you like. Also:
@bershan2 The race condition isn't really fixable since browsers are designed like that... There are a few hacks that sometimes work but... Why everyone cares about the UI? You look at that once a blue moon, functionalities are more important. Violentmonkey autocomplete is way better than Tampermonkey.
@jspenguin2017
The race condition isn't really fixable since browsers are designed like that...
Does older API used by Greasemonkey allow solutions without race conditions? I guess it does not matter since Greasemonkey will probably die with Firefox 57 release...
I agree that functionality is more important than the visuals, but visuals are a necessary part of UX thus deserve some attention too. Furthermore, (I think) most people fairly rarely write scripts and more often tweak them and use "Installed scripts" pane.
@bershan2 Yea, the old API is fully synchronous so it doesn't have race condition, but on the flip side, one website can lock up your whole browser. Tweaking script by changing its code? Or just settings? Settings needs to be handled elsewhere and that UI depends on the script author. I don't know how many scripts do you install, but I have at most 3. I combined all the small scripts I use into a personal extension, so I'm not using a script host right now. If you want beautiful animated UI, you can just throw in some Bootstrap or Polymer, it will be nice and shiny in no time. The price is speed, animation is costly, and not every device can afford that.
@bershan2
Does older API used by Greasemonkey allow solutions without race conditions?
Yes. Web Extensions are screwing over a lot of existing Firefox add-ons, since previously they could modify pretty much any code in the browser.
@jspenguin2017
From my experience modern phones & tablets handle CSS animations very well (anything that costs $200+).
@Giwayume Really? My $800 tablet can't quite handle it... Maybe because I'm doing other stuff when trying to animate the modal... If done right, the animation should be handled by GPU, hopefully soon we can use Bootstrap or Polymer without thinking about performance.
I hope our discussion did not diverge too far from the original topic...
@jspenguin2017 No, there is no animation, just SVG icons and expanding list, and no outside dependencies. There is even no :hover
. I'm not the author of the extension, but I do not think he will ever put in any animations.
I do not really use userscripts, I just like the idea of simple prototyping... I have yet to find any useful scripts. So far I really use only three extensions: uBO (obviously), HTTPS Everywhere (hope they'll improve memory usage) and Google Input Tools (could be better). Also, sometimes I just fix minor things without real reason.
@Giwayume Unfortunately, the computational cost does add up and although my devices cost significantly more than $200, I care about efficiency.
Update: typo fix.
@bershan2 If you care about speed, then don't worry about how things look. Violentmonkey uses quite a bit less RAM than Tampermonkey, it is a lot lighter. Animating beautiful user interface is not wasting. I didn't build my PC to look at UI from the 90s, but I don't care about UI as much when I'm on my tablet as it is significantly slower than my PC and do not have spare computation cycles to handle animation. Coding faster in a language you like is not wasting neither, uBlock Origin uses Python for build script, which is 10 to 50 times slower than JavaScript (Node.js), build script runs once from time to time, its efficiency doesn't matter. (I think it can use PyPy as runtime to set back the efficiency difference though...)
Now back to topic, AAK-Cont is not really maintained, but it is still better than the original AAK. Adding it to the filters list will probably not cause damage considering the original AAK is kept.
@TerrakionSmash It is, but so far it's only been me. It needs more devs.
@TerrakionSmash Not enough maintainers. Maybe not enough interest as everyone wants the best in the world. Also, many people uses AdBlock and Adblock Plus, so AAK-Cont will probably never work as expected.
@bershan2
As @gorhill said, Wasting is not using
That statement was specifically in response for those who tried to excuse ABP's inefficient use of CPU/memory, this is not a statement to be used as an argument without context in other unrelated discussions.
@gorhill Sorry for that, I just meant that UI does not need a lot to look nice (I'm currently adding in some SVGs with tooltips in place of text buttons). I'm not against animations, I'm against unnecessary use of powerful (and thus large) dependencies, responding to the comment right above mine. Also, I mentioned absence of :hover
as an extreme example of minimalist CSS (but that might be unintentional).
Replace "uBlock Protector List" (Chrome only) and "Anti-Adblock Killer | Reek" (obsolete) with "Anti-Adblock Killer Continued" ("Based on uBlock Protector (by jspenguin2017) and Anti-Adblock Killer (by Reek)") in uBlock Origin for Firefox.
I'm going to remove "uBlock Protector List" and add "Anti-Adblock Killer Continued", uBO shouldn't promote Chrome at the expense of Firefox. For those who have "uBlock Protector List" selected, the list will be moved to the "Custom" section.
It seems that reek's AAK repo has been discontinued/abandoned for over 7 months (reek/anti-adblock-killer#3272), some features don't work any longer. Fortunately, someone else forks and maintains this repo at GitLab.
I think you should consider to add this new filter to the "3rd-party filters" tab.