implement a reputation system

[chadwhitacre]

Right now we have a binary (well, trinary) is_suspicious field to track reputation. We should evolve something more granular. Users should be able to unlock features by earning reputation. I feel like we've talked about this before but I don't know that we have a ticket dedicated to the idea.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[chadwhitacre]

Example from Mandrill:

[chadwhitacre]

I thought Coinbase had a good implementation of this under "Verifications" or something, but I'm not finding it right now.

[colindean]

Maybe reputation is a function of how many weeks a user has successfully participated, weighted by booleans of giving and receiving? Perhaps also figure in consecutive charges, etc.

[chadwhitacre]

@colindean Yes. Also::

• verified email
• 2fa
• received from reputable user
• identity document (verify individual identity programmatically #2449)
• social accounts with long history

[blrhc]

This is a good idea! +1

[techtonik]

I don't like systems like Facebook, which require too much personal info from me just to become a normal citizen. What is your goal for the reputation system?

Reputation thing is too broad. It is better start with features to unlock.

[webmaven]

This might be helpful (either the book or the wiki):
http://buildingreputation.com/doku.php

[chadwhitacre]

For hard-suspending a user, we should evolve the existing is_suspicious knob into is_suspended (#3058).

[webmaven]

Is hard-suspending the equivalent of being banned from the service?

Assuming an owner gets banned, is the team banned as well, or is there opportunity for the team to be transferred to another owner?

If a team is banned, the members are not, correct (as they may be or become members of other teams)?

What will the processes (or lifecycle, if you will) look like for individuals joining/leaving teams?

Do we watch if teams have a high proportion of their members suspended or banned over time?