- There is no "average"ing of the previous day's save list as yet, and I'm thinking about it (I can think of reasons for and against this option);
It's not, er, wasn't, an average. It was an intersection. The idea was, if burper and don started and completed a match "today", "tonight's" fibs.com/savedgames would list it. The only reason the match was "persisted", was to support the oldmoves command. If tomorrow nights' savedgames was intersected with it however, the result would not show it.
There are several complicating factors (see below) that might cause you to argue that performing this intersection starts you down the slippery slope, losing objectivity as you go, that I understand. Perhaps there is a way to address that by making this optional, or by providing both metrics, e.g.
mudPY says: [playBunny] Rating: 1796.30 Experience: 814 Saved: 13 (possibly completed today: 4)
Even simpler, why not resurrect the RepBot, with the complain and ask functions removed? It should be a trivial change.
No complaining means everyone gets a positive rep, and using friends rather than ask (may be better to route the ask command to the friends command) means there would be no motivation to create duplicate accounts to pump up your rep. This would be best if the existing RepBot database, with all complaints removed, could be used to seed things.
*Those complicating factors I mentioned above:
- -if don and I played (to completion) 2 matches on consecutive days, the intersection would not remove the match from the savedgames list.
- -"today", "tonight", etc... are all used very loosely. It all depends on what the first character of the filename is of your saved game. That is the lexicographically first (case sensitive, and including _) of the two names involved in the match, e.g. for don and burper, it would be "b". I don't have my notes in front of me at the moment, but you can tell when the match will be removed by watching the output of the 'stat' command.
- -It also depends on when the savedgames web file is compiled, posted, and when you retrieve it. Judgin from some of the inconsistencies I've seen in the data, I believe Pattis' script compiles the page "live", rather than taking a locked snapshot. There may be no choice without interrupting fibs, and the result is "close enough", but there is the first slip down that slope mentioned above.
Perhaps Patti could confirm item 2 from the list above.
There are some other objective facts that could be derived from archiving the list of savegames over a period of time, such as a count (or rate) of saved games that were removed because they became too old (how many days is it?). If the match was there "yesterday", and its' not "today", and you know for sure at least one of the players were not logged in during that magic period of time, then bump the counter by 1. Its' an objective bit of data, leave the interpretation up to the user.
Even better, you should be able to count the number of times vegasvic and souptree play each other to completion (savedgames between them show up one day, gone the next, there again another day, gone the next, etc...). Leave the interpretation to the user, but if I didn't know souptree, but noted that many of the people I had marked as friends in my client had played multiple matches with him, I might feel more comfortable about accepting an invitation.
I'm glad you are attacking the issue don, there's hope for you yet!