To understand how Stackoverflow can calculate points so accurately, I asked them: https://meta.stackoverflow.com/q/370194/1066234
They store votes and other point events per day. And they cannot be changed in the future!!
That means, the "points recalculation" of q2a is messing up all user points as soon as something has been changed (changed points, deleted posts, new upvotes etc.).
If we could track all point events per day, then I could improve the best-user-per-month plugin a lot, so intervals could be self-defined, i. e. weekly and daily!
This is how Stackoverflow stores/tracks the reputation points:
total votes: 787
2 9605154 (5)
-- 2012-03-07 rep +5 = 6
2 10531683 (5)
-- 2012-05-10 rep +5 = 11
1 11085525 (2)
-- 2012-06-18 rep +2 = 13
1 11178723 (2)
2 11178599 (5)
-- 2012-06-24 rep +7 = 20
2 11178599 (5)
-- 2012-07-21 rep +5 = 25
-- 2012-08-22 rep 0 = 25
-- 2012-08-26 rep 0 = 25
-- 2012-09-07 rep 0 = 25
1 12415046 (2)
1 12420385 (2)
-- 2012-09-14 rep +4 = 29
2 12412388 (5)
-- 2012-09-15 rep +5 = 34
...
Check your own (if you are member there): https://stackoverflow.com/reputation
I also see that with Q2A you can get points for posting, but not at Stackoverflow.
For Q2A we need to get those basic point events with the specific day they happened:
- Q/A posted (in table qa_posts, field created)
- Upvote/Downvote for Q/A (in table qa_uservotes, field votecreated or voteupdated)
- Select Best answer (in ? qa_eventlog ?)
- Answer as best selected (in ? qa_eventlog ?)
Problem: The select events are to be found in /db/points.php with function qa_db_points_update_ifuser($userid, $columns) which does not save the single data but only updates the count in qa_userpoints.
Anyone?
- - - -
I now understand how Stackoverflow is doing it:
"Any deductions aren't made retrospectively" – ... if posts from the past are deleted, they are not changed in the past, but instead will trigger minuspoints for the current day!
