Statement on US government directive to suspend access to Fable 5 and Mythos 5
Summary
The U.S. government issued an export‑control directive requiring Anthropic to suspend all access to its Fable 5 and Mythos 5 models for any foreign national, including Anthropic employees abroad, effective immediately; other Anthropic models remain available. The order, received at 5:21 p.m. ET, cites a national‑security concern about a “jailbreak” method for Fable 5 but provides no specifics. Anthropic reviewed the reported technique, finding only minor, non‑universal vulnerabilities that also exist in publicly available models.
Key points from Anthropic’s response:
- Strong safeguards were built into Fable 5, tested for thousands of hours with U.S., U.K., and private red‑team partners, and deemed more effective than prior models.
- No universal jailbreak has been discovered; only narrow, low‑impact bypasses are known.
- A defense‑in‑depth strategy, including 30‑day data retention for monitoring, is in place.
- The cited jailbreak involved asking the model to analyze and fix a codebase—capabilities common to other frontier models.
- Anthropic argues that recalling the models over a narrow issue would set a precedent that could halt future model deployments and calls for a transparent, fact‑based statutory process.
Anthropic apologizes for the disruption and is working to restore access.
Read full article →
Community Discussion
Comments converge on the view that the U.S. export‑control action against Anthropic’s Fable 5 and Mythos 5 signals a broader shift toward governmental restriction of advanced language models, driven by national‑security concerns. Many see the move as likely to limit public and foreign access, prompting speculation about future KYC requirements, on‑premise deployments, and increased reliance on non‑U.S. alternatives such as Chinese or European offerings. While some criticize Anthropic’s hype and handling of safeguards, others doubt the models’ superiority and worry the decision will hinder AI innovation and market dynamics. Overall sentiment is cautious and skeptical about both the policy and the technology’s impact.
Open source AI must win
Summary
The piece argues that AI must remain open‑source to preserve operational freedom and prevent dependence on a limited set of closed institutions. It emphasizes that intelligence, as a civilizational infrastructure for work, education, science, creativity, public services, and national capacity, should be study‑able, build‑able, repairable, auditable, adaptable, teachable, preservable, and runnable without external permission. Open‑source AI is defined as usable, understandable, reproducible, locally deployable, economically viable, and community‑governed, resilient to changes or disappearance of dominant labs, hardware vendors, cloud platforms, or model providers. The text warns that concentration of control in a few frontier labs and platform companies could turn cognition into a subscription economy. It calls for American capacity aligned with global open standards to ensure freedom to run, inspect, modify, benchmark, teach, and preserve AI infrastructure.
Read full article →
Community Discussion
The comments converge on concern that a few AI megacorporations could dominate data, software, and infrastructure, prompting calls for open‑weight models and decentralized development. Contributors highlight technical and financial obstacles to large‑scale open training, note geopolitical pressures shaping access to chips and funding, and debate whether open‑source initiatives can match proprietary performance. Optimism persists that open models may eventually become competitive and democratize AI, yet skepticism remains about sustained investment, regulatory constraints, and the timeline for achieving parity with closed‑source systems.
EWlectric motors with no rare earths
Summary
Renault Group’s electric motor portfolio, branded as EESM, spans three generations without rare‑earth materials.
- First‑generation motors (part 5A) debuted in the Kangoo Z.E (2011) and Zoe (2012) with 57‑100 kW output; the final 5AL version powered the 2020 Twingo Electric at 60 kW.
- Second‑generation (part 6A) entered production in 2021; the 6AM motor equipped the Megane E‑Tech (early 2022) delivering up to 160 kW, later used in the 2024 Scenic E‑Tech and Alpine A290.
- Third‑generation launch began October 2024 with the Renault 5 E‑Tech (6AK motor, 110 kW) and Renault 4 E‑Tech (March 2025). The Alpine A390 (Sept 2025) adds a front‑axle 6AM motor plus a twin‑motor rear set, totalising roughly 345 kW (≈470 hp).
All motors are produced at Renault’s Cléon plant, with a next‑generation EESM line planned for 2027.
Read full article →
Community Discussion
Comments emphasize that magnet‑free wound‑field motors have a long history and avoid rare‑earth supply risks, offering efficiency advantages at moderate torques and high speeds, especially for trucks or auxiliary drives. Critics note the necessity of brushes, slip rings, or high‑frequency transformers, which add complexity, cooling challenges, and can limit power density and speed. Manufacturers such as Renault, BMW, Nissan and several European and Indian suppliers are actively developing the technology, yet its adoption remains limited in North America and China, prompting both optimism and caution about broader deployment.
CRISPR tech selectively shreds cancer cells, including "undruggable" cancers
Community Discussion
The comments express cautious optimism about recent cancer‑targeting advances, especially CRISPR‑based approaches, while emphasizing that delivery, resistance, and scalability remain major hurdles and that clinical use is likely years away. Several remarks note the limited number of approved CRISPR therapies compared with other viral‑vector treatments and criticize hype, patent constraints, and profit‑driven priorities that may slow progress. Participants also call for more data on tumor adaptation, faster regulatory pathways for life‑threatening cases, and broader public support for research.
Show HN: Putt.day a daily mini golf game
Summary
The page “putt.day” presents a daily mini‑golf feature. This entry, numbered 31, was published on June 12 2026 and introduces a single new hole for that day. The only visual element described is an image whose alt text reads “A floating mini golf course over water,” indicating that the depicted hole is set on a platform that appears to hover above a water surface, creating an aquatic‑themed mini‑golf experience. No additional text, rules, or commentary accompanies the entry. The content therefore consists of the series title, a brief description (“A daily hole of mini golf”), the specific episode identifier and date, and a single image caption describing the floating course.
Read full article →
Community Discussion
Overall the comments praise the game’s concept, graphics and entertaining shortcuts, but repeatedly point out issues with physics and controls, such as excessive rolling resistance, soft‑feel ball, bounce damping, camera angle problems, and difficulty dragging without panning. Performance concerns like lag and loading failures are also noted. Players find the par‑6 challenge unrealistic and request features like automatic camera positioning, multiplayer modes, and clearer visual cues. The consensus is that the game is enjoyable but needs refinements to feel polished.
Twenty One Zero-Days in FFmpeg
Summary
Depthfirst’s autonomous security agent analyzed FFmpeg’s ~1.5 M‑line codebase and produced 21 zero‑day bugs for roughly $1 k, a tenth of the cost reported by Anthropic’s Mythos scans. Eight findings received CVE‑2026‑39210 through ‑39217 and involve heap, stack, integer and underflow errors across components such as the TS demuxer, swscale, VP9 decoder, DASH demuxer and option parser. The remaining 13 issues, tracked internally as DFVULN‑127 to DFVULN‑119, affect RTP depacketizers (AV1, AV1 AV1, AV1 LATM, MPEG‑4, JPEG, etc.), AVIF overlay, CAF, AVI, RTSP/RTMP parsers, and the option map logic; all are heap or stack overflows or integer over/underflows, many dormant for 10‑23 years.
A highlighted exploit is a heap overflow in the AV1 RTP depacketizer (libavformat/rtpdec_av1.c). Skipping a Temporal‑Delimiter OBU advances the write cursor without allocating memory, allowing an attacker‑controlled 183‑byte RTP packet to overwrite the `AVBuffer.free` function pointer (offset 152) and trigger arbitrary code execution when the packet is freed. The vulnerability is reachable via a standard `ffmpeg -i rtsp://attacker/stream` command, requiring no special flags. All findings include reproducible proof‑of‑concept inputs confirming exploitability.
Read full article →
Community Discussion
The comments acknowledge ffmpeg’s long‑standing vulnerability history and emphasize the importance of sandboxing or isolation when processing untrusted media, noting that its complex C code makes complete safety difficult. Opinions vary on the immediacy of the disclosed flaws; some view them as serious risks for services handling attacker‑controlled streams, while others question the likelihood of remote code execution given modern mitigations. Praise for ffmpeg’s functionality coexists with criticism of exaggerated “zero‑day” terminology and skepticism toward LLM‑generated explanations. Overall, consensus leans toward cautious deployment and thorough security testing.
Swift at Apple: Migrating the TrueType hinting interpreter
Summary
Apple rewrote its TrueType hinting interpreter in Swift for the Fall 2025 releases, replacing a legacy C implementation. The new interpreter provides full memory safety, maintains binary compatibility and pixel‑identical rendering, and runs on average 13 % faster. Development relied on extensive testing: a unit‑test suite covering 99.7 % of code and a minimized corpus of 4,200 PDFs (27 M glyphs) fuzzed to verify bitmap output against the reference interpreter. Performance gains were achieved by eliminating ARC and exclusivity overhead through copyable value types, using Swift 6.2’s `Span` for efficient sequence access, and avoiding data copies via projection types that safely wrap C structures. Hot‑path optimizations included in‑place stack operations with continuation‑passing to remove heap allocations. The top‑level interface remains an `@objc` class for Objective‑C++ interoperability. The source code is released on GitHub as a production reference, and the project’s lessons have been codified for LLM‑assisted C/C++‑to‑Swift migrations.
Read full article →
Community Discussion
The comments convey a generally positive outlook on using a memory‑safe language for OS development, highlighting enthusiasm for Swift’s security and testing benefits and noting ongoing hiring for related roles. Simultaneously, there is noticeable frustration with current compiler instability, particularly around lifetime features, and skepticism about the breadth of adoption beyond specific components like the TrueType engine. Comparisons to Rust surface, questioning language choice, while concerns about UI hinting, performance expectations, and broader strategic priorities such as SwiftUI also appear.
How to setup a local coding agent on macOS
Summary
A local coding agent was built on macOS (Apple M1 Max, 64 GB) using llama.cpp compiled with Metal, the Gemma 4 26B‑A4B model in GGUF format, an Q8 MTP draft model for speculative decoding, and the Gemma 4 multimodal projector to enable image input. The baseline llama.cpp run delivered ~58 tokens/s; adding the MTP draft and tuning `--spec-draft-n-max` to 3 raised throughput to ~72 tokens/s (≈24 % gain) without slowing prompt processing. Benchmarks used a 128‑token Python‑diff task. llama.cpp outperformed MLX for this setup. The server is launched with `llama-server` specifying the main model, draft model, projector, speculative type `draft-mtp`, and context size 65536, exposing an OpenAI‑compatible endpoint at http://127.0.0.1:8080/v1. Pi (the terminal coding agent) is configured with a local provider pointing to this endpoint, supporting both text and image inputs. An alternative Qwen 3.6 35B‑A3B stack is provided; it offers better coding ability but slower performance (~55 tokens/s). The final stack includes the main GGUF model, MTP draft, projector, `--spec-draft-n-max 3`, and runs via tmux.
Read full article →
Community Discussion
The comments acknowledge the article’s useful details while highlighting several concerns and alternatives. Reviewers note that the 128‑token benchmark is too brief for reliable speed measurements and that early token acceptance may inflate perceived gains, recommending llama.cpp’s built‑in benchmark tool and the “‑hf” download flag. Various users share experiences with Ollama, omlx.ai, DeepSeek, and other models, noting mixed results on MTP acceleration, hardware limits, and quality trade‑offs. Overall sentiment is cautiously appreciative, emphasizing experimentation, better benchmarking practices, and a focus on answer quality over raw token throughput.
Why a Computer Science Degree Still Opens Hidden Doors
Summary
The article argues that a computer‑science (CS) degree remains a strong entry point despite recent headlines about AI‑driven job cuts. Federal Reserve data show 6.1 % unemployment for recent CS graduates (7.5 % for computer engineering), but when underemployment is included, engineers rank below a 20 % underemployment rate versus a 42 % average across all majors. “Entry‑level software engineer” postings rose ~47 % from late 2023 to late 2024 while actual hires fell ~73 %, creating “ghost jobs” that obscure real opportunities.
Practical advice includes:
- Leverage personal networks; ~26 % of offers come via referrals.
- Target startups where junior hires share risk and gain broad exposure.
- Create demonstrable experience (deployed projects, open‑source contributions) rather than relying on “toy” work.
- Acquire hands‑on AI engineering skills (RAG pipelines, embeddings, vector databases, multi‑agent systems) beyond tool fluency; AI‑related roles grew 163 % in 2025.
- Focus on durable systems‑thinking abilities, as demand for such engineers persists despite hiring fluctuations.
The piece also notes upcoming Big‑Tech layoffs linked to AI, a robotics‑policy shift restricting Chinese components, and related industry news.
Read full article →
Community Discussion
The comment presents a cautionary view of bypassing a formal degree, stressing that social capital and networking outweigh technical skill for career advancement in tech. It highlights higher unemployment rates among recent computer‑science graduates compared to other majors and warns that AI is increasingly displacing junior positions, creating long‑term risks for entry‑level engineers. The author recommends obtaining a degree—preferably from a well‑ranked program—or studying a mathematically rigorous field before pursuing a master’s, emphasizing that strong institutional credentials and existing connections remain crucial for success.
Malware developers added nuclear and biological weapons text to to their spyware
Summary
John Scott‑Railton reported that some malware authors have inserted references to nuclear and biological weapons into their spyware code. The purpose of these strings is to trigger safety refusals in large‑language‑model (LLM)–based security scanners, causing the tools to block analysis of the malicious payload. By prompting an LLM’s content‑filtering mechanisms, the attackers aim to evade detection and forensic examination. The tweet highlights this technique as a concrete example of how over‑reliance on first‑order safety checks can be exploited, emphasizing the need for more robust, context‑aware AI security solutions. The message includes a link to a source for further details.
Read full article →
Community Discussion
The comments express strong skepticism toward the perceived threat of large language models being used to develop nuclear or other weapons, arguing that necessary expertise and resources are already publicly accessible and that AI moderation acts as a denial‑of‑service mechanism rather than a genuine safety measure. They note that jailbreak techniques can bypass guardrails, suggest that automated scanners could flag suspicious code, and criticize current safety restrictions as obstructive, while acknowledging that malicious actors may still exploit AI‑assisted analysis tools. Overall, the tone is dismissive of extensive AI‑safety interventions.