frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Livenerf: Has Opus 5.5 been nerfed yet?

https://github.com/ninjahawk/livenerf
399•bryan0•6h ago•159 comments

LinkedIn Larpmaxxing

https://hereticpleb.vercel.app/blog/linkedin-larpmaxxing/
17•BurnerBurner•59m ago•11 comments

PSSA: A non-transformer language model written from scratch in Rust

https://github.com/Sparticle62ops/pssa
39•sparticle62•1h ago•11 comments

Dots: Always-on agents

https://openai.com/index/introducing-dots/
517•alvis•12h ago•392 comments

U.S. postal inspectors shut down website selling counterfeit postage labels

https://postalemployeenetwork.com/news/2026/09/26/u-s-postal-inspectors-shut-down-website-selling...
199•ilamont•9h ago•118 comments

Vermont replacing power plants with home batteries

https://www.bbc.com/future/article/20260928-a-virtual-power-plant-hidden-in-vermont-homes-is-keep...
134•devonnull•11h ago•113 comments

Responsible Release of AI-Generated Mathematics

https://agmai.org/general-sep29/
14•aureianimus•2h ago•2 comments

NASA asked several former SR-71A staffers to help secret restart

https://aviationweek.com/defense/aircraft-propulsion/nasa-asked-several-former-sr-71a-staffers-he...
94•ilamont•19h ago•93 comments

America.gov

https://america.gov/
475•plesiv•15h ago•379 comments

Show HN: Real-time Solar System with 526k asteroids and all tracked satellites

https://space.bl2.net/
172•wanick•10h ago•39 comments

GPT 6.1 Sol: Near-Astra intelligence for a fifth of the price

https://openai.com/index/introducing-gpt-6-1-sol/
849•crorella•12h ago•774 comments

How Delhi cut electricity loss from 50 to 5 percent

https://spectrum.ieee.org/delhi-electricity-loss
474•rbanffy•16h ago•274 comments

PS5 Relapse Exploit

https://github.com/ntfargo/Relapse-Exploit
267•therepanic•13h ago•149 comments

Language models for text classification: From bag-of-words to Jev

https://magazine.sebastianraschka.com/p/classifier-history-and-jev
65•Anon84•18h ago•2 comments

Backblaze drive stats for Q2 2026

https://www.backblaze.com/blog/backblaze-drive-stats-for-q2-2026/
129•HieronymusBosch•15h ago•30 comments

Needed 1+1, built a functional programming language

https://hereticpleb.vercel.app/blog/needed-one-plus-one/
60•birdculture•13h ago•16 comments

Phyllotaxis: An audio-reactive LED display

https://jagi.studio/posts/phyllotaxis/
271•evakhoury•1d ago•45 comments

When oil prices spike, where does the money go?

https://theconversation.com/when-oil-prices-spike-where-does-the-money-go-280763
52•thelastgallon•1d ago•46 comments

We’re forgetting what darkness feels like

https://www.theguardian.com/environment/2026/sep/29/night-sky-darkness-city-regulation
111•pseudolus•10h ago•66 comments

NAND-16: a computer built from 277,248 NAND gates

https://somethingbig.ai/computer
119•rossant•2d ago•68 comments

Tesla takes on $30B in credit as it approaches unprofitability

https://electrek.co/2026/09/29/tesla-takes-on-30-billion-in-credit-as-it-approaches-unprofitability/
9•ciconia•42m ago•1 comments

RSS Feeds for Last.fm

https://lfm.xiffy.nl/
12•Baljhin•2h ago•3 comments

Testing WebGPU data layouts with Facet

https://www.mattkeeter.com/blog/2026-08-23-wgpu-facet/
3•luu•1d ago•0 comments

Ask HN: What are you reading?

202•dan-bailey•15h ago•457 comments

A Staff Engineer's Guide to Inventing Work

https://sujithjay.com/inventing-work
228•amortize•1d ago•45 comments

Deser: Rethinking Rust Serialization

https://lucumr.pocoo.org/2026/9/29/deser/
49•tosh•7h ago•6 comments

Show HN: A working 3D model of an Enigma machine

https://enigma.design
51•primitivesuave•12h ago•18 comments

Ballmer Peak

https://en.wikipedia.org/wiki/Ballmer_Peak
23•thunderbong•2h ago•0 comments

Show HN: NSL – WSL for Linux

https://frostyard.github.io/nsl/
106•bketelsen•14h ago•73 comments

Strange Parodies of Atari 2600 Video Game Box Cover Art (2008)

https://mightygodking.com/2008/04/21/fun-from-yesterday/
24•peter_d_sherman•3h ago•17 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.