-
Notifications
You must be signed in to change notification settings - Fork 435
Stop accepting donations, or explain where the money are going to! #1706
Comments
Hey. If you don't wish to donate, don't. I've been immensely busy with an actual job and working on Purify. I'll be able to work more on uBlock in Q3 and Q4 of 2017. This is an open-source project. If you find something wrong with the software that you think the users would benefit from fixing, please create a pull request. Quit making this seem like a conspiracy. It is not. There's an FAQ on the website that explicitly differentiates uBlock from uBlock Origin. |
I am just as sorry about the name confusion as anyone. I am sure there are users who think they're donating to uBlock Origin — and some have asked for refunds of their donations based on that, in which case they've been given those refunds immediately. |
@chrisaljoudi thank you! I appreciate your reply. My only concern is that as long as you're not actively working on uBlock(even if you plan on doing so), it's morally wrong to take donations. If you don't want to do that, then at least perhaps make it immediately obvious that uBlock is not uBlock Origin. It's great news that you plan on resuming to work on uBlock and I hope that you'll be able to get the extension back up to speed. PS: If you don't stop taking donations now and you don't resume work by Q4, then please, please take the donation form down. We probably have different moral values, and that's ok - but taking the form down when you're not working on the extension will show people that you're really not trying to scam anyone. |
@nikolov-tmw I understand your concern. I honestly think it should be kept in mind that these are donations. Voluntary, unobtrusively accepted donations. The only two places where it is even mention are the README and the website homepage — never in the extension itself or even the Chrome Webstore/Mozilla Addons pages. uBlock has 800K+ daily active users across Safari, Chrome, and Firefox. I think many of them are happy users who wish to donate to show support for the project, orthogonally to uBlock Origin's existence and user-base. I don't expect donations any more than any user or visitor to ublock.org is obligated to give one. Does this thought process make any sense? |
@chrisaljoudi I see your point. And while I might not 100% agree with it, I really appreciate the conversation and that you shared your point of view. It's much better than not hearing anything at all from you :) My personal recommendation for you(in order to avoid people like me) would be to put this statement somewhere. Even if it's the FAQ section on the site. Perhaps the readme in this repository. Just somewhere saying what you said above. |
You changed 4 lines of code in the last 2 years. You should really consider adding a redirect to ublock origin to this repo, and removing the donation links. |
@chrisaljoudi can you please tell me how can I cancel my monthly donation? I'm trying to find a way but it seems that the only option will be to just report the charge to the credit card company as fraudulent. |
@chrisaljoudi - you silently closed #1659, #1689, #1690, #1692, #1694 and #1695. You are no longer pushing any code to this repository, or updates to the uBlock Chrome extension. You're also not pushing any commits to gorhill/uBlock.
According to ublock.org, you're still collecting donations. Unless there's something going on that is not explained, then this is completely dishonest and can be considered illegal(as it's pretty much a scam - you're asking people to donate to support development, but there's no such development).
You've had plenty of people call you out on this - it's time to accept the fact that you're not entitled for donations to something you no longer work on.
Here's some screenshot evidence(the pile will only get bigger the longer you refuse to respond):
Donations bar on 9-th of July 2017
Donations bar on 16-th of July 2017
Some deleted comments(I don't condone @Soret's comment, but see nothing wrong with @anewuser's):
Same, on GitHub's side in #1692:
The text was updated successfully, but these errors were encountered: