frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

AWS Finally Built Its Own AWS Emulator

https://github.com/aws/aws-emulator
235•super_linear•1h ago•60 comments

Tim Peters has died

https://discuss.python.org/t/in-memoriam-tim-peters-1952-2026/110028
374•ayhanfuat•12h ago•40 comments

A false smoke alarm almost drowned Jane Street's only NYC datacenter

https://michael.bacarella.com/2026/11/10/false-smoke-alarm-jane-street-datacenter/
253•mbac32768•2h ago•130 comments

AWS Emulator and the engineer's job when agents write the code

https://www.allthingsdistributed.com/2026/11/aws-emulator-and-the-engineers-job-when-agents-write...
53•drbm•1h ago•3 comments

Show HN: I recreated Papers Please but you're deciding which YC startups to fund

https://termsheetplease.com/
22•bolau•23m ago•2 comments

Faster Retrieval for Better, More Efficient RAG

https://machinelearning.apple.com/research/faster-retrieval
75•zerop•2h ago•14 comments

Jensen Huang Must Resign

https://www.economist.com/leaders/2026/11/11/jensen-huang-must-resign
16•Anon84•25m ago•7 comments

Google SWE points 48 AI agents at NASA Lidar, finds unmapped Maya pyramid in 72h

https://pietromiotti.com/latest/maya-site/?maya
834•eyvindn•7h ago•306 comments

Hyper-Realistic Sand with WebGL2

https://av.github.io/safe-sand/
210•everlier•5h ago•49 comments

Show HN: Yogurt – Free, private, open-source alternative to Granola

https://github.com/FrigadeHQ/yogurt
78•brownrout•4h ago•37 comments

Retirement Savings Are Fueling the AI Bubble

https://lpeproject.org/blog/your-retirement-savings-are-fueling-the-ai-bubble/
7•speckx•28m ago•0 comments

Atuin Threads: All your agent sessions on every machine

https://blog.atuin.sh/threads-agent-sessions/
137•linsomniac•5h ago•55 comments

Can a Linear Program Do Weight-Space Programming?

https://nathan.rs/posts/weight-space-lp/
194•emschwartz•7h ago•29 comments

Launch HN: Pomerado (YC F26) – Turn any website into an MCP for agents

https://pomerado.ai/
24•alanjm23•2h ago•13 comments

Using voltage glitching to unleash the A100 in my mining card

https://blog.kate.land/posts/using-voltage-glitching-to-unlock-the-a100/
215•lae•8h ago•81 comments

Pharo in the Browser with WebAssembly

https://massimo-nocentini.github.io/pharo-vm/world.html
103•xkriva11•5h ago•29 comments

The tiny transmitter tracking monarch butterflies' migration, Canada to Mexico

https://www.begiant.ca/stories/places/monarch-butterflies-tracking-conservation
7•upofadown•1d ago•1 comments

We need more goat sacrifices

https://www.experimental-history.com/p/we-need-more-goat-sacrifices
144•iamnothere•7h ago•85 comments

Show HN: Godbolt-in-a-floating-window for Neovim (C, C++, Rust)

https://github.com/0xdeadf1sh/AssemblyForNeovim
81•0xdeadf1sh•6h ago•15 comments

The hardest notes to find on the guitar fretboard

https://www.gitori.com/blog/articles/hardest-notes-on-the-guitar-fretboard
32•udit99•3h ago•37 comments

Tinfoil (YC P25) is hiring an applied AI security engineer in San Francisco

1•FrasiertheLion•7h ago

AI, activity, and outcomes in software engineering

https://cabird.com/talks/shipping-faster/
69•azhenley•3h ago•81 comments

Show HN: Micron – Oberon with the Power of C

https://github.com/rochus-keller/Micron
26•Rochus•3d ago•8 comments

TimeNet: Open-source data infrastructure for Temporal Foundation Models

https://github.com/OpenTSLM/TimeNet
30•rjakob•1d ago•4 comments

The Computer Graphics Book of Knowledge

https://www.cs.cmu.edu/~ph/nyit/masson/history.htm
38•num42•3h ago•16 comments

I asked every TV manufacturer 17 questions about how they spy on you

https://www.theverge.com/tech/1012372/tv-privacy-acr-questions
294•Brajeshwar•5h ago•174 comments

The Power and Legacy of Virginia Tech's Mac-Based Supercomputers

https://512pixels.net/2026/11/va-tech-system-x-system-g/
12•CharlesW•2h ago•0 comments

Show HN: Klad, a paint app your coding agent can drive (source-available)

https://github.com/klad-app/klad
53•ambewas•3h ago•26 comments

Protecting SSH Keys with macOS Secure Enclave

https://gatezh.com/posts/macos-secure-enclave-ssh-keys/
363•js2•15h ago•131 comments

Attention to Mamba: A Recipe for Cross-Architecture Distillation

https://machinelearning.apple.com/research/attention-mamba-distillation
46•zerop•6h ago•3 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.