All the games in the database are complete: that is they have been played out to the bitter end. Most games captured from actual play are incomplete, and I arrange for a completion (which may or may not be correct) before the games are included in the database.
I recently started logging all additions, and many other manipulations to the database. This helps you find out if your most recent contribution has been added, and gives you game numbers to track. You can find a copy of the log here, or you can email me to request a more recent one.
The database can only choose among the moves that are on file. There may be (and very often are) better moves that are not shown because the database does not (yet) know about them.
Win and Loss:
The database marks a move as a win or a loss depending on the outcomes that are on file, assuming that each player makes the best choice among the available moves at each turn.
There are surely errors in the database, because not all moves have been tried and reported here. A losing move may be incorrectly marked as a winning move if all the games in which it appears include mistakes by the opponent. Likewise, a winning move may be incorrectly marked as a losing move if all the games in which it appears include later mistakes by the same player.
As the database can only display the moves that it knows about, the best way for you to correct an error in the sequence is to send me a game that incorporates a better move. Here's how.
The machine has dual XEON CPU's.
The OS is Gentoo Linux, with kernel 2.6.
The web server is Apache 2.
The database is GNU GDBM. Test versions with a home-made database are in development.
The programs are written in Python. They are being converted to C++.
I'm not ever going to have all the possible games. That's not even feasible with forseeable technology. Here's why.