4 ms·
And the first thing the guy who took over the original uBlock did was ask for donations, for code that was mostly written by someone else. Better use uBlock Or
by yAnonymous 11y ago
And the first thing the guy who took over the original uBlock did was ask for donations, for code that was mostly written by someone else.
Better use uBlock Origin, which is developed by the original uBlock author.
https://github.com/gorhill/uBlock https://github.com/gorhill/uBlock
- cpeterso 11y agoThe maintainer of uBlock Origin needs to do a much better job of explaining the difference between uBlock and uBlock Origin. The extensions' descriptions on addons.mozilla.org are word-for-word identical: https://addons.mozilla.org/en-US/firefox/addon/ublock https://addons.mozilla.org/en-US/firefox/addon/ublock https://addons.mozilla.org/en-US/firefox/addon/ublock-origin https://addons.mozilla.org/en-US/firefox/addon/ublock-origin
- jd3 11y agohe already did... https://github.com/gorhill/uBlock/wiki/uBlock-vs.-uBlock-Origin%3A-Facts https://github.com/gorhill/uBlock/wiki/uBlock-vs.-uBlock-Ori...
- cpeterso 11y agoInteresting. He still hasn't answered why a user should pick one or the other. If he wanted to focus on refactoring and larger features, he could have enlisted a "lieutenant" to manage bug fixes and releases while he works in a dev branch. The uBlock "brand" had quickly become the "new, memory-efficient ad blocker", but now the brand has been divided and muddied. This seems like a good example of the problems with 'product line extension', where a new extension should have used a new name. https://en.wikipedia.org/wiki/Product_line_extension https://en.wikipedia.org/wiki/Product_line_extension
- jd3 11y agoI don't understand why he doesn't just re-po the repo (ha) from the guy he gave it to. it would solve the strange monetization problem and fix the schism the two projects have created for end users.