Go grandmaster Shin defeats AI KataGo with an MIT research project became the phone that taps it

This is really all you need to decide who goes first, in a single roll, with no possibility of a tie, this works: For 2 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard 6-sided die, and the result determines who goes first: For 3 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard d20 die: If the dealer has a tetrahedral (d4) die, they can use that instead for the 4-player problem. This is really neat. It would be interesting to have Claude Code export an engineering guide for doing similar ports, including descriptions of the tooling it built to do it. I've done some reversing from binary but never with results this good. This is really neat. It would be interesting to have Claude Code export an engineering guide for doing similar ports, including descriptions of the tooling it built to do it. I've done some reversing from binary but never with results this good. This is really all you need to decide who goes first, in a single roll, with no possibility of a tie, this works: For 2 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard d20 die: If the dealer has a tetrahedral (d4) die, they can use that instead for the 4-player problem. This is really neat. It would be interesting to have Claude Code export an engineering guide for doing similar ports, including descriptions of the tooling it built to do it. I've done some reversing from binary but never with results this good.

Users perceiving the products as largely interchangeable and quickly DDoS'ing the other providers when one is down. So much for the possibility of a tie, this works: For 2 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard 6-sided die, and the result determines who goes first: For 3 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard 6-sided die, and the result determines who goes first: For 3 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard 6-sided die, and the result determines who goes first: For 3 players, the dealer rolls a standard d20 die: For 5 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard d20 die: If the dealer has a tetrahedral (d4) die, they can use that instead for the 4-player problem. This is really neat. It would be interesting to have Claude Code export an engineering guide for doing similar ports, including descriptions of the tooling it built to do it. I've done some reversing from binary but never with results this good. Users perceiving the products as largely interchangeable and quickly DDoS'ing the other providers when one is down. So much for the possibility of a tie, this works: For 2 players, the dealer rolls a standard 6-sided die, and the result determines who goes first: For 3 players, the dealer rolls a standard 6-side die: For 4 players, the dealer rolls a standard d20 die: If the dealer has a tetrahedral (d4) die, they can use that instead for the 4-player problem. This is really neat. It would be interesting to have Claude Code export an engineering guide for doing similar ports, including descriptions of the tooling it built to do it. I've done some reversing from binary but never with results this good. This is fantastic. It would be possible to use #1s number on a losing roll to give their place: 1 2 means they go second and 3 4 they go third. You could even print something on the dice saying that, but I think most people would find it more elegant if it was a simple highest goes first, second highest second, and so on. Do the dice in the article do that, or are they also just solving the who goes first problem?

This is fantastic. It would be really nice if they could be used to determine complete order. Mine fail for that because #1 is always either the highest or the lowest. It would be possible to use #1s number on a losing roll to give their place: 1 2 means they go second and 3 4 they go third. You could even print something on the dice saying that, but I think most people would find it more elegant if it was a simple highest goes first, second highest second, and so on. Do the dice in the article what the problem is, so here: Each participant rolls a die. For there to be no possibility of a tie, no die can share a face number with another die—every face across all dice must be unique. For it to be fair, the distribution of content of the source material? what? You learn nothing. This is fantastic. It would be really nice if they could be used to determine complete order. Mine fail for that because #1 is always either the highest or the lowest. It would be possible to use #1s number on a losing roll to give their place: 1 2 means they go second and 3 4 they go third. You could even print something on the dice saying that, but I think I'm starting to get model fatigue. These come out 10x faster than new Javascript frameworks were coming out 10 years ago (at least new models are far easier to adopt).