frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Things to know when you get cancer

https://jjmaxwell4.com/writing/things-to-know-when-you-get-cancer/
1384•jjmaxwell4•14h ago•345 comments

Wanted to download an ISO, ended up writing a kernel exploit

https://blog.dfb.sh/blog/eap770-root-for-two-zeros/
92•0xdeafbeef•1d ago•43 comments

OpenCode 2.0

https://anoma.ly/notes/opencode-2-0/
620•gmays•13h ago•244 comments

The cost of getting a job today

https://weli.dev/blog/the-cost-of-getting-a-job-today/
15•weli•1h ago•16 comments

Tiny Little Office

https://tinylittleoffice.com/
446•donohoe•12h ago•71 comments

Do dentists know what they're doing?

https://mapwriting.substack.com/p/dentists
710•doitLP•3d ago•512 comments

Show HN: Indigene – Native plants for where you stand

https://indigene.app/
27•olivierlacan•2d ago•5 comments

LFM2.5-24B-A2B: Built for fast on-device agents

https://www.liquid.ai/blog/lfm2-5-24b-a2b
213•gmays•10h ago•46 comments

The First Social Network: In rural Argentina residents send messages w AM radio

https://www.newyorker.com/magazine/2026/10/19/the-first-social-network
19•bookofjoe•1d ago•4 comments

Catch a Bird – I made it for my own sanity

https://catchabird.com
180•eduardsik•3d ago•48 comments

Americans' social activity has steeply declined in the past 30 years

https://www.dataforprogress.org/blog/2026/9/29/americans-social-activity-has-steeply-declined-in-...
408•hubraumhugo•18h ago•379 comments

AI was great until it was not

https://thetheorygirlie.substack.com/p/ai-was-great-until-it-was-not
56•JohnHammersley•1h ago•35 comments

Sticky alpine flower confirms Darwin's 150-year-old carnivorous plant prediction

https://phys.org/news/2026-08-sticky-alpine-darwin-year-carnivorous.html
30•maxall4•2d ago•12 comments

Donaldson Futuro House in Idyllwild, California, USA

https://www.wowhaus.co.uk/2026/10/12/donaldson-futuro-house-in-idyllwild-california-usa/
46•rmason•1d ago•16 comments

The Toftwood Male Voice Choir: A Mystery Pressed in Vinyl

https://ei3lh.eu/2026/10/11/the-toftwood-male-voice-choir-a-mystery-pressed-in-vinyl/
40•austinallegro•3d ago•3 comments

It took me nine years to hack my Xbox 360

https://kennedn.com/blog/posts/glitching/
82•kennedn•1d ago•22 comments

Better HTTP/1 connection reuse in Go 1.27

https://go.dev/blog/http-connection-reuse
256•allddd•17h ago•37 comments

Show HN: Flipflop, Iroh-powered persistent tunnels for filesharing

https://github.com/andunieee/flipflop
41•andunie•5h ago•12 comments

The Double Headed Stack Allocator

https://blog.demofox.org/2026/10/03/the-double-headed-stack-allocator/
66•g0xA52A2A•8h ago•20 comments

Bookofjoe's Favorite Thing: Best Pill Splitter

https://bookofjoe2.blogspot.com/2026/09/bookofjoes-favorite-thing-worlds-best.html
3•surprisetalk•1d ago•1 comments

Aidlc: Adaptive workflow steering rules for AI coding agents

https://github.com/awslabs/aidlc-workflows
8•pramodbiligiri•2h ago•8 comments

Your C is not standard C

https://sebsite.pw/w/20261012-notstdc.html
90•dverlaeckt80•1d ago•56 comments

David Rudnick on "borderline impossible" process of designing Arsenal typeface

https://www.itsnicethat.com/features/david-rudnick-johnnie-campbell-arsenal-rocastle-typeface-gra...
24•droidjj•2d ago•9 comments

Why is every rationalist blog post way too long?

https://alexwennerberg.com/blog/2026-10-13-long.html
360•epestr•1d ago•308 comments

How Amazon pushes up prices all across the Internet

https://www.not-ship.com/how-amazon-pushes-up-prices-all-across-the-internet/
838•sighborg•1d ago•644 comments

Show HN: Ito – Build Terminal UIs in Lua

https://uji.sh/ito/
21•cat-whisperer•11h ago•8 comments

Show HN: Petal, open-source CoScreen/ScreenHero finally free

https://petal.live/
169•thedracle•15h ago•38 comments

We’re releasing Jev 1.14.0 along with experimental features for dreamers

https://typesafe.ai/blog/jev-1-14
294•emschwartz•13h ago•92 comments

Containment and monitoring failures are to blame for AI hacking reports: experts

https://www.csoonline.com/article/4234854/ai-agents-arent-going-rogue-frontier-labs-are-skipping-...
902•latexr•16h ago•533 comments

Ask HN: CAD for wood working with LLM support?

77•reacharavindh•2d ago•70 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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