I've heard various ideas such as limiting it only after mods have expended their points (this will require implementing a cooldown to prevent a user from getting points again too soon). I want to hear your feedback, and I'll roll together something for the next major update of the site. Leave your comments
Points are awarded only to users who are currently logged in, and work in a LIFO system, so if you haven't gotten mod points in awhile, then log in, you'll get them within five minutes if you meet all other critera (currently positive karma, 80% of oldest accounts)
OK, that's fine.P.S. Sorry for using the A-word in the subject line - bit of a brainfart there.
Thanks for the clarification.
I still think 8 hours are too little, unless we have a really good reason to make them expire that quickly.
My use case may or may not be typical, but I typically check SN in the morning before I go to work, read a few stories, then go to work. After work, I have time to check in again (and maybe read/moderate stories that I only glanced at earlier or that are new). I've more than once been awarded mod points in the AM, then when I went back in the afternoon with time to use them have found they've already expired.
I'd really like to see ~16 hours, personally. YMMV.
When the site first launched, the value was set at 24 hours. The problem was that we got stuck with people hoarding points, and the new algo needs points going in/out (it tries to maintain X points at all times, so its dependent on rapid expiration, or people using points). Dropping it down to 4 was an emergency fix until I could get around to revising the mod algo.
Unfortunately, when I wrote it, I had no hard numbers to work again, and its working on some faulty assumptions. I keep putting rewrite on the list, but its not SUPER high priority.
The system considers you active if you've clicked within five minutes; a timestamp in the backend is updated with every page refresh. As for accounts, its basically max_uid*0.8 for eligibility.
so you're penalising 20% of your users for no apparent reason, good job sonny...
This is true on the other site as well; this variable is the default in Slash. We've set it so there's a slight delay from when a user first signs up, and then gets handed modpoints.
I had a hole which pre-existed for the moderation algorthim, and at the time, very little idea how slash works. This code was written three days into the slashcott during madness. I've jotted this down for v2 of the algorthim, but until now, this is a stopgap until I can sit down, rework the math, and get it better.
+1 if I could :D
I think the main problem is that the selection for mod points is asynchronous (if I understand it right). That is, the user accesses the site, and gets no mod points yet. Then, while the user is reading, he gets mod points, but doesn't see them because he doesn't reload the site (there's no need to do so, because he's still busy reading the current version). He may even then quit reading for now. Then, at a later time, he again accesses SN, and gets a message that he has mod points. But they are to expire soon (because all the time they were sitting there without him knowing anything about that).
I think the right thing to do is to only tentatively give mod points in the asynchronous process, but really activate them only the next time he loads a page (so at that time — the first time he can learn about them — he gets the full period).