> if you can do the worst “bad” thing possible, you can also do the best “good” thing possible
You say this like it's a truism, but I don't think it is. The bad things may be categorically easier than the good things. It's easier to destabilize a delicate system than to stabilize it. It's easier to break something than to fix it.
Cipher noob question: is there any check that can be done to ensure a cipher is actually decodable? What if the author made a flaw when encoding it, so that it's not actually solvable?
My intuition is no, the family of cipher methods (even those that could be implemented by hand) is too open-ended, so there's no particular statistic that you could expect to see for all solvable ciphers and no unsolvable ciphers.
The definition of solving a cipher must be something like getting a highly meaningful result (like intelligible natural language text) by applying a process with relatively low Kolmogorov complexity relative to the length of the output. If you don't have a constraint like that, it could literally be meaningless what should count as a solution. For example, a cipher that was encrypted under a one-time pad can be successfully decoded to any plaintext just by choosing the appropriate key; there's no reason to prefer any plaintext over any other unless you have external knowledge that constrains the plaintext and/or the key. (That's what it means for the one-time pad to be information-theoretically secure, which is the lack of a constraint that helps distinguish a "good" solution from a "bad" solution.)
Basically you could say that every cipher is a transformation of a plaintext with some kind of computer program. (The human who invented the cipher may not have thought of it as a computer program, perhaps because computers hadn't even been invented yet, but there should be an equivalent program to the encipherment and decipherment process.) A good solution in that Kolmogorov complexity sense is like "a short program produced a meaningful decryption". There are statistical methods to recognize some kinds of plaintext, and there are statistical methods to recognize properties of specific ciphers (for example, to guess the most likely length of a Vigenère key), but it doesn't seem that this can inherently generalize across "all possible programs".
But if you want to limit the family of ciphers to specific things like Vigenère or Playfair or something, then yes, there are good statistical tests. It's just that it creates a higher-order question of how much flexibility the cipher creator could have had to choose a cipher method, conceivably including one that isn't attested anywhere, or one that has more good security properties of some kind than other classical ciphers did.
It seems like this will intersect with historical research, like "well, I don't think that so-and-so was actually sophisticated enough to literally create an interesting new kind of cipher from scratch, so therefore if this is a real message, it's probably one of these methods that would have been known in that cultural environment at that time and place", which maybe is enough of a constraint to have decent statistical tests. But we still have some idiosyncratic things like the Voynich Manuscript where experts have been fighting for decades over the baseline question of whether it's actually an enciphered human language plaintext!
The worst case problem is not even an error in encipherment but the idea that the apparent ciphertext could literally be random (chosen by throwing dice or spinning a wheel or drawing letter tiles or something), so there's no form of meaningful decipherment possible by any means, even with the original creator's knowledge.
Without a third-party check, nope. Case in point, Chaocipher ... https://www.chaocipher.com/ e.g. see "Progress Report #23" the PDF there. Transcription errors galore!
This cipher context "rhymes" well with Kryptos K4 in many ways.
Actually the article that you didn't bother to read mention a few encoding errors that Fable has been able to recover and point to the probable author's intent.
I did bother to read it, and that isn't what I meant. I wasn't referring to one-off errors that you can fix after successfully decoding a cipher into something that produces a majority-correct answer. I meant something more akin to what schoen's answer touched on: whether there are any closed-form mathematical/statistical analyses that can be performed ahead of time to assess the structural legitimacy of any ciphertext before you spend a lot of cycles trying to decode it.
There's a larger existential crisis still in store for you. Our global civilization is collapsing. We are choking to death on the unchecked negative externalities of our own progress. It is our species' Achilles heel. Whether or not an individual developer adapts to this temporary capability blip (agentic coding) will not matter in the long run. The systems necessary for supporting these capabilities are too brittle to survive the century.
Where is the evidence for this? I use Claude every day at work but other than that my life hasn’t changed at all. Electricity, food production, security, human relations, the house I live in etc. hasn’t change.
Where did you get that from? This must be relying on picking very specific parts of the Arctic. This year has not been unusual for the Arctic, in fact, it was colder than the normally cited average (1958-2002). Take a look, see for yourself:
It didn't go above freezing this year, which is unusual (actually I think it may be the first time on record!)
Sea ice extent is a fair bit above the record low in 2012, where "record" here means arbitrarily starting in 1981, although sea ice extents have been observed much further back.
Not the parent, but pointing out a couple of problems in your analysis:
First, arctic temperatures: this is a widely misunderstood point. Notice that in the graph, the non-summer months are noticeably warmer. The summer months are going to be effectively capped at around 0 degrees until all the ice is gone, so holding up this graph and saying "look, the temperature never got above freezing!" is misleading, because the "warming" is actually happening as a function of melting ice, not air temperature.
Sea ice extent: the last 18 years were the lowest 18 minimums on record. Also, ice extent != ice volume. March 2026 recorded a record-low ice volume. An extent chart reads the same regardless of whether the underlying ice is thin or thick.
Greenland mass balance: here you're just plain wrong. You linked to the surface mass balance page, in other words, snowfall minus surface melt + runoff. This does not account for glacial calving and basal melt. The page you linked says this directly. Total mass balance is a grimmer picture: an average loss of about 252 km³ of water per year over 2003-2025, contributing 0.69 mm/yr to sea level rise.
This is why we're so screwed. People can't even read graphs. They'll stand outside in smoke-filled scorching summer heat and say "but Joe Rogan says the earth is in a cooling cycle".
It's quite misleading to take a two week period and describe it as "last winter". No wonder people give blank looks, it was a transient spike that means nothing. The idea everyone should feel sad is based on arguments about long term averages.
But they were almost exactly average in February. You're reading far too much into noise. The idea of a climate crisis is built on arguments about trends that span hundreds of years, not two weeks.
I think there's some sort of communication gap here. My point is that neither fact tells you anything much, especially not about "how screwed" we are. It's not a battle of data points.
Definitely a comms gap. I'm not going to sit and list all the evidence for the climate crisis we're currently experiencing in an offhand HN comment. I'm going to say something like "this winter we saw crazy high anomalies" to express how screwed we are.
You say this like it's a truism, but I don't think it is. The bad things may be categorically easier than the good things. It's easier to destabilize a delicate system than to stabilize it. It's easier to break something than to fix it.
reply