frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Immersa: Open-source Web-based 3D Presentation Tool

https://github.com/ertugrulcetin/immersa
36•simonpure•1h ago•8 comments

Gemini 3 Pro vs. 2.5 Pro in Pokemon Crystal

https://blog.jcz.dev/gemini-3-pro-vs-25-pro-in-pokemon-crystal
25•alphabetting•4d ago•0 comments

NTP at NIST Boulder Has Lost Power

https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/ACADD3NKOG2QRWZ56OSNNG7UIEKKT...
247•lpage•7h ago•120 comments

What Does a Database for SSDs Look Like?

https://brooker.co.za/blog/2025/12/15/database-for-ssd.html
83•charleshn•5h ago•59 comments

Skills Officially Comes to Codex

https://developers.openai.com/codex/skills/
109•rochansinha•7h ago•56 comments

CSS Grid Lanes

https://webkit.org/blog/17660/introducing-css-grid-lanes/
618•frizlab•17h ago•179 comments

Charles Proxy

https://www.charlesproxy.com/
223•handfuloflight•9h ago•78 comments

Privacy doesn't mean anything anymore, anonymity does

https://servury.com/blog/privacy-is-marketing-anonymity-is-architecture/
182•ybceo•8h ago•126 comments

Arduino UNO Q bridges high-performance computing with real-time control

https://www.arduino.cc/product-uno-q/
14•doener•3d ago•4 comments

Mistral OCR 3

https://mistral.ai/news/mistral-ocr-3
602•pember•2d ago•108 comments

Reflections on AI at the End of 2025

https://antirez.com/news/157
79•danielfalbo•5h ago•100 comments

Raycaster (YC F24) Is Hiring a Research Engineer (NYC, In-Person)

1•levilian•3h ago

A terminal emulator that runs in your terminal. Powered by Turbo Vision

https://github.com/magiblot/tvterm
85•mariuz•3d ago•10 comments

New Quantum Antenna Reveals a Hidden Terahertz World

https://www.sciencedaily.com/releases/2025/12/251213032617.htm
67•aacker•4d ago•2 comments

A train-sized tunnel is now carrying electricity under South London

https://www.ianvisits.co.uk/articles/a-train-sized-tunnel-is-now-carrying-electricity-under-south...
60•zeristor•6h ago•58 comments

Garage – An S3 object store so reliable you can run it outside datacenters

https://garagehq.deuxfleurs.fr/
629•ibobev•23h ago•137 comments

Airbus to migrate critical apps to a sovereign Euro cloud

https://www.theregister.com/2025/12/19/airbus_sovereign_cloud/
291•saubeidl•6h ago•213 comments

TailwindSQL – Like TailwindCSS, but for SQL Queries in React Server Components

https://github.com/mmarinovic/tailwindsql
4•ravenical•1h ago•0 comments

A proof of concept of a semistable C++ vector container

https://github.com/joaquintides/semistable_vector
14•joaquintides•4d ago•2 comments

Contrails Map

https://map.contrails.org/
82•schaum•7h ago•34 comments

Hash tables in Go and advantage of self-hosted compilers

https://rushter.com/blog/go-and-hashmaps/
30•f311a•5d ago•17 comments

NOAA deploys new generation of AI-driven global weather models

https://www.noaa.gov/news-release/noaa-deploys-new-generation-of-ai-driven-global-weather-models
117•hnburnsy•2d ago•79 comments

Fuzix on a Raspberry Pi Pico

https://ewpratten.com/blog/fuzix-pi-pico
87•ewpratten•5d ago•6 comments

TP-Link Tapo C200: Hardcoded Keys, Buffer Overflows and Privacy

https://www.evilsocket.net/2025/12/18/TP-Link-Tapo-C200-Hardcoded-Keys-Buffer-Overflows-and-Priva...
313•sibellavia•20h ago•94 comments

8-bit Boléro

https://linusakesson.net/music/bolero/index.php
290•Aissen•1d ago•41 comments

LLM Year in Review

https://karpathy.bearblog.dev/year-in-review-2025/
276•swyx•18h ago•94 comments

Graphite is joining Cursor

https://cursor.com/blog/graphite
245•fosterfriends•23h ago•242 comments

Sharp: High performance Node.js image processing/optimization

https://github.com/lovell/sharp
29•nateb2022•3d ago•3 comments

A better zip bomb (2019)

https://www.bamsoftware.com/hacks/zipbomb/
158•kekqqq•17h ago•54 comments

Carolina Cloud – One third the cost of AWS for data science workloads

https://carolinacloud.io/
130•bojangleslover•5d ago•69 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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