<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: mswphd</title><link>https://news.ycombinator.com/user?id=mswphd</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Mon, 15 Jun 2026 09:50:49 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=mswphd" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by mswphd in "Anthropic apologizes for invisible Claude Fable guardrails"]]></title><description><![CDATA[
<p>This kind of reasoning leads you to reasoning that if he was an <i>ineffective</i> fraudster, it would be less moral, as he would have bought less mosquito nets. So it’s not only moral to do fraud, but you most <i>extremely competently</i> do fraud.<p>I think this being a reasonable utilitarian point to make is not a point in utilitarianism’s favor.</p>
]]></description><pubDate>Thu, 11 Jun 2026 20:50:43 +0000</pubDate><link>https://news.ycombinator.com/item?id=48496227</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48496227</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48496227</guid></item><item><title><![CDATA[New comment by mswphd in "How Terry Tao became an evangelist for AI in math"]]></title><description><![CDATA[
<p>the way to interpret the gigantic lean proof is not by inlining each lemma, looking at all the lines, and thinking "yeah that's a lot". That's also not the way to read a paper.<p>Instead, you proceed in layers of abstraction. For example<p>1. the main claim may rest on some set of sub-claims, as well as some local (to teh main claim) work to "patch things together"<p>2. each of those sub-claims themselves may require other sub-claims + local work, etc<p>These can be collected into a dependency graph. In lean, this is often called a "blueprint". Here is the blueprint for the formalization of the Polynomial Frieman-Rusza conjecture (now a theorem, by Gowers, Green, Manners, and Tao).<p><a href="https://teorth.github.io/pfr/blueprint/" rel="nofollow">https://teorth.github.io/pfr/blueprint/</a><p>This layer of abstractions is (roughly) equivalent a different way to format mathematics. You could remove the Lean component (let alone any AI), and create such a dependency graph for a paper. I would argue this is a <i>clearer</i> way to format mathematics (again, ignoring both the formal verification applications of it, as well as AI).<p>Any mathematics paper intrinsically has a graph such as this underlying it, and tries to make the various linkages in the graph clear via prose. Prose is only so powerful a way to organize things. I'm sure you're familiar with the way early mathematicians would describe various formula (e.g. the quadratic formula) via prose. It is very hard to understand.<p>Separately from this dependency-graph perspective, you can do things like<p>1. add formal verification. Now, each component in the dependency graph is verifiable with high confidence (though harder to write and read). This has some benefits and downsides. Harder to write and read is bad. Being able to have high confidence in the veracity of the result is *very* good. It allows larger collaborations in mathematics. Previously, a large collaboration would require all mathematicians to trust eachother to a large extent. This is (practically) difficult.<p>2. when each component can now be verified to high accuracy, you can now throw AI at it. I won't extoll the virtue of this. There are parts of it that seem interesting, but many "AI for Math" things currently are stil producing unformalized papers (in prose).<p>Maybe the main thing I'd say is that this type of "graph structure, with each component trusted" is already implicitly what mathematicians do. You write papers that cite other papers etc. Except now, instead of needing to look for status signals to trust papers (or invest personal effort), you can look for another (honestly fairer) signal to trust papers. So there's a sense in which formalization allows for the democratization of mathematics. I do think there's something beautiful about that.</p>
]]></description><pubDate>Thu, 11 Jun 2026 19:52:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=48495548</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48495548</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48495548</guid></item><item><title><![CDATA[New comment by mswphd in "Anthropic apologizes for invisible Claude Fable guardrails"]]></title><description><![CDATA[
<p>The first half of your answer presupposes some platonic utilitarian calculus that, if it were applied correctly, would yield moral outcomes. This is very hard to believe. If I look at notable/well-known examples of EA-affiliated people, it is hard to skip by members such as SBF. Did he correctly apply the utilitarian calculus?<p>It is relatively easy to take the proceeds of a massive fraud, buy a relatively small (as a percentage of the fraud) $ amount of mosquito nets, and save more lives than the lives impacted by your massive theft. Is this a correct application of the utilitarian calculus? What sort of data would we need <i>a priori</i> to do this calculation "correctly"? Do you think he had a careful estimate of the suicide rate of victims of ponzi schemes before perpetuating the fraud, or would any suicide rate have made the decision net [pun intended] moral, as any such victim of fraud would lead to >> 1 net purchased (so you would almost always net save lives).<p>The above is of course snarky. It is also a best-effort way of analyzing a notable utilitarian's actions. I do not think it would be difficult at all to use this type of argument to argue that SBF's actions net raised utility in the world. If only we all would become fraudsters, then we could truly live in Omelas --- a notable utilitarian paradise.</p>
]]></description><pubDate>Thu, 11 Jun 2026 18:32:29 +0000</pubDate><link>https://news.ycombinator.com/item?id=48494517</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48494517</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48494517</guid></item><item><title><![CDATA[New comment by mswphd in "Apple Core AI Framework"]]></title><description><![CDATA[
<p>there's pros and cons to it for them. Clearly, they get good branding (at least in enthusiast circles). Perhaps more important is they get community work on optimization. There have been significant performance uplifts on the Qwen3.6 models from the open-source community since they were launched (at a minimum, multi-token prediction is now working with them. It is almost a 2x token generation speedup)<p><a href="https://www.reddit.com/r/LocalLLM/comments/1ti9w4o/qwen3635ba3bmtp_on_an_rtx_3090_in_lm_studio_is/" rel="nofollow">https://www.reddit.com/r/LocalLLM/comments/1ti9w4o/qwen3635b...</a></p>
]]></description><pubDate>Wed, 10 Jun 2026 14:11:53 +0000</pubDate><link>https://news.ycombinator.com/item?id=48476587</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48476587</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48476587</guid></item><item><title><![CDATA[New comment by mswphd in "Let's Encrypt bans certificate usage in any US sanctioned territory [pdf]"]]></title><description><![CDATA[
<p>love thought-terminating cliches. really helps keep from actually thinking ever.</p>
]]></description><pubDate>Tue, 09 Jun 2026 17:01:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=48463863</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48463863</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48463863</guid></item><item><title><![CDATA[New comment by mswphd in "An introduction to functional analysis for science and engineering"]]></title><description><![CDATA[
<p>both no in principle, and when you're used to reading LaTeX, word is ugly. It's a milder form of how if these notes were handwritten it wouldn't matter, but it would also be less appealing than them being typeset well.</p>
]]></description><pubDate>Tue, 09 Jun 2026 16:53:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=48463728</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48463728</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48463728</guid></item><item><title><![CDATA[New comment by mswphd in "Apple Core AI Framework"]]></title><description><![CDATA[
<p>Yes and no.<p>Qwen 3.5 was released 3/2/2026. It includes models up to a 397B-A17B model<p><a href="https://huggingface.co/collections/Qwen/qwen35" rel="nofollow">https://huggingface.co/collections/Qwen/qwen35</a><p>A day afterwards, a high-up technical leader working on Qwen was let go<p><a href="https://techcrunch.com/2026/03/03/alibabas-qwen-tech-lead-steps-down-after-major-ai-push/" rel="nofollow">https://techcrunch.com/2026/03/03/alibabas-qwen-tech-lead-st...</a><p>The more recent Qwen 3.6 was released on 4/16<p><a href="https://huggingface.co/collections/Qwen/qwen36" rel="nofollow">https://huggingface.co/collections/Qwen/qwen36</a><p>This does not include any particularly large models. But the models it contains (Qwen3.6 27B and Qwen3.6 35B-A3B) are the local models people have been very excited about lately. So they didn't release any larger models, and the models people praise so much are from this most recent release.</p>
]]></description><pubDate>Tue, 09 Jun 2026 03:35:00 +0000</pubDate><link>https://news.ycombinator.com/item?id=48456021</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48456021</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48456021</guid></item><item><title><![CDATA[New comment by mswphd in "Sum-product, unit distances, and number fields"]]></title><description><![CDATA[
<p>|x| on a vector is not well-typed. The notation for norms of vectors is ||x||, namely 2 bars on each side.<p>There still is a naming collision between |X| (cardinality of a set) and |x| (absolute value of a scalar). Sometimes this happens. It generally is still unambiguous though, as mathematicians tend to use different segments of the alphabet for different purposes, and also additionally tend to capitalize sets, and leave scalars lower case.</p>
]]></description><pubDate>Fri, 05 Jun 2026 01:30:23 +0000</pubDate><link>https://news.ycombinator.com/item?id=48406914</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48406914</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48406914</guid></item><item><title><![CDATA[New comment by mswphd in "Branchless Quicksort faster than std:sort and pdqsort with C and C++ API"]]></title><description><![CDATA[
<p>Funny: you can cf "sorting network", and see they use them within their own design even.</p>
]]></description><pubDate>Thu, 04 Jun 2026 22:45:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=48405701</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48405701</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48405701</guid></item><item><title><![CDATA[New comment by mswphd in "A Post-Quantum Future for Let's Encrypt"]]></title><description><![CDATA[
<p>this is broadly true. I've heard some criticisms of industrial QC research along these lines, namely that it runs into the issue that its entire TAM ends up being some combination of<p>1. defense contracting, which can definitely be lucrative, but (hopefully) will dry up quickly after the PQ transition (and especially will if we successfully transition before QCs are advanced enough, which is the goal), and<p>2. theft, with things like e.g. stealing bitcoins or whatever.<p>The second is plausibly a large market. It may be difficult to put it on a quarterly report though. So the economic basis industrial QC research may not end up panning out.</p>
]]></description><pubDate>Thu, 04 Jun 2026 17:36:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=48401929</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48401929</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48401929</guid></item><item><title><![CDATA[New comment by mswphd in "A Post-Quantum Future for Let's Encrypt"]]></title><description><![CDATA[
<p>I am pointing out a particular cryptographer's abysmal track record in understanding the security of PQ schemes to call into question their current criticisms of PQ schemes. They've always been (in my opinion obviously) fear-mongering in the past. None of this fear-mongering has been right. So I do not put particularly high weight on their current fear-mongering.<p>This is especially true because they often <i>lie</i> in their fear-mongering. For example, you appear to be a follower of Dan. You seem to think the argument against hybrids is an argument against hybrid <i>KEMs</i>. It's not. That is a lie. Even Dan's recent tirade on the TLS-WG mailing list has been against putting forward an <i>informational RFC</i> on ML-DSA, a (pure lattice) <i>digital signature</i> scheme.<p>Perhaps you misunderstood this, and Dan accurately described the setting he is fear-mongering over. Perhaps Dan misrepresented things again, as he has been doing for nearly a decade again. I don't particularly care either way. All that matters to me is accurate evaluation of our current options. It is exceedingly frustrating that a high-profile cryptographer seems incapable of doing this, either due to incompetence or malice.</p>
]]></description><pubDate>Thu, 04 Jun 2026 17:32:52 +0000</pubDate><link>https://news.ycombinator.com/item?id=48401871</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48401871</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48401871</guid></item><item><title><![CDATA[New comment by mswphd in "A Post-Quantum Future for Let's Encrypt"]]></title><description><![CDATA[
<p>Nation states have been pouring billions into QC. It's hard to collect the varous announcements into clean figures, but rough estimates are that the US has allocated ~$5B to QC computation research, the EU (via the EU itself, and individual member states) have allocated more (closer to ~$10B-15B), and China has allocated a similar amount (again in the ~$10B range).<p>Industry quantum computing has made precipitous progress in the last few years, leading to industry companies (e.g. Cloudflare) to upping their personal targets for transition to 2029. You can read their motivation in the first few paragraphs of the following<p><a href="https://blog.cloudflare.com/post-quantum-roadmap/" rel="nofollow">https://blog.cloudflare.com/post-quantum-roadmap/</a><p>We are currently in a place where it is entirely plausible that nation states will have quantum computers capable of breaking EC crypto (and RSA, although paradoxically it is mildly harder to break quantumly due to larger data sizes) by 2030. This is not guaranteed. But there have been increasingly many warning signs.<p>Maybe you don't care, and want to bury your head in the sand. That's your prerogative. But cryptographers do care, and so are taking all of the above very seriously.</p>
]]></description><pubDate>Thu, 04 Jun 2026 17:24:55 +0000</pubDate><link>https://news.ycombinator.com/item?id=48401763</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48401763</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48401763</guid></item><item><title><![CDATA[New comment by mswphd in "A Post-Quantum Future for Let's Encrypt"]]></title><description><![CDATA[
<p>the rational argument is that this time is not particularly worse than prior transitions, and arguably is one we are doing much more clear-eyed (think about all the ECC vulnerabilities during their first few years of deployment due to not knowing how to "pick safe curves". The analogous issue for standardized NIST PQ schemes is understood very well). So the hysteria around the transition, from an expert's perspective, is misplaced.<p>This doesn't guarantee things will work. In cryptography there are no guarantees. In particular, failing to transition fast enough can also lead to vulnerabilities (by this I mean quantum attacks. Cryptographers are increasingly worried this may happen very soon. I've seen some estimate as soon as 2030). So there is an underlying tension in changing, and also a clear worry about not changing.</p>
]]></description><pubDate>Thu, 04 Jun 2026 17:17:04 +0000</pubDate><link>https://news.ycombinator.com/item?id=48401646</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48401646</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48401646</guid></item><item><title><![CDATA[New comment by mswphd in "A Post-Quantum Future for Let's Encrypt"]]></title><description><![CDATA[
<p>note that OTP is only "perfectly secure" for a rather limited notion of security, namely IND-CPA. This is (roughly) an "honest but curious" adversary who looks at data on the wire (or wherever), but never tampers with it.<p>This is not a particularly realistic attack model. People typically instead want security against an "active" adversary who does whatever they can (say IND-CCA2 security). You <i>can</i> achieve this information-theoretically, given enough pre-shared randomness, by (roughly) taking some standard Authenticated Encryption with Associated Data (AEAD) construction, and swapping out whatever primitives that are used with information-theoretically secure components. A OTP for the block cipher and a Wegmen-Carter MAC for the MAC should work.<p>Note that this gives you a scheme with roughly the same practical security as standard ones (unless you think someone can break AES), but it <i>still</i> can be subject to non-trivial attacks that AES cannot. In particular<p>1. randomness used on both sides MUST never be repeated, and MUST stay in sync throughout, so<p>2. both sides MUSt stay in sync as to where 1. they are in terms of the randomness they're using, and where 2. the other half of the communication is. Realistically these should be two completely different randomness streams to guard against race conditions where otherwise each side may accidentally reuse a block of randomness<p>3. having to stay in sync adds several difficulties. In particular, network issues become much more annoying to deal with. This is true for e.g. environmental network disruptions, but also (plausibly) an adversary can disrupt the network temporarily. If this causes you to lose synchronization, then <i>best case</i> this temporary network disruption becomes a permanent network disruption. Worst case it manages to get randomness re-used on one side, which then breaks everything.<p>The above is likely not an exhaustive list of the problems you have to deal with. But still, you can see how it quickly becomes unclear if things are easy to implement.</p>
]]></description><pubDate>Thu, 04 Jun 2026 17:11:57 +0000</pubDate><link>https://news.ycombinator.com/item?id=48401572</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48401572</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48401572</guid></item><item><title><![CDATA[New comment by mswphd in "A Post-Quantum Future for Let's Encrypt"]]></title><description><![CDATA[
<p>these have always been an issue, and were the motivation for starting the NIST standardization in ~2016. My point is more that recent developments in quantum computing have caused many cryptographers to go from "we should do this so people are secure if progress happens in the decades from now" to "this may be a near-term issue, and we should prioritize transition for user safety issues". You can read some about this in a cloudflare article from 2 months ago, which mentions some recent developments that have people concerned about possible "Q-day" being in ~2029-2030". This is much earlier than what was the consensus 5 years ago.<p><a href="https://blog.cloudflare.com/post-quantum-roadmap/" rel="nofollow">https://blog.cloudflare.com/post-quantum-roadmap/</a><p>Part of this is because of a 3rd reason to transition early, which is the "long tail" of deployments which will switch over (potentially very) slowly. Think embedded/iot devices that are either difficult to patch, or have vendors who are not as security-focused.</p>
]]></description><pubDate>Thu, 04 Jun 2026 16:56:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=48401369</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48401369</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48401369</guid></item><item><title><![CDATA[New comment by mswphd in "SpaceX's IPO is a disaster waiting to happen for your pension fund"]]></title><description><![CDATA[
<p>Again, not everyone responds to a perceived social ill by gambling. Timing a short is still gambling.</p>
]]></description><pubDate>Thu, 04 Jun 2026 03:46:24 +0000</pubDate><link>https://news.ycombinator.com/item?id=48393510</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48393510</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48393510</guid></item><item><title><![CDATA[New comment by mswphd in "A Post-Quantum Future for Let's Encrypt"]]></title><description><![CDATA[
<p>it's worth mentioning opinions have started to shift away from this. Quantum computing has made quite concrete progress in the last ~2 years. No guarantee this continues, but among people I know it has changed their perspectives from (roughly) similar things as that essay, to thinking we really must transition now.</p>
]]></description><pubDate>Thu, 04 Jun 2026 02:20:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=48392860</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48392860</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48392860</guid></item><item><title><![CDATA[New comment by mswphd in "A Post-Quantum Future for Let's Encrypt"]]></title><description><![CDATA[
<p>First, it doesn't, because we don't use public-key encryption. Instead, we use key-encapsulation mechanisms, which you have to hybridize in another way.<p>Second, hybridization can add weaknesses in several ways<p>1. Hybridization may preserve some, but not all, security properties of the constituent parts. This is the case for hybrid signatures. In particular, ML-DSA signatures have a better than SUF-CMA type of security typically called "BUFF" security. Known hybridization techniques lose this security.<p>2. Hybridization is also more code (and more <i>complex</i> code) to write. Historically, the vast majority of cryptographic issues come from implementation issues, not fundamental weaknesses in the underlying hard problems. So suggesting to obtain security by doing more complex things may not always achieve the desired goal.</p>
]]></description><pubDate>Thu, 04 Jun 2026 02:18:47 +0000</pubDate><link>https://news.ycombinator.com/item?id=48392850</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48392850</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48392850</guid></item><item><title><![CDATA[New comment by mswphd in "A Post-Quantum Future for Let's Encrypt"]]></title><description><![CDATA[
<p>> as they almost certainly have weaknesses for some of those new PQ schemes already lying around<p>why believe this about PQ schemes vs about pre-existing schemes? Or any other schemes?<p>It's also worth mentioning that it appears that other countries (in particular China) will adopt fundamentally similar schemes. The NSA loves vulnerabilities, but generally only vulnerabilities of a certain type. These are generally referred to as "NOBUS"<p><a href="https://en.wikipedia.org/wiki/NOBUS" rel="nofollow">https://en.wikipedia.org/wiki/NOBUS</a><p>It includes things like backdoors (say DUAL_EC_DRBG), as well as historically things like reducing the key size of DES, where the US thought they'd be able to brute force it (but other countries would lack the compute). Historically the NSA has actually <i>assisted</i> in removing non-NOBUS vulnerabilities (at least they did this with the SBOX design of DES, which was vulnerable to differential/linear cryptanalysis --- I forget which).<p>The NSA hasn't publicly assisted/disclosed any vulnerabilities with currently suggested schemes, though a close US ally (Isreal, through an IDF group known by Matzov) has. If America was hoarding vulnerabilities, one might imagine America would have pressured Isreal to keep this secret.<p>A final point is that it's not clear where the NSA would source the vulnerabilities. By a peculiar chain of coincidences, nearly all of the most successful lattice cryptanalysts are European. None have "gone dark" in a way that would be concerning (say how Don Coppersmith did, when he moved to a NSA affiliate in the mid 2000s). This isn't to say that it would be impossible for the NSA to have better-than-public vulnerabilities, but more to say that they can't just take some of the most successful people who have publicly attacked the problem, and throw more money at them. Their "talent-pipeline" for this particular problem is not as available (and many cryptographers soured on working with them post-Snowden anyway).</p>
]]></description><pubDate>Thu, 04 Jun 2026 02:15:48 +0000</pubDate><link>https://news.ycombinator.com/item?id=48392829</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48392829</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48392829</guid></item><item><title><![CDATA[New comment by mswphd in "A Post-Quantum Future for Let's Encrypt"]]></title><description><![CDATA[
<p>it's not just those two institutions. South Korea is running their own standardization currently, and fundamentally similar algorithms are expected to win (some more modern insights might be incorporated, due to starting >=5 years after the NIST standardization did, but still).<p>The Chinese Academy of Science made their own professional recommendation to the Chinese government a few years ago to use fundamentally similar schemes. The Chinese government this year is planning to start on their own standardization. Again, it is expected they will use fundamentally similar schemes.<p>The German BSD has suggested their own schemes as well, which are fundamentally similar (they suggested unstructured lattices, which is mildly different. They've also made some incompetent suggestions regarding quantum networking though iirc, so it might be a BSD-specific quirk).<p>Cryptographers are paranoid by default. It's really the only reasonable way to evaluate things competently. Even among the paranoid though, there's been no plausible argument suggested that something bad is happening with the PQ transition. People will point various fingers, for example<p>1. a backdoor! Except we can typically detect the possible presence of a backdoor, and nobody has suggested anything despite the designs being fundamentally fixed over the last 15 years (again, except the "one obvious" possible backdoor of standardizing a ML-KEM lattice, which was decided against for this reason), or<p>2. lattice-based problems are classically weak! There is no publicly visible reason to suspect this. One might then conjecture that they're weak in only a way a nation-state can detect/exploit. Then it would be <i>very weird</i> that it appears that both the US and China will both adopt lattice-based schemes.<p>It takes more to be a competent cryptographer to be blindly paranoid. There has been zero credible reasons presented though, and the cryptographic community has been looking into these problems and constructions for well over a decade now.</p>
]]></description><pubDate>Thu, 04 Jun 2026 00:50:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=48392282</link><dc:creator>mswphd</dc:creator><comments>https://news.ycombinator.com/item?id=48392282</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=48392282</guid></item></channel></rss>