frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Go Concurrency Distilled

https://antonz.org/go-concurrency-distilled/
101•chmaynard•14h ago•31 comments

PipePipe: NewPipe hard fork implementing SponsorBlock

https://github.com/InfinityLoop1308/PipePipe
354•Qision•1d ago•198 comments

DeepSeek Elastic Compute (DSec)

https://arxiv.org/abs/2609.22978
200•shenli3514•10h ago•59 comments

Show HN: Reladraw – A diagram language where you decide where to place things

https://github.com/reladraw/reladraw
228•jpwalsh234•11h ago•65 comments

Exploding variance of means of exponentials: least-squares to the rescue

https://francisbach.com/spectral_log_density_estimation/
10•matt_d•1d ago•0 comments

Evolving programming languages in the AI era

https://dashbit.co/blog/evolving-ai-era
59•pjm331•2d ago•37 comments

What is the size of Yemen? (2024)

https://theborys.substack.com/p/what-is-the-size-of-yemen
51•kspacewalk2•2h ago•8 comments

If we do not stop to help each other, what do we become?

https://blog.codinghorror.com/if-we-do-not-stop-to-help-each-other-what-do-we-become/
66•signa11•1h ago•13 comments

Does Georgism work? Five years later

https://www.astralcodexten.com/p/does-georgism-work-five-years-later
214•silveraxe93•1d ago•144 comments

Snap Wants to be a State Actor??–Kansas v. Snap

https://blog.ericgoldman.org/archives/2026/09/snap-wants-to-be-a-state-actor-kansas-v-snap.htm
35•hn_acker•1d ago•7 comments

Turning GLM-5.3-Flash into a Jev-like decision model

https://www.privatemode.ai/blog/system-one-from-glm-flash
64•flxflx•13h ago•26 comments

A searchable library of forgotten public-domain film clips from 1915 onward

https://www.movingimagearchive.com/
138•momentmaker•2d ago•26 comments

An agent used DNS to reach an external chatbot

https://alignment.openai.com/misalignment-reports/an-agent-used-dns-to-reach-an-external-chatbot/
49•apsec112•1d ago•57 comments

Reverse-engineering the Intel 8087's tangent algorithm: more than CORDIC

https://www.righto.com/2026/09/8087-tangent-cordic.html
51•pwg•11h ago•7 comments

Drawgent: Coding agent on a live Excalidraw canvas

https://tangled.org/yanndegat.tngl.sh/drawgent
131•parasitid•12h ago•35 comments

Fifteen years later, the Apple Cards origin story

https://lexontech.org/fifteen-years-later-the-apple-cards-origin-story
369•ksec•19h ago•93 comments

We Should Be Able to Change Our Languages

http://jimmyhmiller.com/change-our-languages
24•surprisetalk•1d ago•10 comments

Promising discoveries about the potential for life on one of Saturn’s icy moons

https://www.fu-berlin.de/en/presse/informationen/fup/2026/fup_26_116-enceladus-cassini-mikroben-s...
40•geox•1d ago•22 comments

ASML says it sold 'absolutely nothing' in Europe in 2026

https://www.tomshardware.com/tech-industry/semiconductors/asml-says-its-sells-absolutely-nothing-...
200•MC995•1d ago•511 comments

Biology might not be quantum, but its math is quantumlike

https://www.quantamagazine.org/biology-might-not-be-quantum-but-its-math-is-quantumlike-20260923/
40•pseudolus•2d ago•14 comments

OpenAI agents tried to bruteforce a UN website's API fields

https://swarmcha.se/posts/openai-unctad
11•intunderflow•3h ago•7 comments

Welcome to the Medical Clinic at the Interplanetary Relay Station

https://www.lightspeedmagazine.com/fiction/welcome-to-the-medical-clinic-at-the-interplanetary-re...
62•bucket2015•8h ago•10 comments

How I changed teaching after AI managed to do all my homework assignments

https://thelastsoftwareengineer.substack.com/p/how-i-changed-teaching-after-ai-managed
162•azhenley•2d ago•153 comments

The Evolution of Vending Machines

https://www.saturdayeveningpost.com/2026/09/from-holy-water-to-frozen-meals-the-evolution-of-vend...
27•ohjeez•11h ago•7 comments

LA Metro has some of the slowest escalators

https://basin.la/articles/ninety-feet-a-minute.html
94•big_toast•2d ago•74 comments

Modern Object Pascal Introduction for Programmers

https://castle-engine.io/modern_pascal
157•birdculture•2d ago•63 comments

Generate fonts where every LLM token is the same width

https://ampdot.mesh.host/token-space-fonts.html
42•z-mach9•1d ago•10 comments

How to keep enjoying programming in a world of LLMs

https://discourse.haskell.org/t/how-to-keep-enjoying-programming-in-a-world-of-llms/14705
179•signa11•19h ago•232 comments

Real-time feedback: My closing move in every interview

https://mgrebler.substack.com/p/real-time-feedback-my-closing-move
14•fagnerbrack•3h ago•4 comments

How one Twitch chat message became code execution on a streamer’s PC

https://blog.scrt.ch/2026/09/22/how-one-twitch-chat-message-became-code-execution-on-a-streamers-pc/
38•tau255•1d ago•23 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.