You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.
That shows the percentage of users who were in fact active for the given number of weeks, out of those who could possibly have been active for the given number of weeks.
Although our common terminology for active users refers to those who either receive or give tips in a week, I don't think that it's the best criteria to consider for a retention chart. Since we're just taking tips, someone who created an account long ago and has been receiving $0.01 every week would be considered an active user throughout the 122 weeks.
I think a better way to look at activeness would be - people who have done either one of the following within the previous month/week/whatever-time-period-we're-using
People who have set a tip up to someone else, or changed an existing tip
People who have received new tips or whose tips have been changed (the people on the other side of point 1
People who have changed their takes in a team.
There are people who would fall through the cracks on this one, but I think they'd be far less than the number of non-active users we're counting in the current method. Here's a list of people I can think of who should be, but won't be included in this chart.
People who maintain a constant take from the team(s) they're a part of, and don't experience a change in receiving/giving often.
People who only give a significant amount of money, and don't change it often. Could be organizational givers, for example.
Splitting out from #89 (comment).
That shows the percentage of users who were in fact active for the given number of weeks, out of those who could possibly have been active for the given number of weeks.
Context is https://www.youtube.com/watch?v=n_yHZ_vKjno.
IRC
retention.py
The text was updated successfully, but these errors were encountered: