| … | |
… | |
| 9 | - trivial: remember the time of the last move for restarting the timer |
9 | - trivial: remember the time of the last move for restarting the timer |
| 10 | |
10 | |
| 11 | - or is it a flag(?): |
11 | - or is it a flag(?): |
| 12 | lavalyn: "~" is what you get if you have played 5 more than twice the number of games you've played against "?" "-" or "not stronger" players |
12 | lavalyn: "~" is what you get if you have played 5 more than twice the number of games you've played against "?" "-" or "not stronger" players |
| 13 | |
13 | |
|
|
14 | - some user'ess prefers the ggo board. well... |
|
|
15 | |
|
|
16 | - seperate goboard etc. from the rest. |
|
|
17 | |
| 14 | VIEWER: |
18 | VIEWER: |
| 15 | |
19 | |
| 16 | - various off-by-one (or off-by-half) errors ("edgy" stones) |
20 | - labels, resize bg colour |
|
|
21 | - board colour => traditional yellowish kaya |
| 17 | |
22 | |
| 18 | BUGS: (send to wms if time is right) |
23 | BUGS (should report to wms, but since he started a war, maybe we should try to |
|
|
24 | avoid attention). |
| 19 | |
25 | |
| 20 | - Room Chats don't check username. |
26 | - one can get random memory dumps from the server (passwords if you try long enough? :) |
| 21 | - game channel messages for games in challenge are not healthy to the server it seems. |
27 | (UPDATE: indeed, the server leaks passwords, unfortunately the associated usernames |
| 22 | - leaving a game (probably a room, with channel id 0 (at least)) instantly crashes the server |
28 | are not near, still troubling...) |
| 23 | - sending userpic requests with ivalid username ("zerokun [0k]") also crashes(?) |
29 | - it seems the client is extremely easy to crash... |
| 24 | |
|
|
| 25 | |
|
|
