Hacker Newsnew | past | comments | ask | show | jobs | submit | TheRedBarron's commentslogin

Looks great!!


Oh certainly. I thought I'd explained my thought process but what I meant was that "Since the same number of colors exists then a arrangement may exist" and given that it may a brute-force type approach was taken to confirm that one indeed does


Yeah that tweet was a let down. I guess the best resolution is that pangrams (or things with many unique letters) are hard to come by?


Interesting. The issue I was getting was that it would like tweets that were "@MyFriendWhoHasAUserNameLikeZXCVBNMQWERTYU hey". Should I just strip it of the word "@____"?


That would absolutely be the way I'd suggest going about it.


Okay. Iteration is key! I'll update her maybe tonight. Thanks


I'd try stripping such words (and URLs) when they appear at the start or end of the tweet. If in the middle, removing seems likely to mess with the meaning.


hahah I should have thought of that!


I made something that did stats on this a few months ago

see it here

https://barronwasteland.wordpress.com/2014/08/04/random-move...


It seems like draw by insufficient mating material needs to be separated out from draw by repetition, although if you only enforce draw by repetition, it will inevitably happen on a board with insufficient mating material.

ChessPeace says "Draws by insufficient mating material is not available because of insufficient theory dealing with the non-standard pieces".

"Play with many new pieces with new abilities not seen in standard chess"

It seems that if the board is currently limited to standard pieces, it should use the standard rules for draws by insufficient mating material. How hard is that? No pawns, no non-standard pieces, no queen, no rook, less than two bishops, and no knight + bishop.


Those statistics are surprising.


Correct, hence part two was required. This went into some of the possible errors that came up

https://barronwasteland.wordpress.com/2014/12/13/infinite-mo...


Thanks for putting this here!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: