Sneak Peek

[Harleqin]

It seems that one cannot go back now, no matter what: not back '<', nor beginning '<<', nor reload work.

[daniel_the_smith]

Doh, I fixed that but I guess I didn't restart it. In a car driving to congress right now so I'm not sure when I'll have a chance to log in and fix it. Sorry, guys!!

[Nikolas73]

Wow, this is an amazing idea! Very impressive! I can't wait until it's finished, then I might actually learn more than just a few joseki .

Good luck and of course let us know if you need any help.

[Bantari]

Announcing: dailyjoseki.com!
Where do I get the list of joseki: They are automatically extracted from professional games (specifically, the 60,000+ games of GoGoD). This allows me to be pretty confident I won't be teaching people something stupid from Kogo's.

I am not sure if it is safe to assume that pro moves in the corner are always joseki.
Its good you also try to provide a approximate averaged board position at each move. That's the really innovative feature I like.
All in all, a pretty cool site.

Here is something I wrote about 'Studying Joseki', just to support your point and do some self-promotion.
http://www.bantari.net/go/thoughts/page-001.php

[daniel_the_smith]

Ok, fixed. Night night.

[SpongeBob]

This is a bit Off-Topic, but could you give your opinion about the new 'Go' programming language? I heard lots of positive things and it would be interesting to hear how it feels from someone who is actually using it.

[daniel_the_smith]

It needs genetics, but other than that, I love it. (EDIT: months later: holy crap, of course that should read "generics" and not "genetics"...)

(My opponent for the us open was a no-show, so I'm taking game results for the TD and checking the forum...)

[unkx80]

I finally played around a bit on your website. Very nicely done.

Currently each click takes around a second to respond. A bit slow but acceptable, given the long distances.

At first I found it slightly confusing when a position is reached by X times, but clicking on a point results in another position being reached Y times, with Y > X. I guess that's because there are multiple paths to the same position.

[daniel_the_smith]

At first I found it slightly confusing when a position is reached by X times, but clicking on a point results in another position being reached Y times, with Y > X. I guess that's because there are multiple paths to the same position.

Yes, exactly. Many positions can be reached multiple ways.

[Li Kao]

Will you add support for fuseki too? It shouldn't be hard to code that.

[CarlJung]

In case Daniel doesn't add fuseki, see my sig for a free opening library.

[Dusk Eagle]

Daniel, when I play through to this position, it says that the position has been reached three times, but the total below has a sum of four. What's going on?

Edit: This position is also messed up.

[Li Kao]

Daniel, when I play through to this position, it says that the position has been reached three times, but the total below has a sum of four. What's going on?

Edit: This position is also messed up.

All games were tenukied at first. Once it was continued by the player who was to, and twice by the other.

[daniel_the_smith]

Yeah, hit "pass" to see the rest of the plays made (by the other side). I had some bugs where those counts did not agree, but I think I've fixed all of them.

That said, there *is* a bug with the way I keep track of the tenukis, I don't take into consideration *who* is making the tenuki, I just lump them all together. So, the tenuki count might be completely wrong at times.

[Psychee]

How do you tenuki a move? When it says 70% of the time black tenukis, is there a way to see the continuation of the corner later on?