Repository navigation
Allow developers to opt out of being tipped #154
Description
Activity
they can - in fact that is the default - commits only receive tip offers - one must opt-in to receive the tips
there has been much discussion lately regarding the site poilicies and a draft of a "how it works" page is being created now https://github.com/tip4commit/tip4commit/wiki/about-page-draft
Offering opt-out should be a stopgap measure to accommodate the entirely reasonable requests you're receiving, until such time as the correct policy is adopted. The correct and only acceptable permanent policy is no unsolicited contact, no unsolicited tip offers, and no solicitation on behalf of an individual developer unless/until that individual developer has explicitly opted in. Anything else is asking for further massive headaches, as unsolicited contact of developers based on harvesting information from GitHub would appear to clearly violate GitHub's terms of service, and may also violate local laws in force where the developers live.
Getting tipped via tip4commit was a very confusing experience for me, and the amount of the tip was low enough that I quickly decided the service provided no value to me. If this is not made into an opt-in service, I don't think it will be around for very long based on what I'm seeing from both sides. There seems to be a pessimistic view on how opt-in would affect the quality of the service, but it would make it more appealing to me. If I know that a project I'm contributing to intends to use it, it feels more legitimate and worth opting into. So +1 for opt-in on my end, but this is also very much related to #155 for me
also opt-in feature request is #152
+1
@nnjpp thanks for your feedback, we introduced a minimal notification thershold over a month ago... so no more notifications about micro-tips
Raised the notification threshold to 21000000 btc (that will never exist), nobody should receive any notifications from us until we find an appropriate solution.
@ubernostrum when you are talking about opt out, do you mean email notifications (that are now temporary disabled as a whole) or do you mean that we can't publish already public information about project developers and show tips that they can collect?
When I talk about opt out I talk about it as a temporary thing before you transition to explicit opt-in.
I have outlined clearly in #146 what I want for myself individually based on the fact that you "opted" me in without my wanting you to.
you mentioned in #157 that this feature should be implemented ASAP but doesn't this functionality already exist?
there is a link in the existing invitation email to opt out - this was copied over to the draft - does it not work yet?
https://github.com/tip4commit/tip4commit/wiki/email-invitation-draft%p %small = link_to "Don't notify me anymore, I don't need tips.", login_users_url(token: @user.login_token, unsubscribe: true)When I say "opt out", I do not mean "have tip4commit pretend it no longer claims to accept donations for me by having it avoid emailing me" or anything of that nature.
I mean that I want to really, actually, really for real, for real actually, really actually FOR REAL be scrubbed out of the system completely, since I never opted into it, never consented to it, never agreed to it, never should have been opted into it, and want nothing more than to return to my life as it was before tip4commit decided to "help" me. And I do not -- again do not -- mean "hide the information but keep it around." Purge the rows from the databases which contain information harvested about me in violation of GitHub's terms of service. Purge the records of attempts to give me "tips". Make it as if tip4commit had not invaded my life in the first place. If you've done your jobs well it should be a few simple
DELETEqueries.Now. Stop arguing. Stop stonewalling. Stop making me regret the decision to be charitable and give time to make things right. From this point on, any comment from the most freuqently-seen-in-these-threads tip4commit defenders/project members -- at the very least, @arsenische and @bill-auger -- which I deem to be improbably obtuse or stonewalling will result in a reduction of my ability to trust that tip4commit is acting in good faith, and thus in a reduction of the grace period of #146 by ten (10) days. If that period expires or is reduced to nonexistence without satisfactory action by tip4commit, I will as noted in that issue begin engaging with entities external to tip4commit to seek enforcement of first all applicable policies of all services engaged by tip4commit and then, if that fails, investigate the possibility of enforcement of law against tip4commit should that appear to be necessary to resolve the issue. I sincerely hope this does not become necessary, but in previous interactions with tip4commit in a project capacity, I have seen it be the case that only threats of outside enforcement which would hamper or end tip4commit's operations sufficed to provoke remedial action from tip4commit. Please learn from that experience and do the right thing this time around.
Ditto.