Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

For those one-offs where I have interacted with the person directly, I would equate this very closely to the barista model, and expect to be able to give them a single-instance tip that doesn't recur.

I mentioned this before (I think, or somebody did) and Whit's response was that he wanted to be able to shore up the 'regularity' of the revenue stream, but I think that does the whole service an injustice.

I am likely to tip small amounts that recur, and larger amounts for, pardon the analogy, 'good service' or for someone who went out of their way to help me, or did something awesome. I might tip a $1 a week to the Apache Foundation, for example, and/or $10 to the guy who helped me figure out why Apache kept crashing.

As for the 'regularity' of the income, I see no reason why you couldn't just represent the values separately on admin panel... "You are 'earning' $200 a week on GitTip, and also got $50 extra in your tip jar this week."

Add to that the ability to integrate a 'tip jar' into websites, Trac, FogBugz, Github issues or anywhere people interact with other people who help them, and you've got a more rounded system (IMHO).



> I see no reason why you couldn't just represent the values separately on admin panel... "You are 'earning' $200 a week on GitTip, and also got $50 extra in your tip jar this week."

Right, this is how we would do it. I've reopened this ticket:

https://github.com/whit537/www.gittip.com/issues/5




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: