frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Many African families spend fortunes burying their dead

https://davidoks.blog/p/how-funerals-keep-africa-poor
87•powera•2h ago•60 comments

Native Instant Space Switching on macOS

https://arhan.sh/blog/native-instant-space-switching-on-macos/
272•PaulHoule•4h ago•131 comments

Charcuterie – Visual similarity Unicode explorer

https://charcuterie.elastiq.ch/
99•rickcarlino•4h ago•18 comments

How NASA Built Artemis II’s Fault-Tolerant Computer

https://cacm.acm.org/news/how-nasa-built-artemis-iis-fault-tolerant-computer/
32•speckx•9h ago•3 comments

PicoZ80 – Drop-In Z80 Replacement

https://eaw.app/picoz80/
131•rickcarlino•5h ago•21 comments

Reverse engineering Gemini's SynthID detection

https://github.com/aloshdenny/reverse-SynthID
98•_tk_•4h ago•42 comments

Robots Eat Cars

https://telemetry.endeff.com/p/robots-eat-cars
31•JMill•2d ago•14 comments

Instant 1.0, a backend for AI-coded apps

https://www.instantdb.com/essays/architecture
67•stopachka•6h ago•34 comments

Will I ever own a zettaflop?

https://geohot.github.io//blog/jekyll/update/2026/01/26/own-a-zettaflop.html
18•surprisetalk•3d ago•4 comments

Unfolder for Mac – A 3D model unfolding tool for creating papercraft

https://www.unfolder.app/
123•codazoda•7h ago•30 comments

Moving from WordPress to Jekyll (and static site generators in general)

https://www.demandsphere.com/blog/rebuilding-demandsphere-with-jekyll-and-claude-code/
28•rgrieselhuber•3h ago•11 comments

Research-Driven Agents: When an agent reads before it codes

https://blog.skypilot.co/research-driven-agents/
114•hopechong•7h ago•40 comments

Hegel, a universal property-based testing protocol and family of PBT libraries

https://hegel.dev
74•PaulHoule•5h ago•28 comments

BunnyCDN has been silently losing our production files for 15 months

https://old.reddit.com/r/webdev/comments/1sglytg/bunnycdn_has_been_silently_losing_our_production/
82•speckx•2h ago•14 comments

Top laptops to use with FreeBSD

https://freebsdfoundation.github.io/freebsd-laptop-testing/
272•fork-bomber•15h ago•152 comments

Old laptops in a colo as low cost servers

https://colaptop.pages.dev/
133•argentum47•6h ago•73 comments

Microsoft is employing dark patterns to goad users into paying for storage?

https://lzon.ca/posts/other/microsoft-user-abuse/
188•jpmitchell•3h ago•100 comments

Reallocating $100/Month Claude Code Spend to Zed and OpenRouter

https://braw.dev/blog/2026-04-06-reallocating-100-month-claude-spend/
287•kisamoto•15h ago•194 comments

Show HN: I built a Cargo-like build tool for C/C++

https://github.com/randerson112/craft
114•randerson_112•8h ago•105 comments

How the Trivy supply chain attack harvested credentials from secrets managers

https://vaultproof.dev/blog/trivy-supply-chain-attack
10•Rial_Labs•2h ago•2 comments

Introduction to Nintendo DS Programming

https://www.patater.com/files/projects/manual/manual.html
211•medbar•1d ago•44 comments

EFF is leaving X

https://www.eff.org/deeplinks/2026/04/eff-leaving-x
1065•gregsadetsky•7h ago•890 comments

The Training Example Lie Bracket

https://pbement.com/posts/lie_brackets/
9•pb1729•2h ago•3 comments

Show HN: Druids – Build your own software factory

https://github.com/fulcrumresearch/druids
20•etherio•1d ago•1 comments

A WebGPU implementation of Augmented Vertex Block Descent

https://github.com/jure/webphysics
119•juretriglav•12h ago•15 comments

Wit, unker, Git: The lost medieval pronouns of English intimacy

https://www.bbc.com/future/article/20260408-the-extinct-english-words-for-just-the-two-of-us
180•eigenspace•14h ago•114 comments

Progressive encoding and decoding of 'repeated' protobuffer fields

https://schilk.co/blog/protobuffer-repeat-append/
11•quarkz02•4d ago•1 comments

Maine is about to become the first state to ban major new data centers

https://www.gadgetreview.com/maine-is-about-to-become-the-first-state-to-ban-major-new-data-centers
238•rmason•4h ago•338 comments

LittleSnitch for Linux

https://obdev.at/products/littlesnitch-linux/index.html
1261•pluc•1d ago•413 comments

Help Keep Thunderbird Alive

https://updates.thunderbird.net/en-US/thunderbird/140.0/apr26-1e/donate/
507•playfultones•17h ago•343 comments
Open in hackernews

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

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

Comments

MacsHeadroom•11mo 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•10mo 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•11mo 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•11mo ago
do you have references to

> TTT, cannon layers, and titans

najarvg•11mo 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•11mo ago
is titans replicated? I feel like lucidrains couldn't replicate.
logicchains•11mo 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•11mo 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•11mo 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•11mo 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•11mo 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.