Live data from Hacker News

Chess CAPTCHA

en.lichess.org

101–110 of 171 posts

Re: Chess CAPTCHA

#102
Considering that modern chess software can defeat grandmasters, the Chess CAPTCHA seems more designed to admit bots instead of humans.

"It was my luck (perhaps my bad luck) to be the world chess champion during the critical years in which computers challenged, then surpassed, human chess players"

From Garry Karparov: http://www.nybooks.com/articles/archives/2010/feb/11/the-che...

Re: Chess CAPTCHA

#103
post #43

Brilliant building of software. Less than brilliant copy. I would change Black plays; checkmate in one! This is a chess CAPTCHA. Click on the board to make your move, and prove you are human. to This is a chess CAPTCHA... To prove that you are human, click on a black piece, then click on the only destination square that will checkmate. I really don't mean to nitpick, but took me a minute to figure out what to do. Som…

No need. Given the demographic targeted, the current text is sufficient (possibly overly wordy at that) and regards the question of how to move, they are used to interfaces far worse than this---they will figure it out. I suppose that you could claim that as part of the puzzle :)

I disagree. Use the clearer set of instructions. Do not leave confusing instructions in place just because the target demographic can decipher them while others are left in confusion.

Re: Chess CAPTCHA

#104
post #90
post #83

Earlier quoted context omitted.

Or how about: A CAPTCHA appears before you, in form of a chessboard to prove, that you're a real user, and not a computer, by checkmating WHITE in one move.

I would change "a real user" with "a real user who doesn’t use a screen-reader". That’s less funny, but more accurate.

Out of curiosity: are there any known blind chess players? I guess it would be quite hardcore.

Re: Chess CAPTCHA

#105
post #104
post #90

Earlier quoted context omitted.

I would change "a real user" with "a real user who doesn’t use a screen-reader". That’s less funny, but more accurate.

Out of curiosity: are there any known blind chess players? I guess it would be quite hardcore.

Not sure about blind, but blindfold chess is a thing: http://en.wikipedia.org/wiki/Blindfold_chess

Re: Chess CAPTCHA

#106

Earlier quoted context omitted.

No need. Given the demographic targeted, the current text is sufficient (possibly overly wordy at that) and regards the question of how to move, they are used to interfaces far worse than this---they will figure it out. I suppose that you could claim that as part of the puzzle :)

I disagree. Use the clearer set of instructions. Do not leave confusing instructions in place just because the target demographic can decipher them while others are left in confusion.

If we want the captcha to be accessible outside the target demographic, we should scrap the whole chess thing as well.

Re: Chess CAPTCHA

#107

Earlier quoted context omitted.

CAPTCHA solve a specific design problem. They are not an IETF protocol or solution to be used everywhere. That's kind of the issue. Once a CAPTCHA is worth enough it will be overcome. The problem is to design a CAPTCHA that implements just enough headache to make it worthwhile not to overcome and at the same time not frustrating users. I think this chess problem uniquely and elegantly solves the problem for the site…

if the idea of the chess captcha is to be used once on a single site, (ignoring the fact that it's a chess captcha for a chess community) it's very over engineered. Jeff Atwood gets away with a captcha where all you have to do is type "orange" to post a comment[1] and even that manages to mitigate a lot of spam. http://www.codinghorror.com/blog/2008/03/captcha-is-dead-lon...

There's no such thing as overengineering if it entertains the users while meeting the mission intent. :P

Re: Chess CAPTCHA

#108

Considering that modern chess software can defeat grandmasters, the Chess CAPTCHA seems more designed to admit bots instead of humans. "It was my luck (perhaps my bad luck) to be the world chess champion during the critical years in which computers challenged, then surpassed, human chess players" From Garry Karparov: http://www.nybooks.com/articles/archives/2010/feb/11/the-che...

This CAPTCHAs are easy enough for humans :)

And writing a bot to defeat them would take more time than posting your viagra ads manually in all four sections of this forum.

Re: Chess CAPTCHA

#109
post #43

Brilliant building of software. Less than brilliant copy. I would change Black plays; checkmate in one! This is a chess CAPTCHA. Click on the board to make your move, and prove you are human. to This is a chess CAPTCHA... To prove that you are human, click on a black piece, then click on the only destination square that will checkmate. I really don't mean to nitpick, but took me a minute to figure out what to do. Som…

When writing instructions for users who might see the instructions frequently, putting an introduction like that, especially with the locally-relevant data buried, is not helpful.

Instead, their terse instructions, written in a familiar and easily-parsable format are ideal. Placing a "What is this?" link afterward that opens[1] to more detailed instructions is how you should approach this.

[1] Through whatever mechanism is most appropriate for your audience. I'd suggest a tooltip by default.

Re: Chess CAPTCHA

#110
post #45

I am fairly certain it would be quicker to program a computer that can brute force a checkmate in one than I can solve these things by hand. You have what, 11 pieces, they can move into 64 positions each (at most, much less in reality). That means a computer must brute force 64*11 = 704 attempts. In other words, no time at all to bruteforce this once you've read the grid. Reading the grid in itself is rather trivial…

Yes, an afternoon of coding to be able to post spam on exactly one website. Until they change the captcha.

Actually, the captcha predicate is a GET request that looks like this:

http://en.lichess.org/captcha/78pkfjgz?solution=e5+e4 which returns 1 or 0.

So the brute force captcha solution is to go through 8^4 (~4k) get requests, which you could code in five minutes and execute in a minute.

Post reply on HN