frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Commodore 64 released September 1, 1982

https://dfarq.homeip.net/commodore-64-released-september-1-1982/
84•giuliomagnifico•2h ago•15 comments

Claude Fable 5.1 and Claude Mythos 5.1

https://www.anthropic.com/claude-fable-and-mythos-5-1
1265•denysvitali•17h ago•1189 comments

The Emergent Symbolic Structure of Artificial Neural Networks

https://arxiv.org/abs/2608.29530
159•schmuhblaster•6h ago•54 comments

How accurate have Ed Zitron's AI skeptic predictions been?

https://danluu.com/zitron/
730•jatins•16h ago•797 comments

Fine, I'll build my own text editor

https://dbushell.com/2026/09/01/text-editor/
145•Alephinitesimal•17h ago•126 comments

FBI Probes Service Selling 153M+ Drivers Licenses

https://krebsonsecurity.com/2026/09/fbi-probes-service-selling-153m-drivers-licenses/
237•tatersolid•11h ago•101 comments

Introducing Ad Blocker for Firefox on iOS

https://blog.mozilla.org/en/firefox/ad-blocker-on-ios/
494•HieronymusBosch•21h ago•166 comments

WebFPGA (2019)

https://webfpga.io/
89•gurjeet•7h ago•32 comments

Open Battery Information

https://github.com/mnh-jansson/open-battery-information
11•toomuchtodo•3d ago•3 comments

Show HN: Weedout – Safari extension that hides YouTube AI-labeled videos

https://masteranza.github.io/weedout/
150•masteranza•12h ago•66 comments

Telli (YC F24) is hiring engineers and designers [Berlin, on-site]

https://careers.telli.com/
1•sebselassie•2h ago

Sonic Pi

https://sonic-pi.net/
176•Bluestein•4d ago•34 comments

My local model setup on an M4 Pro Mac Mini

https://lws.io/blog/my-local-model-setup/
218•raybb•12h ago•131 comments

The efficient frontier of LLM inference

https://www.baseten.co/blog/the-efficient-frontier-of-llm-inference/
127•philipkiely•11h ago•34 comments

Launch HN: Nori Robotics (YC S26) – A low-cost humanoid robot for development

https://www.norirobotics.com/
174•AntonioLi•17h ago•54 comments

Movie Scene Map – 13,312 films, series, games, anime and manga

https://moviescenemap.com/
263•Flightmussy•18h ago•38 comments

Ambient CSS v3 – Blender meets CSS

https://ambientcss.vercel.app/
279•kikkupico•19h ago•82 comments

The ChatGPT/Codex app bundles a full copy of LibreOffice

https://simonwillison.net/2026/Sep/1/codex-libreoffice/
422•timpera•14h ago•193 comments

Path to Astra: critical capabilities and frontier safeguards

https://openai.com/index/path-to-astra/
160•jithinraj•14h ago•73 comments

The creator of Jujutsu has joined ERSC

https://ersc.io/blog/martin-joins-ersc
243•steveklabnik•17h ago•180 comments

Refurbishing a Tektronix TDS7104 Oscilloscope

https://tomverbeure.github.io/2026/08/23/Tektronix-TDS7104-Refurbishing.html
130•jwise0•15h ago•55 comments

True Rate of Unemployment

https://www.lisep.org/tru
242•ptrhvns•8h ago•206 comments

Show HN: HN Match Maker – Matching "Who Wants to Be Hired?" With "Who's Hiring?"

https://hnmatchmaker.com/
94•all2•14h ago•40 comments

How bicycle coaster brakes work (2018)

https://www.dougbarnesauthor.com/2018/06/how-bicycle-coaster-brakes-work.html
69•Vedor•4d ago•55 comments

Ask HN: Who is hiring? (September 2026)

221•whoishiring•19h ago•245 comments

Show HN: Running 104GB Qwen3.8-Flash-Next on 48GB Mac with at ~12 tok/s

https://github.com/carloslfu/slotstream
215•carloslfu•18h ago•99 comments

Building an interactive instrument for a one-of-a-kind festival

https://benholmen.com/blog/halfmoon-chimes/
56•tjwds•4d ago•6 comments

Forgotten History of Small Nuclear Reactors (2015)

https://spectrum.ieee.org/the-forgotten-history-of-small-nuclear-reactors
42•derriz•4d ago•28 comments

Atlas: A World Model for Spatial Intelligence

https://www.worldlabs.ai/blog/atlas
227•johnsutor•17h ago•53 comments

Top Web Design Styles of 1993

https://contemporary-home-computing.org/prof-dr-style/
51•luu•1d ago•9 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.