惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

S
Secure Thoughts
S
SegmentFault 最新的问题
云风的 BLOG
云风的 BLOG
T
Tailwind CSS Blog
博客园 - 聂微东
小众软件
小众软件
J
Java Code Geeks
MyScale Blog
MyScale Blog
人人都是产品经理
人人都是产品经理
量子位
GbyAI
GbyAI
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
M
MIT News - Artificial intelligence
Apple Machine Learning Research
Apple Machine Learning Research
有赞技术团队
有赞技术团队
月光博客
月光博客
B
Blog RSS Feed
D
DataBreaches.Net
酷 壳 – CoolShell
酷 壳 – CoolShell
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
D
Darknet – Hacking Tools, Hacker News & Cyber Security
Cyberwarzone
Cyberwarzone
I
Intezer
The Register - Security
The Register - Security
博客园 - 【当耐特】
博客园 - 司徒正美
L
Lohrmann on Cybersecurity
U
Unit 42
N
News and Events Feed by Topic
S
Security Affairs
V
Visual Studio Blog
Y
Y Combinator Blog
Security Latest
Security Latest
Know Your Adversary
Know Your Adversary
Google DeepMind News
Google DeepMind News
大猫的无限游戏
大猫的无限游戏
S
Schneier on Security
P
Privacy International News Feed
TaoSecurity Blog
TaoSecurity Blog
Spread Privacy
Spread Privacy
G
Google Developers Blog
NISL@THU
NISL@THU
Project Zero
Project Zero
P
Palo Alto Networks Blog
Help Net Security
Help Net Security
宝玉的分享
宝玉的分享
Stack Overflow Blog
Stack Overflow Blog
S
Security @ Cisco Blogs
G
GRAHAM CLULEY
www.infosecurity-magazine.com
www.infosecurity-magazine.com

Hacker News - Newest: "LLM"

GitHub - lechmazur/position_bias: A benchmark for testing whether LLM judges keep the same preference when two lightly edited versions of the same story are shown in opposite orders. Flex routing (EU and EFTA) Dark Factories: Retooling for LLM Velocity Ask HN: What would be the impact of a LLM output injection attack? GitHub - AronDaron/dataset-generator: No-code desktop app for generating high-quality synthetic datasets to fine-tune LLMs — plan-then-execute pipeline, LLM-as-judge, HuggingFace upload. GitHub - Oaklight/llm-rosetta: Production-ready LLM API translation layer for Python — bidirectional conversion between OpenAI, Anthropic & Google formats via hub-and-spoke IR. Optional API gateway. Streaming & non-streaming. Zero core deps. Contributions welcome! GitHub - browser-use/browser-harness: Self-healing browser harness that enables LLMs to complete any task. GitHub - moeen-mahmud/remen: Remen turns thoughts into something you can return to Analyzing 156 LLM Launch Posts on Hacker News ChatGPT vs Gemini vs Claude: The Best LLM Subscription You Should Buy GitHub - salaamalykum/quran-semantic-search: High-density RAG Semantic Search Engine & Quran Corpus (GEO/SEO Architecture) GitHub - NVIDIA/TensorRT-LLM: TensorRT LLM provides users with an easy-to-use Python API to define Large Language Models (LLMs) and supports state-of-the-art optimizations to perform inference efficiently on NVIDIA GPUs. TensorRT LLM also contains components to create Python and C++ runtimes that orchestrate the inference execution in a performant way. The State of LLM Bug Bounties in 2026 Operational Readiness Criteria for Tool-Using LLM Agents Meshcore: Architecture for a Decentralized P2P LLM Inference Network How an LLM becomes more coherent as we train it GitHub - seetrex-ai/laimark GitHub - Jossifresben/BibCrit: AI-assited biblical textual criticism GitHub - wastedcode/memex: File system based wiki, maintained by Claude 99helpers.com GitHub - cliver-project/AITrigram GitHub - unbody-io/adapt: A self-evolving memory layer for AI agents. GitHub - hb20007/awesome-gen-ai-fails: A list of incidents where reliance on generative AI and LLMs resulted in harm to companies, individuals, or society GitHub - nevenkordic/localmind: Run any local LLM with persistent memory and context. CLI agent over Ollama with SQLite-backed hybrid recall. No cloud. Ask HN: What are the machine requirements for a LLM like Llama-3.1-8B? Faster LLM Inference via Sequential Monte Carlo grpo explained: group relative policy optimization for llm finetuning - cgft Stop comparing price per million tokens: the hidden LLM API costs · TensorZero Andrej Karpathy's LLM Wiki Is a Bad Idea GitHub - GG-QandV/mnemostroma: Offline RAM-first cognitive leer/coprocessor for AI agents and robotics. Solves "Context Abandonment" with 20-80ms latency using a dual-thread biomimetic memory architecture (ONNX + SQLite WAL). mempalace/agent at agent · skorotkiewicz/mempalace GitHub - Nyquest-ai/nyquest-rust-fullstack-pub: Nyquest — Semantic Compression Proxy for LLMs. 350+ rules, local LLM stage, 15-75% token savings. Full Rust stack. GitHub - TheoV823/mneme: Enforce architectural decisions in AI-assisted development. GitHub - klemenvod/TokenBrawl: A 1v1 Bomberman-style game where two LLM agents play autonomously against each other. No human plays — you watch the AIs fight. Each agent receives a text description of the board state, reasons about it, and outputs a move as JSON. The game engine executes it. Introducing the Common AI Provider: LLM and AI Agent Support for Apache Airflow Power Circuit AI: Designing Power Electronic Circuits for Motor Drives with Generative Artificial Intelligence Ask HN: How to program with IDE and LLM on CPU locally? Show HN: Agent-cache – Multi-tier LLM/tool/session caching for Valkey and Redis Bonsai 1-bit WebGPU - a Hugging Face Space by webml-community The LLM Fallacy: Misattribution in AI-Assisted Cognitive Workflows Ask HN: Simple tooling for local LLM code critique without IDE integration? Can a General LLM Diagnose a DICOM Slice? A 10-Case Public Benchmark Charts-of-Thought: Enhancing LLM Visualization Literacy (PDF, 2026) GitHub - Mesh-LLM/mesh-llm: Distributed AI/LLM for the people. Share compute privately or publicly to power your agents and chat. GitHub - seamus-brady/springdrift: A persistent runtime for long-lived LLM agents Writing an LLM from scratch, part 32k -- Interventions: training a better model locally with gradient accumulation Ask HN: Which LLM model and agentic CLI are you using for local development? GitHub - wayneColt/modelcascade: Route local. Escalate smart. Never overspend. Open-source multi-model cascade routing for autonomous agents. LLM pricing is 100x harder than you think GitHub - asakin/llm-primer: Pre-warmed Claude Code sessions in tmux. No startup wait. GitHub - EggerMarc/chat-rs: A multi-provider LLM framework for Rust. GitHub - SynapseKit/SynapseKit: Minimal, async-first Python framework for production LLM apps- 2 hard deps, no magic, no SaaS. A Claude Skill that Makes LLM Paragraphs More Bearable Does Gas Town 'steal' usage from users' LLM credits & paid services to improve itself? What's Claude Code Actually Doing? Open the Black Box with the Arthur Engine Milla Jovovich's New Open Source LLM Memory App and the Dark Code Problem Your intuition of LLM token usage might be wrong Show HN: Bloomberg Terminal for LLM ops – free and open source GitHub - 0xchamin/mcptube: Transform YouTube videos into a compounding knowledge base with transcripts, vision analysis, and agentic search. Works as an MCP server for Claude, Copilot & more. Show HN: Open KB: Open LLM Knowledge Base Your LLM is a compiler, not a runtime GitHub - sapountzis/Unslop: A Web Feed That Deserves You crates.io: Rust Package Registry Beyond Karpathy's LLM-Wiki: The Necessity of Cognitive Governance GitHub - amitshekhariitbhu/llm-internals: Learn LLM internals step by step - from tokenization to attention to inference optimization. GitHub - parallem-ai/parallem: An expressive library for running agents with the Batch API. GitHub - stfurkan/pi-llm LLM-Wiki Show HN: Formal – Formal verification for AI-generated code using Lean 4 LRTS – Regression testing for LLM prompts (open source, local-first) LLM Wiki Skill: Build a Second Brain with Claude Code and Obsidian I built an LLM Wiki and RAG solution: here's a demo for a security KB The biggest advance in AI since the LLM Predict-Rlm: The LLM Runtime That Lets Models Write Their Own Control Flow the-synthetic-library/the-synthetic-mind at main · joshferrer1/the-synthetic-library GitHub - yisding/reviewwiggum GitHub - Donnyb369/mcp-spine: Context Minifier & State Guard — Local-first MCP middleware proxy GitHub - Beledarian/wgpu-llm: A from-scratch LLM inference engine that uses wgpu (the cross-platform WebGPU implementation) to dispatch WGSL compute shaders for every math operation a Transformer needs. No CUDA. No Python. No massive framework dependencies. Just Rust, raw shaders, and your GPU. GitHub - anitiue/Hindsight: An experience-driven self-improvement framework for LLM agents — 基于经验的 LLM Agent 自我改进框架 GitHub - stef41/lmscan: 🔍 Detect AI-generated text and fingerprint which LLM wrote it. Open-source GPTZero alternative. Zero dependencies, works offline. GitHub - alainnothere/AmdPerformanceTesting: Amd Performance Testing Ask HN: Is a purely Markdown-based CRM a terrible idea? Optimized for LLM agents Context Engineering - LLM Memory and Retrieval for AI Agents | Weaviate little_helper_tui/letter.md at main · sleepyeldrazi/little_helper_tui GitHub - EvanZhouDev/umr: The Unified Model Registry for all your local AI apps. GitHub - JordanCT/VigIA-Orchestrator Your Agent Is Mine: Measuring Malicious Intermediary Attacks on the LLM Supply Chain A Taxonomy of RL Environments for LLM Agents Llama LLM Network Feture GitHub - genedeng-ca/ai-mac-migration: AI-powered Mac-to-Mac migration tool - replace Apple Migration Assistant with intelligent, selective transfer using local LLMs GitHub - lunargate-ai/gateway: High-performance self-hosted AI gateway (OpenAI-compatible) with routing, retries, and streaming GitHub - AuthBits/webmcp: A lightweight, prompt-driven MCP web research server for high-quality LLM powered information extraction. Externalization in LLM Agents: A Unified Review of Memory, Skills, Protocols and Harness Engineering Springdrift: An Auditable Persistent Runtime for LLM Agents with Case-Based Memory, Normative Safety, and Ambient Self-Perception High-Stakes Personalization: Rethinking LLM Customization for Individual Investor Decision-Making From Static Templates to Dynamic Runtime Graphs: A Survey of Workflow Optimization for LLM Agents HUOZIIME: An On-Device LLM-enhanced Input Method for Deep Personalization TIDE: Token-Informed Depth Execution for Per-Token Early Exit in LLM Inference Characterizing WebGPU Dispatch Overhead for LLM Inference Across Four GPU Vendors, Three Backends, and Three Browsers LLM Targeted Underperformance Disproportionately Impacts Vulnerable Users
Four thoughts on Anthropic's Fable 5 kerfuffle
ProductMind · 2026-06-16 · via Hacker News - Newest: "LLM"

The reports point to Amazon being the source of the ‘tattling’ to the US Govt about potential malicious use of Fable 5. And then the US Govt asking for a specific unprecedented restriction on Mythos and Fable 5: “no access for any foreign national inside or outside the United States, including Anthropic’s own employees”. Swatting depends on a roided-out SWAT team to react peremptorily to a malicious phone call, sans careful investigation. And this is what it seems happened here - Amazon (Anthropic’s largest investor) sent a written report to the US govt, in which it posited dangerous use of Claude - something that needed careful evaluation on its merits.

If you’re experienced in technology and policy, you know the restriction requested from Anthropic can’t be administered at the level of national citizenship. So it’s all or nothing (Anthropic chose ‘all’, restricting it for everyone). We think it’s wrong to frame it as ‘Anthropic was recalcitrant’ as David Sacks did. Usually, the asker (the USG) should have the sophistication to understand the choices imposed by its request. No company can build the infrastructure to filter out non-US citizens’ access to globally deployed software platforms. Only the US government has done it at scale.

And then there is the matter of whether the ‘jailbreak’ was legitimate. Actual details are scant, even with Anthropic’s official statement and Axios’ reporting, and it comes down to trust: whether you trust the flawed but safety-minded AI company or the top tier of the Trump administration. The internet is unequivocal on that one.

This is an important moment in the history of the evolution of Artificial Intelligence. On the surface, LLMs have been driven by research labs for the last 5 years. Even though most of them are for-profit, it seems to have worked well; research papers flowed from Google, OpenAI, Anthropic, Meta, Microsoft, Qwen, DeepSeek, and more. But underneath what seems governed by commercial intent, nations have been jockeying and negotiating for what amounts to: ‘who gets to make the best AI and call the shots’. The US has advantages in energy density per capita, data-center build-out potential, capital flows, and intellectual property. It has explicitly blockaded the chip layer (temporary fix) but has not pulled the same for the model layer. Well, it did this week, in a shocking, ham-handed fashion. It cannot be overstated how important this moment is. The United States imperiously ordered that effectively EVERYONE in the world would not get a certain piece of software, which many depended on. No laws were passed, and very few deliberations were held. And it was publicly framed as adversarial to anyone not a United States citizen, even though the policy eventually caught up to citizens, too.

This reveals LLMs as geopolitical ordnance deployed by foreign powers in exclusionary ways against other nations and their citizens. I’m sure the Chinese are not surprised (they offer a different kind of AI diplomacy with their competent, famous, and cheap open-weight models). But the Europeans are likely very pained at this moment. Awkward.

We expect second and third-order consequences, including the following:

1. Public research on LLMs will continue to decline1.

2. Nations will hoard breakthroughs.

3. For-profit labs will yield more and more to the regulation of their nation-state cradles.

4. Some of the new ones will try to be stateless if they can manage it, and still secure venture or other funding.

It was imprudent for the US to tip its hand this early. Oh well. I think we will all regret it together.

In response to this model yank, we see a lot of speculation about local AI being the future of AI proliferation. The general story goes something like this: Moore’s law will make CPU chips do native inference on phones, laptops, and desktops up to a level beyond Mythos. In 5 to 10 years, everyone will have models running locally and problem-solved.

What this ignores is relative advantage and competition between nations and companies. Moore’s Law is actually a relentless upgrade cycle law. When new chips emerge, the most competitive productivity-minded companies HAVE to upgrade to keep up.

Does anyone remember IT departments handing out the beefiest laptops to developers every 2 years? Does anyone remember the big upgrade cycle driven by the emergence of the Apple M1 and M2 chips?

The best models will always run in the data center first, because the best and highest-performing chips always appear there first. It’s a lucrative and easy supply chain target, while phones, laptops, and PCs are incredibly slow to field upgrade.

Frontier models whose capabilities will outstrip your capable PC models will always come to you via API first, in a world economy built around relative performance. And in a world where AI supremacy is a relative acceleration race, local AI will be a second-tier productivity cushion, not the ceiling of performance. And if you think otherwise, you have not contemplated why Azure and AWS exist in the first place.

The future of LLMs is both local and datacenter. It’s not one or the other; it’s complementary. In the very same way, it’s already complementary today. To wit, most businesses use AWS and still issue powerful PCs to their employees. What is yet to emerge is the ‘cooperation layer’ that connects the two more seamlessly.

One more thing. This ham-handed episode is a prime example of an unforced error. The matter required more delicacy in handling than was exhibited by the Commerce Department and its secretary. This need not have become a domestic and international incident. It has all the hallmarks of an unsophisticated administrator trying to use insufficient evidence to boss a free-willed civilian business around. One that had tried its best to not only submit its IP to oversight but had put in guardrails to prevent circumvention2. It feels like a more consultative approach, looser deadlines, and more assistance would have finessed this last critical engagement. It’s hard not to chalk it up to the ineptness of the named players like Andy Jassy, Treasury Secretary Scott Bessent, and Commerce Secretary Howard Lutnick.

If it’s any comfort, you can be 100% sure Fable 5 will be back; after all, in a year, Mythos class models will be ordinary, even if neutered. But the world of AI will never be the same again.

Discussion about this post

Ready for more?