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

推荐订阅源

Y
Y Combinator Blog
宝玉的分享
宝玉的分享
月光博客
月光博客
小众软件
小众软件
Jina AI
Jina AI
WordPress大学
WordPress大学
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
T
Tailwind CSS Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 【当耐特】
博客园 - 三生石上(FineUI控件)
博客园 - 司徒正美
大猫的无限游戏
大猫的无限游戏
The Cloudflare Blog
G
Google Developers Blog
M
MIT News - Artificial intelligence
N
Netflix TechBlog - Medium
云风的 BLOG
云风的 BLOG
MyScale Blog
MyScale Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
爱范儿
爱范儿
U
Unit 42
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
Blog — PlanetScale
Blog — PlanetScale

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 - 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
Show HN: FERNme – agent memory that updates with ~zero LL...
mirkofr · 2026-06-20 · via Hacker News - Newest: "LLM"

Hi HN, FERNme is a memory layer for AI agents. Most systems (Mem0, etc.) call an LLM on every turn to extract/summarize memory, or dump everything into a vector DB. I wanted to see how far a cheaper, more brain-like approach goes. Each user is a node in a fuzzy preference graph; edges (0–9, plus explicit negative edges for dislikes) update with a Hebbian co-occurrence rule — no LLM on the write path — decay ACT-R-style, and compile to a flat, ~40-token "memory card." Retrieval is spreading activation, not vector search. Some early results (all reproducible in the repo): ingesting 86 free-form diary entries about one person ran with 0 write-time LLM calls, kept a flat ~40-token card, and on a LoCoMo-style QA set the context-seeded retrieval answered ~4× more questions than frequency/recency baselines at equal budget — and was the only LLM-free method that handled preference drift. Honest about what this is not: the Hebbian + spreading-activation mechanism isn't novel — HippoRAG, Ori-Mnemos, and HeLa-Mem all use versions of it. My bet is on the combination: near-zero-cost writes, multi-tenant + a privacy-preserving population prior, user-owned cross-surface memory, and evaluating on actions rather than QA. Benchmarks so far are synthetic or single-person; a real LLM-memory (Mem0) head-to-head needs API keys and isn't run yet. It's MCP-compatible, and the repo has a paper draft (PAPER.md) plus a reproducible demo (demo/elena/ — builds memory from 86 free-form diary entries and runs the QA benchmark). Code: github.com/mirkofr/FERNme I'd love feedback on: the memory representation, whether the action-coupled eval is meaningful, failure modes you'd expect, and benchmarks/competitors I should test against — especially a real Mem0 head-to-head. Criticism very welcome.