frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Attention Media ≠ Social Networks

https://susam.net/attention-media-vs-social-networks.html
354•susam•6h ago•155 comments

Fix Your Tools

https://ochagavia.nl/blog/fix-your-tools/
78•vinhnx•2h ago•36 comments

Fresh File Explorer – VS Code extension for navigating recent work

https://github.com/FreHu/vscode-fresh-file-explorer
6•frehu•22m ago•2 comments

Show HN: 3D Mahjong, Built in CSS

https://voxjong.com
39•rofko•2h ago•22 comments

What Is a Database Transaction?

https://planetscale.com/blog/database-transactions
149•0x54MUR41•6h ago•24 comments

Xweather Live – Interactive global vector weather map

https://live.xweather.com/
65•unstyledcontent•3h ago•18 comments

We hid backdoors in ~40MB binaries and asked AI + Ghidra to find them

https://quesma.com/blog/introducing-binaryaudit/
140•jakozaur•3h ago•55 comments

Back to FreeBSD: Part 1

https://hypha.pub/back-to-freebsd-part-1
171•enz•11h ago•80 comments

Git's Magic Files

https://nesbitt.io/2026/02/05/git-magic-files.html
28•chmaynard•4h ago•8 comments

Man accidentally gains control of 7k robot vacuums

https://www.popsci.com/technology/robot-vacuum-army/
109•Brajeshwar•3h ago•62 comments

Monkey Patching in VBA

https://ecp-solutions.github.io/ASF/Language%20reference.html
25•n013•4d ago•3 comments

How Taalas “prints” LLM onto a chip?

https://www.anuragk.com/blog/posts/Taalas.html
333•beAroundHere•23h ago•199 comments

Gamedate – A site to revive dead multiplayer games

https://gamedate.org/
268•msuniverse2026•1d ago•38 comments

How far back in time can you understand English?

https://www.deadlanguagesociety.com/p/how-far-back-in-time-understand-english
694•spzb•4d ago•353 comments

Show HN: Llama 3.1 70B on a single RTX 3090 via NVMe-to-GPU bypassing the CPU

https://github.com/xaskasdf/ntransformer
337•xaskasdf•21h ago•88 comments

I Analyzed Every Nootropic Study on PubMed

https://outspeaker.com/post/217
14•paulpauper•1h ago•6 comments

How I use Claude Code: Separation of planning and execution

https://boristane.com/blog/how-i-use-claude-code/
803•vinhnx•18h ago•514 comments

Japanese Woodblock Print Search

https://ukiyo-e.org/
170•curmudgeon22•15h ago•26 comments

Iran students stage first large anti-government protests since deadly crackdown

https://www.bbc.com/news/articles/c5yj2kzkrj0o
227•tartoran•4h ago•279 comments

Two Bits Are Better Than One: making bloom filters 2x more accurate

https://floedb.ai/blog/two-bits-are-better-than-one-making-bloom-filters-2x-more-accurate
168•matheusalmeida•5d ago•24 comments

zclaw: personal AI assistant in under 888 KB, running on an ESP32

https://github.com/tnm/zclaw
241•tosh•1d ago•130 comments

ReferenceFinder: Find coordinates on a piece of paper with only folds

https://mutsuntsai.github.io/reference-finder/
53•icwtyjj•3d ago•7 comments

Claws are now a new layer on top of LLM agents

https://twitter.com/karpathy/status/2024987174077432126
375•Cyphase•1d ago•841 comments

Evidence of the bouba-kiki effect in naïve baby chicks

https://www.science.org/doi/10.1126/science.adq7188
179•suddenlybananas•20h ago•56 comments

Volatility: The volatile memory forensic extraction framework

https://github.com/volatilityfoundation/volatility3
29•transpute•5h ago•2 comments

The Four-Color Theorem 1852–1976

https://www.ams.org/journals/notices/202603/noti3305/noti3305.html
44•bikenaga•1d ago•5 comments

Parse, Don't Validate and Type-Driven Design in Rust

https://www.harudagondi.space/blog/parse-dont-validate-and-type-driven-design-in-rust/
236•todsacerdoti•23h ago•67 comments

Show HN: TLA+ Workbench skill for coding agents (compat. with Vercel skills CLI)

https://github.com/younes-io/agent-skills/tree/main/skills/tlaplus-workbench
16•youio•4h ago•2 comments

How I launched 3 consoles and found true love at Babbage's store no. 9 (2013)

https://arstechnica.com/gadgets/2013/01/how-i-launched-3-consoles-and-found-true-love-at-babbages...
57•zepearl•3d ago•21 comments

Unreal numbers

https://lcamtuf.substack.com/p/unreal-numbers
51•surprisetalk•5d ago•19 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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