frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Rack-mount hydroponics

https://sa.lj.am/rack-mount-hydroponics/
92•cdrnsf•3h ago•20 comments

Treasure hunter freed from jail after refusing to turn over shipwreck gold

https://www.bbc.com/news/articles/cg4g7kn99q3o
61•tartoran•4h ago•62 comments

Why Mathematica does not simplify sinh(arccosh(x))

https://www.johndcook.com/blog/2026/03/10/sinh-arccosh/
15•ibobev•3d ago•0 comments

How kernel anti-cheats work

https://s4dbrd.github.io/posts/how-kernel-anti-cheats-work/
124•davikr•7h ago•94 comments

A most elegant TCP hole punching algorithm

https://robertsdotpm.github.io/cryptography/tcp_hole_punching.html
45•Uptrenda•3h ago•7 comments

Show HN: Han – A Korean programming language written in Rust

https://github.com/xodn348/han
153•xodn348•9h ago•89 comments

Mathematics Distillation Challenge – Equational Theories

https://terrytao.wordpress.com/2026/03/13/mathematics-distillation-challenge-equational-theories/
58•picafrost•21h ago•2 comments

Ageless Linux – Software for humans of indeterminate age

https://agelesslinux.org/
535•nateb2022•9h ago•349 comments

Allow me to get to know you, mistakes and all

https://sebi.io/posts/2026-03-14-allow-me-to-get-to-know-you-mistakes-and-all/
104•sebi_io•9h ago•33 comments

Tree Search Distillation for Language Models Using PPO

https://ayushtambde.com/blog/tree-search-distillation-for-language-models-using-ppo/
51•at2005•6h ago•3 comments

SBCL Fibers – Lightweight Cooperative Threads

https://atgreen.github.io/repl-yell/posts/sbcl-fibers/
74•anonzzzies•8h ago•13 comments

Bumblebee queens breathe underwater to survive drowning

https://www.smithsonianmag.com/science-nature/bumblebee-queens-breathe-underwater-to-survive-drow...
105•1659447091•10h ago•25 comments

A look inside Dialector, filmmaker Chris Marker's chatbot from 1988

https://kubicki.org/letters/the-festival-of-the-machines/
31•kosmavision•3d ago•2 comments

Launching the Claude Partner Network

https://www.anthropic.com/news/claude-partner-network
129•gmays•10h ago•58 comments

How Jeff Bezos Upended The Washington Post

https://www.nytimes.com/2026/03/14/business/media/washington-post-jeff-bezos-layoffs.html
33•y1n0•1h ago•14 comments

An unappetizing shrub became different vegetables

https://www.worksinprogress.news/p/many-of-the-tastiest-vegetables-are
21•bensouthwood•3d ago•16 comments

MCP is dead; long live MCP

https://chrlschn.dev/blog/2026/03/mcp-is-dead-long-live-mcp/
112•CharlieDigital•11h ago•116 comments

Fedora 44 on the Raspberry Pi 5

https://nullr0ute.com/2026/03/fedora-44-on-the-raspberry-pi-5/
86•jandeboevrie•11h ago•22 comments

Airbus is preparing two uncrewed combat aircraft

https://www.airbus.com/en/newsroom/press-releases/2026-03-airbus-is-preparing-two-uncrewed-combat...
121•phasnox•8h ago•68 comments

Marketing for Founders

https://github.com/EdoStra/Marketing-for-Founders
155•jimsojim•11h ago•61 comments

Library of Short Stories

https://www.libraryofshortstories.com/
69•debo_•11h ago•3 comments

An ode to bzip

https://purplesyringa.moe/blog/an-ode-to-bzip/
119•signa11•15h ago•68 comments

A Recursive Algorithm to Render Signed Distance Fields

https://pointersgonewild.com/2026-03-06-a-recursive-algorithm-to-render-signed-distance-fields/
79•surprisetalk•3d ago•5 comments

Baochip-1x: What it is, why I'm doing it now and how it came about

https://www.crowdsupply.com/baochip/dabao/updates/what-it-is-why-im-doing-it-now-and-how-it-came-...
300•timhh•3d ago•67 comments

The Enterprise Context Layer

https://andychen32.substack.com/p/the-enterprise-context-layer
45•zachperkel•4d ago•8 comments

Hostile Volume – A game about adjusting volume with intentionally bad UI

https://hostilevolume.com/
85•Velocifyer•12h ago•56 comments

Show HN: GrobPaint: Somewhere Between MS Paint and Paint.net

https://github.com/groverburger/grobpaint
38•__grob•8h ago•5 comments

Postgres with Builtin File Systems

https://db9.ai/
59•ngaut•10h ago•14 comments

Python: The Optimization Ladder

https://cemrehancavdar.com/2026/03/10/optimization-ladder/
307•Twirrim•4d ago•110 comments

Show HN: Ichinichi – One note per day, E2E encrypted, local-first

98•katspaugh•12h ago•38 comments
Open in hackernews

EM-LLM: Human-Inspired Episodic Memory for Infinite Context LLMs

https://github.com/em-llm/EM-LLM-model
113•jbotz•10mo ago

Comments

MacsHeadroom•10mo ago
So, infinite context length by making it compute bound instead of memory bound. Curious how much longer this takes to run and when it makes sense to use vs RAG.
zfountas•9mo ago
Hi MacsHeadroom, first author here. Thanks for the great questions about compute/memory trade-offs.

The quick take: To give you an example of processing speed, with a 7B model on an NVIDIA V100, EM-LLM processes (or generates) about 326 tokens/sec with a 51.2K context window (which is quite competitive for these old GPUs).

More broadly, EM-LLM is designed to make ultra-long contexts (memory-prohibitive for standard O(n^2) attention) computationally tractable. The Appendix C of our paper https://openreview.net/pdf?id=BI2int5SAC details how: significantly better attention scaling, efficient O(nm) memory formation, and large KV cache management via CPU/disk offloading. While there's a slight per-chunk overhead compared to the simplest retrieval methods initially, the crucial part is our ability to handle sequences at scales infeasible for full-context models. For instance, we're successfully using 8B models with 10M token contexts on a single GPU without prohibitive delays.

Regarding RAG in particular, EM-LLM often shows significant gains on tasks needing deep understanding of a single, long, coherent context. A key reason is that EM-LLM allows each layer to retrieve and integrate relevant information from different "episodes" of the context independently, offering more nuance than a typical single RAG step, for similar overall resource use.

mountainriver•10mo ago
TTT, cannon layers, and titans seem like a stronger approach IMO.

Information needs to be compressed into latent space or it becomes computationally intractable

searchguy•10mo ago
do you have references to

> TTT, cannon layers, and titans

najarvg•10mo ago
This was the nearest reference I could find. Links to an unofficial pytorch implementation on Github are also linked in the threads somewhere - https://www.reddit.com/r/LocalLLaMA/comments/1i0q8nw/titans_...
vessenes•10mo ago
is titans replicated? I feel like lucidrains couldn't replicate.
logicchains•10mo ago
I think something like Titans explains Gemini's excellent long context performance. That would explain why the Titan team hasn't released the training code or hyperpameters used even though they said in the paper that they would, and why soon after that it came out that DeepMind would be holding off publishing new results for 6 months to avoid giving away competitive advantages.
p_v_doom•10mo ago
Interesting. Before there even was attention I was thinking that the episodic memory model offers something that could be very useful for neural nets, so its cool to see people testing that
killerstorm•10mo ago
Note that this works within a single sequence of tokens. It might be consistent with "episodic memory" metaphor if we consider a particular transformer run as its experience.

But this might be very different from what people expect from "memory" - i.e. ability to learn vast amounts of information and retrieve it as necessary.

This is more like a refinement of transformer attention: instead of running attention over all tokens (which is very expensive as it's quadratic), it selects a subset of token spans and runs fine-grained attention only on those. So it essentially breaks transformer attention into two parts - coarse-grained (k-NN over token spans) and fine-grained (normal).

It might be a great thing for long-context situations. But it doesn't make sense when you want millions of different facts to be considered - making them into long context is rather inefficient.

yorwba•10mo ago
It would be inefficient if you had to do it from scratch for every query, but if you can do it once as a preprocessing step and reuse the prepared context for many queries, it might start to become more efficient than a shorter context that includes only some documents but has to be reprocessed because it's different every time.
killerstorm•10mo ago
Yes, I think it might be a good solution where you have a context up to 10M of tokens and you do a lot of requests with that context. It might be relevant for agentic stuff which tends to produce long chat logs - especially with some gadgets on top, e.g. some 'episodes' might be completely removed as obsolete.

But I don't think it's a good solution for bigger amounts of data - as in that case it's more beneficial if that can be formed into independent memories.