frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Olmo 3: Charting a path through the model flow to lead open-source AI

https://allenai.org/blog/olmo3
113•mseri•3h ago•24 comments

It's Hard to Build an Oscillator

https://lcamtuf.substack.com/p/its-hard-to-build-an-oscillator
42•chmaynard•2h ago•14 comments

Nano Banana Pro

https://blog.google/technology/ai/nano-banana-pro/
1056•meetpateltech•19h ago•605 comments

Android and iPhone users can now share files, starting with the Pixel 10

https://blog.google/products/android/quick-share-airdrop/
669•abraham•17h ago•380 comments

WebAssembly from the Ground Up

https://wasmgroundup.com/
106•gurjeet•5d ago•19 comments

FEX-emu – Run x86 applications on ARM64 Linux devices

https://fex-emu.com/
198•open-paren•1w ago•67 comments

Show HN: 32V TENS device from built from scratch under $100

https://littlemountainman.github.io/2025/11/17/tens/
17•autonomydriver•3d ago•5 comments

Apple's iPhone Overhaul Will Reduce Its Reliance on Annual Fall Spectacle

https://www.bloomberg.com/news/newsletters/2025-11-16/apple-s-iphone-road-map-iphone-air-2-iphone...
15•doener•3d ago•25 comments

Over-regulation is doubling the cost

https://rein.pk/over-regulation-is-doubling-the-cost
194•bilsbie•11h ago•337 comments

New OS aims to provide (some) compatibility with macOS

https://github.com/ravynsoft/ravynos
223•kasajian•13h ago•105 comments

Hilbert space: Treating functions as vectors

https://eli.thegreenplace.net/2025/hilbert-space-treating-functions-as-vectors/
61•signa11•1w ago•29 comments

Data-at-Rest Encryption in DuckDB

https://duckdb.org/2025/11/19/encryption-in-duckdb
174•chmaynard•14h ago•18 comments

NTSB Preliminary Report – UPS Boeing MD-11F Crash [pdf]

https://www.ntsb.gov/Documents/Prelimiary%20Report%20DCA26MA024.pdf
173•gregsadetsky•15h ago•184 comments

The Lions Operating System

https://lionsos.org
163•plunderer•15h ago•42 comments

Okta's NextJS-0auth troubles

https://joshua.hu/ai-slop-okta-nextjs-0auth-security-vulnerability
293•ramimac•2d ago•113 comments

New Glenn Update

https://www.blueorigin.com/news/new-glenn-upgraded-engines-subcooled-components-drive-enhanced-pe...
165•rbanffy•12h ago•94 comments

Free interactive tool that shows you how PCIe lanes work on motherboards

https://mobomaps.com
203•tagyro•2d ago•47 comments

Historical Reasons

https://exple.tive.org/blarg/2025/11/11/historical-reasons-2/
13•speckx•1w ago•3 comments

Scientists now know that bees can process time, a first in insects

https://www.cnn.com/2025/11/12/science/bees-visual-stimulus-study-scli-intl
7•Brajeshwar•5d ago•0 comments

CBP is monitoring US drivers and detaining those with suspicious travel patterns

https://apnews.com/article/immigration-border-patrol-surveillance-drivers-ice-trump-9f5d05469ce8c...
706•jjwiseman•14h ago•758 comments

Show HN: F32 – An Extremely Small ESP32 Board

https://github.com/PegorK/f32
242•pegor•1d ago•43 comments

Adversarial poetry as a universal single-turn jailbreak mechanism in LLMs

https://arxiv.org/abs/2511.15304
291•capgre•22h ago•152 comments

GitHut – Programming Languages and GitHub (2014)

https://githut.info/
73•tonyhb•12h ago•24 comments

Two recently found works of J.S. Bach presented in Leipzig [video]

https://www.youtube.com/watch?v=4hXzUGYIL9M#t=15m19s
146•Archelaos•3d ago•87 comments

Show HN: My hobby OS that runs Minecraft

https://astral-os.org/posts/2025/10/31/astral-minecraft.html
174•avaliosdev•3d ago•20 comments

Interactive World History Atlas Since 3000 BC

http://geacron.com/home-en/
320•not_knuth•1d ago•134 comments

Microsoft makes Zork open-source

https://opensource.microsoft.com/blog/2025/11/20/preserving-code-that-shaped-generations-zork-i-i...
561•tabletcorry•15h ago•214 comments

Launch HN: Poly (YC S22) – Cursor for Files

54•aabhay•16h ago•56 comments

Measuring Latency (2015)

https://bravenewgeek.com/everything-you-know-about-latency-is-wrong/
29•dempedempe•8h ago•10 comments

Ask HN: How are Markov chains so different from tiny LLMs?

168•JPLeRouzic•3d ago•131 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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