Because the uBlock "Origin" UI sucks compared to ABP.
Because acceptable ads is easy to turn off with one click.
And because gorhill is a real asshole when you submit an issue. It's now obvious to me why uBlock had all sorts of drama at launch.
The "seeing more ads" part can just be the result of having fewer users.
I think it's possibly just a case of someone unhappy for whom I declined[1] to take care of their pet issue, so lashing out with vague supposed flaws so as to undermine my work makes him feel better.
1. https://github.com/gorhill/uBlock/issues?q=label%3Adeclined+...
That's funny. Because the reason I said it was that you close issues without pointing out WHAT item in your huge list of ridiculous guidelines (like "I don't accept pull requests") has been broken. LOL.
It's a real asshole move and if anyone actually reads the list of declined issues they can clearly see that people are annoyed by that.
Given the amount of invalid issues that keep being opened[1], asking me to spend time to detail why issues marked as "invalid" are invalid is to ask me to spend a whole lot of precious free time on not working to improve uBO.
CONTRIBUTING[2] is there to be read and respected. If you disagree with it, best is to not open issues. Countless other people understand why it is needed and respect it, and helps the project get better.
1. https://github.com/gorhill/uBlock/issues?q=label%3Ainvalid+i...
2. https://github.com/gorhill/uBlock/blob/master/CONTRIBUTING.m...
Furthermore, since the person closing the issue is already quite obviously aware of which rule was broken - how much effort are we haggling over? A couple seconds?
Anyway, as I've said it's clear from reading many of the declined issues that people are annoyed by your behavior. It's also clear that you are annoyed by your users, so I wouldn't say that you "happily" volunteer.
In most open source projects, contributing refers to contributing code not opening tickets for issues or requests. Even Github's help documents align with this understanding:
https://github.com/blog/1184-contributing-guidelines
I have never used uBlock or looked at its project pages before now and would have skipped-past CONTRIBUTING.md if I was looking for issue-reporting guidelines. The current title doesn't even tally with the first line of the document. There is also no reference to the appropriate issue-reporting process from README.md.
> Read first: <https://github.com/gorhill/uBlock/blob/master/CONTRIBUTING.m...
And thanks for maintaining uBO. Using it happily since it became a topic on HN.
[1] https://github.com/gorhill/uBlock/issues/1886#issuecomment-2...
It's those that provide the blocking logic, and which need to be updated to fix this.
1. https://github.com/gorhill/uBlock/wiki/Static-filter-syntax