jurek: Will he do this to all of the other hundreds of games that were improperly scored, too?
If I were him, I'd say no :)
I think that unless he's asked to change a specific game result all the results will be kept as they are now. It's very tough for a computer to determine the correct score in many games; that's why the players need to mark dead stones and let the computer determine the score from there. If the stones are incorrectly marked dead, the score is incorrectly calculated.

Binabik: it shouldn't be possible for this to happen, am I right?
Well ... you accepted the score.
If you had declined the dead stones the game would go on ... your opponent could mark the stones differently on the next move ... or maybe she'd mark them the same and you decline again ... and again ... and again ... and again :)
The end of game needs to be reviewed by Fencer. There have been quite a few threads about that already.

Binabik: Send a message to Fencer and he'll make it right (once he returns from vacation).

joshi tm: Yes, he can go directly to the database and set the game finished with a specific winner (if I'm right Black wins by 1.5 points -- that would terminate the tournament and give you 2nd place).

I'm sure he reads this board, but send him a message.

joshi tm: Maybe you can *bump* one of these threads of the "Feature Request" board :)

emmett: As far as I know, using a komi ("handicaps") is standard, though the values vary.

Sensei's Library has a lot to read about komi among many other Go related articles.

kaluza: So I see. Sorry Fencer (but it serves as a reminder ).

kaluza: You're right. The score is wrongly calculated by the server.

I reported it as bug in the Bug tracker.

volant: and a player should pass when every move he/she makes decreases his/her score.

gringo: The game seems to have been tweaked (by Fencer?). Even though it shows Black with 7 points and White with 9.5 points, the winner is Black; which is correct.

Black wins by 11.5 points.

Chaosu: Try changing the text size in your browser. Open the View / Text Size menu and choose different sizes until, hopefully, it looks right.

fakarten: The SGF viewer/editor I like best is Kiseido's. Unfortunately, unlike MultiGo, it doesn't rotate or mirror the board (at least not my old version 2.6.12).

Fencer: I wrote a script to transform the move list into an SGF file. It needs a few twists, but as I don't use it often, I haven't twisted it. You can see the PHP source or use it to convert any public game to SGF by going to http://hexkid.info/BK/ParseGame.php?g=##### where ##### is the game number.

I've also integrated this functionality into BrainKing itself with the help of a Greasemonkey script, accessible at the user scripting fellowship :)

Salkkuman: Moderating this board doesn't look like a lot of work :)
I'll happily co-mod it with you.

Groucho: All white stones on the board are alive and should not be marked dead at game end.

The final score for that game (as BrainKing calculates it and if I didn't make a mistake) should be:
Black: 0 (territory) - 68 (prisoners) - 3.5 (komi) = -71.5 points
White: 18 (territory) - 2 (prisoners) = 16 points

headius: Go boards can be enlarged from the small size to a larger size :)

My solution works simply by setting the image height and width to 25; to use it you need Firefox and GreaseMonkey; you'll also need the Greasemonkey script and possibly to change the value to something you're confortable with (instead of the 25).

onigoroshi: I took the liberty to create an SGF file (which you can download) out of that game of yours.

jurek: One of the games posted by Marfitalu could proceed to this position. Black has just (wrongly) marked all White stones dead and will have to play a stone on her next turn ...

Even if Black insist on playing on, at some point in time White advantage due to captured stones will be big enough to accept the wrongly marked dead stones :)

Salkkuman: The player who (wrongly) marked dead stones is the one who has pass disabled, not the other way around.
Think of it as
player 1: I say these stones are dead
player 2: I don't agree, prove it.
player 1: ok, I play here (and lose 1 point)
player 2: Ah! you're right (but you're now losing by 0.5 points) ... pass
player 1: pass
player 2: mark dead stones correctly
player 1: decline
player 2: (Rats! she didn't fall for it) ... resign

volant: This problem could be solved, if playing a stone was mandatory after a decline of dead stones. A game could then go like this:

137 ...  pass
138 pass D
139 -    h7 (no pass!)
140 pass pass
141 D    -
142 h9   pass
143 pass ...

This, at least, avoids repetition of the same position for every dead stone marking phase and gives a chance for both players to mark stones dead.

The referees thing would be nice too ... I volunteer

volant: Yes ... well, no ...

There is nothing wrong with the picture.
What is wrong is the marked dead stones. After they were marked the way they were marked, the server calculated the score correctly :)

In the game there should be no dead stone marked. All stones on the board are alive.

You should decline the score and maybe tell your opponent to not mark your stones dead.

headius: I think making komi a user-selectable value would be nice. Instead of getting handicap stones I could play a game with komi set to, for example, -83.5 :)

Flummoxed: Many people here have had their fist contact with Go a few weeks ago when Fencer introduced the game on BrainKing. As you win even with all stones marked dead, I'd try pointing to your opponent that no stones are dead in that game (even if you have to offer him F6), and then accept the correct score of "White wins". It is my understanding that winning by 30 points is exactly the same thing as winning by 0.5 point as far as the BKR and statistics go.

Salkkuman: As with so many things in Go, the Sensei's page about Komi is inconclusive

Salkkuman: Currently on BrainKing, komi is 5.5 for a 19x19 board, 4.5 for a 13x13 board and 3.5 for a 9x9 board.

At the current playing level of most of the people (me included, rating notwithstanding) maybe a komi of 0 (zero) would be nice :)

Sensei´s Library is a very nice site (wiki-style) with lots of information for beginners and advanced players.

Have a look at False Eye for an example that looks like it has two eyes, but (as it doesn't) can be killed.