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

That's a consequence of not being allowed to put yourself in check (by any means).


The only way to put yourself in check is by moving.


The only action you can ever take in chess is moving.


You can resign, too.


You can put yourself in check by moving the king. That has nothing to do with pinning. Adding a rule for pinning is redundant.


It isn’t an added rule for pinning. It’s the only rule about putting yourself in check.


Did you mean putting your opponent in check? In chess, you are not allowed to put yourself in check.


You said “ That's a consequence of not being allowed to put yourself in check (by any means).” My point is that there are no other means.


I was replying to a comment quoting an official rule saying "no piece can be moved if that exposes or leaves its own king in check."

I was pointing out that that specific rule (read to mean that moving a piece pinned against a king is not allow) is not strictly necessary. Putting oneself in check is not allowed regardless of whether it's because you moved a piece that was pinned against your king or moved your king directly into the line of sight of an opponent's piece. These are the different "means."

As a sibling comment points out, "The only action you can ever take in chess is moving," so it's not particularly meaningful to say that the only way to put yourself in check is by moving.


And likewise, it's not particularly meaningful to say "That's a consequence of not being allowed to put yourself in check (by any means)."

The rule, "3.9.2: no piece can be moved if that exposes or leaves its own king in check." covers both the case of moving a pinned piece as well as moving the king into check, i.e. it covers all "means" of putting yourself into check.


Will we?


Sometimes HN admins revive quality posts that didn't get much traction when they were first posted. When this happens, the timestamps are updated to make the post look new.

I can't say for sure whether this is what happened here, but it is a possible explanation.


This post did in fact go through the second-chance pool: https://news.ycombinator.com/pool

(For more details on posts getting “rescued”, see Dan’s comment here: https://news.ycombinator.com/item?id=11662380)


The comment you're replying to already mentions this.


Works best when your meetings are 40 minutes long


Obviously, meetings shouldn't be longer than they need to be. But 15-20 minutes of unused time tend to be dead. That's mostly not long enough to do anything useful.

That said, nothing wrong with 30 minute meetings. In my previous analyst stint we tried to default to that--especially for non-clients. Didn't need all the throat-clearing stuff and industry background that we knew perfectly well.


More info on Wikipedia: https://en.wikipedia.org/wiki/Texas_Interconnection

> The Texas Interconnection is maintained as a separate grid for political, rather than technical reasons



steganography — stenography is courtroom transcription


People protect their secrets from stenographers with steganography.


The AI narration was off-putting, but the video footage was cool.


That is not AI. The same voice narrates at least two years ago. Just scroll down in the channel's video list.


The description of the video states it is in fact AI:

> A synthesized text-to-video voiceover was used in the narration for this story.


Where does it say that? I can’t see it in the video description.


The second line. The video description for me says the following:

"HAWAIʻI VOLCANOES NATIONAL PARK - An incredible sight at the summit of Kilauea volcano on Saturday morning, as Episode 38 erupted enormous lava fountains across the caldera, destroying one of the webcams that was live streaming the event.

All images and video are courtesy the U.S. Geological Survey. A synthesized text-to-video voiceover was used in the narration for this story."


Well it would've been better if they kept the video on the actual camera that ate it instead of switching back and forth constantly. It's not Liam Neeson climbing a fence, guys.


The dependency has just come out of the oven, so it's too hot and must cool down ;)


I addressed this though lol. Nobody says "my pie is on cooldown."


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

Search: