frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Longest Straight Line Paths on Water or Land on the Earth (2018)

https://arxiv.org/abs/1804.07389
52•joebig•2h ago•12 comments

Arbitrary code execution in QubesOS via copy-to-VM error reporting backchannel

https://www.qubes-os.org/news/2026/08/29/qsb-118/
28•vntok•1h ago•7 comments

Spark: Sparklines in your shell

https://git.zx2c4.com/spark/about/
7•hskimse•36m ago•0 comments

Brits would quite like their private messages to stay private

https://www.theregister.com/security/2026/08/30/turns-out-brits-would-quite-like-their-private-me...
59•defrost•1h ago•23 comments

Everyone Should Build Their Own Network Stack

https://blog.lyc8503.net/en/post/dn42-2-dnet/
5•uneven9434•46m ago•0 comments

RISC-V is now officially supported by CPython

https://blog.python.org/2026/08/riscv-now-officially-supported/
175•lumpa•5d ago•36 comments

Xcena and Samsung's Near Memory Compute CXL Device

https://chipsandcheese.com/p/hot-chips-2026-xcena-and-samsungs
14•klelatti•3h ago•1 comments

Hy4 preview

https://www.tencent.com/tencent-releases-and-open-sources-tencent-hy4-preview/
306•shenli3514•15h ago•190 comments

FreeCORE TrueNAS Core – Continued

https://freecore.org/
102•sashk•9h ago•58 comments

Bug Blindness

https://danluu.com/bug-blind/
267•davidmckenna•10h ago•157 comments

California lawmakers unanimously pass Linux exemption from age-verification law

https://www.tomshardware.com/software/linux/california-lawmakers-unanimously-pass-linux-exemption...
307•shscs911•7h ago•133 comments

The Einstein-Szilard Refrigerator

https://invention.si.edu/invention-stories/einstein-szilard-refrigerator
33•EndXA•3d ago•5 comments

Tether: iMessage, SMS, etc. on Linux

https://zackbartel.com/blog/2026/08/tether/
466•zackb•6d ago•183 comments

Benjamin Franklin's Alter Egos Gave Him the Most Freedom

https://www.smithsonianmag.com/history/among-all-great-things-benjamin-franklin-invented-discover...
70•cisc•9h ago•28 comments

Nancy Grace Roman Space Telescope

https://science.nasa.gov/mission/roman-space-telescope/
200•JumpCrisscross•18h ago•80 comments

JupyterGIS 0.16: a grammar of graphics for maps, and collaborative story maps

https://blog.jupyter.org/jupytergis-0-16-new-visualization-capabilities-collaborative-story-maps-...
22•arjxn-py•5d ago•3 comments

Benchmarking Pocket-Scale Inference

https://artificialanalysis.ai/hardware-inference-stack/mobile-phones
47•sys42590•2d ago•4 comments

Creating Teensy ELF Executables for Linux (Or, "Size Is Everything") (1999)

https://www.muppetlabs.com/~breadbox/software/tiny/teensy.html
48•Bluestein•4d ago•11 comments

SQLite as a Document Database (2020)

https://dgl.cx/2020/06/sqlite-json-support
214•lioeters•5d ago•51 comments

Lawmakers added $1 to car insurance policies. That money paid for Flock cameras

https://www.texastribune.org/2026/08/28/texas-flock-cameras-auto-insurance-fee-mvcpa-grants/
310•DeepLogin•11h ago•172 comments

EVE Online moves to Python 3

https://www.eveonline.com/news/view/the-move-to-python-3-begins
363•TylerJaacks•4d ago•197 comments

Functional State Machines in Rust: Typestate and Newtype Patterns

https://dl.acm.org/doi/10.1145/3830438.3830958
91•matt_d•15h ago•36 comments

Nvidia's AI advantage is moving beyond the GPU

https://techcrunch.com/2026/08/29/nvidias-ai-advantage-is-moving-beyond-the-gpu/
6•01-_-•41m ago•2 comments

Glacier Mice

https://en.wikipedia.org/wiki/Glacier_mice
304•ostacke•5d ago•59 comments

Calibrate Before You Accelerate: Bias Toward Action in a New Role

https://tucker.wales/writing/bias-towards-action/
162•tuckerwales•16h ago•66 comments

Open Oscar Server: open-source server compatible with AIM and ICQ clients

https://github.com/mk6i/open-oscar-server
41•gregsadetsky•10h ago•13 comments

My fat loss experiments with ChatGPT and water fasting

https://community.webminal.org/t/my-fat-loss-experiments-with-chatgpt-and-water-fasting/8846
3•giis•17m ago•0 comments

Is it safe to call print in a Python signal handler?

https://iafisher.com/2026/08/sigprint
50•hellerve•3d ago•27 comments

Pop-2000, a lingua-franca POP-2 dialect

https://hitogata.neocities.org/POP-2000
16•surprisetalk•3d ago•1 comments

Orbs

https://ampcode.com/notes/orbs-explained
10•tosh•4d 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.