A tesuji problem: how can white break into the left side?

Click Here To Show Diagram Code

[go]$$B
$$ +---------------------------------------+
$$ | . . . X X O . . . . . . . . . . . . . |
$$ | . . X X O O . . . . . . . . O X . . . |
$$ | . . X O O X . O O O O X X O O X . . . |
$$ | . . X O . . O X X X X O O O . X X X . |
$$ | . . . O . . . . . . O X X O X . O O . |
$$ | . . X O . . . . . . X . X X O . . . . |
$$ | . . X O . O . . X . X X O . O . . . . |
$$ | . . . . . X O . O O O O O . O . . . . |
$$ | . . X O O X . . O X X X X X O . O . . |
$$ | . . . O . X . O . , . . . X X , . . . |
$$ | . 1 O . . . . . O X . X O . . X X . . |
$$ | . . X O . X X O X . . X O O O O . . . |
$$ | . . X O O . . O X X . . O X X . O O . |
$$ | . . . X . X X O O X X . . O X . . X . |
$$ | . . . X . X O O X X O O . O X X X X . |
$$ | . . X , . . O X X O . . . . . , O O . |
$$ | . . X O . O . X O O . O O X X X O . . |
$$ | X X O O . . . . . . . . X O O O X X . |
$$ | . O . . . . . . . . . . . . . . . . . |
$$ +---------------------------------------+[/go]

Answer is in this pro game: http://www.go4go.net/go/games/sgfview/42420

Since I don't have an account for that site I'll just post my sketchy Sunday morning reading.

This one breaks into the side, but the white group gets cut off and dies so I don't think that counts as a solution

I second leichtloeslich's solution

_________________
David

Go Game Guru: Learn Go | How to Get Better at Go | Go Game Shop | Go Boards | Baduk TV

Well done! guys.

Uberdude's solution shows the most natual thinking process, although he proved that's not working. By saving one exchange from that sequence, magic happens.

BTW, sorry for those of you who don't have an account at Go4Go. It's really easy to create one. The site was recently targeted by somebody (apparently a Go player) who insisted he having the right to mass downloading everything. His technical skill was akin to a hacker because he somehow used a large range of distributed IPs to target my site. Protecting the game pages by login is by far the easiest defense.

It should be possible to separate viewing permissions from downloading permissions. Right now it's not possible to even replay (view) a game without creating an account or logging in.

That sounds logical and I agree that not even being able to view a game without logging in is very unfortunate. The problem is that there's fundamentally no difference between viewing a game and downloading the data. Whoever is doing this would then just download all the games anyway, by using a script to 'view' them and extract the data they're interested in.

Normally you might solve this by throttling the rate of requests per IP address (which Mace has probably tried already). It sounds to me like someone is accessing go4go using TOR (which is abusing TOR as well as Mace's server, really) and blocking TOR exit nodes is something that some sites do to deal with this sort of thing.

At GGG, we just gave up participating in the arms race (except against those damn spammers!), because we didn't have time for it and 'winning' it eventually involves inconveniencing normal readers in some way (as you've just seen). Requiring users to login is another reasonable compromise once you realize the full context of the problem. Anyway, it's a difficult problem for the person running the website

EDIT: Actually Mace, if you're using PHP, this might help: http://bad-behavior.ioerror.us/

_________________
David

Go Game Guru: Learn Go | How to Get Better at Go | Go Game Shop | Go Boards | Baduk TV

Thanks David for giving a very accurate description of the problem I am facing. No matter what technique is used to present the games, if a game is viewable online, so is the data behind it. It is just a matter of time for the data to be decoded.

I will look into the bad-behavior package. The idea behind it sounds great because it not only stops spam but also saves bandwidth, which is in practice often the biggest issue.

Thank-you for the explanation David, I'm sorry for my ignorance regarding these issues. I wish I was an expert at these things so I could help you with them, macelee.

If memory serves, this is very same problem that made gobase start to require logins (even if they were free ones) several years ago...seems like some things never change )=