-
-
Notifications
You must be signed in to change notification settings - Fork 775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display Tips on Leaderboard #522
Labels
Comments
@tra38 a big 👍 from me on this idea, I think including tips better shows the whole picture |
This is a really really good idea.. I wonder if its appropriate to display who the tip was from or not and for how much.. Is there an expectation of privacy associated with tipping? |
I think it would be best to have it be opt-in for both tipper and tippee |
how dis? #544 |
this is done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that the leaderboard/profile part of the site only displays "bounties" that individuals fulfilled. For example, my profile shows that I worked on a single bounty.
However, tips have been used frequently on gitcoin.co as well, for many reasons, such as:
Displaying both bounties and tips will help give users a better idea of the "reputation" of the individual - if you know how many tips a person has received/given and how many bounties a person created/fulfilled, then you have more data points that will help you better understand the person. In some ways, it would be an improvement on my original proposal for "reputation" where I proposed keeping track of fulfilled bounties.
I am not sure how the leaderboard calculate monetary stats by the way. At the time of posting, the leaderboard said that I made $112.28, but the only bounty that I worked on according to my profile was for 0.07 ETH ($59.32). So it might be possible that some additional data may already be collected, and it may be only a matter of showing this additional data to the user when they view the profile.
The text was updated successfully, but these errors were encountered: