-
Notifications
You must be signed in to change notification settings - Fork 4
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
Reputation Point Rules + App Features #6
Comments
Great job, went through everything and really sorry I didn't manage to join in before, but I still have my dad here and we're still fixing our flat (which was completely empty when we came). Ok, to the point now. Things that are blurry in my head and can't be put into anything concrete yet:
Creation rate
Redistribution
Ok, I will update this later, but just to put first thoughts out finally :) |
Added to SPECIFICATION/README.md in upcoming pull request -> please discuss it there. UPDATE: |
Summary from #1
Work in Progress - please comment
Reputation Points Journal [RPJ]
https://github.com/wizardamigosinstitute/RepPointsServer/blob/master/data/dis_snapshot.json
Reputation Point Rules [RP]
The
RP
work a bit like shares in a company.https://github.com/wizardamigosinstitute/RepPointsServer/blob/master/data/rules.json
Point Creation Rate [CR]
We need a way to create new shares and a
CR
is one way of creating new shares. ACR
is voted on by all users and determined choosing the median. It "waters down" the value of all points currently held by users, but allows for a "higher resolution" (more fine grained control) when transfering points to others. The change in ownership is calculated by dividing ones own points through the total amount of points which currently exist.Point Redistribution Rate [RR]
Everyone respecting
RP
's of others is a service everyone offers and should be paid. APoint Redistribution Rate
is setting the service price and is voted on by all users and determined choosing the median. The change in ownership is directly visible through the points people currently hold.The text was updated successfully, but these errors were encountered: