frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

My server is a phone now

https://seg6.space/posts/phone-server/
153•seg6•4h ago•62 comments

Os8088: A powerful Mac-like OS for the IBM XT, 286, 386

https://os8088.com/
77•jggonz•3h ago•27 comments

The phone book that led us to Assad's spy chief in hiding

https://www.bbc.com/news/articles/c4gyrzn8p94o
23•cwwc•1h ago•4 comments

Improving Heuristics for A* Pathfinding

https://www.redblobgames.com/pathfinding/heuristics/differential.html
108•bobbiechen•1w ago•12 comments

Fastmail offers EU data region

https://www.fastmail.com/blog/fastmail-offers-eu-data-region/
333•groomlake•11h ago•163 comments

Shopify replaced Redis with MySQL for inventory reservations–and it scaled

https://shopify.engineering/scaling-inventory-reservations
75•adletbalzhanov•4h ago•37 comments

Dithered QR Codes

https://www.andrewt.net/dithered-qr-codes/wtf/
54•jmusall•4h ago•11 comments

_for-sale DNS records

https://specification.website/spec/foundations/for-sale-dns/
363•shaunpud•14h ago•134 comments

Open-source interactive map for the Aug 12 total solar eclipse

https://eclipsefan.org/?v=2&t=max&layers=eclipse%2Cbesselian%2Cumbra-live%2Cshadow-3d%2Ccloud-pro...
97•MarcoDewey•7h ago•20 comments

Making difficulty curves in games

http://www.davetech.co.uk/difficultycurves
72•hakkikonu•3d ago•26 comments

The Sound and Music of 'Hyper Light Drifter' [video]

https://gdcvault.com/play/1024135/The-Sound-and-Music-of
31•hyperific•3d ago•4 comments

Timeline of the OpenAI accidental attack against Hugging Face

https://simonwillison.net/2026/Aug/7/openai-timeline/
360•882542F3884314B•16h ago•358 comments

Unexpected events and prosocial behavior: the Batman effect

https://www.nature.com/articles/s44184-025-00171-5
11•davidbarker•6d ago•0 comments

TheoremDB · A public workspace for machine mathematics

https://theoremdb.org/
7•frozenseven•2h ago•0 comments

Can Intel finally beat ARM on performance per Watt?

https://hackaday.com/2026/08/08/want-energy-efficiency-dude-youre-getting-a-dell/
174•gumby•11h ago•127 comments

Triton: DirectX 11 Driver for QEMU

https://blog.getutm.app/2026/introducing-triton-directx-11-driver-for-qemu/
145•electricant•13h ago•27 comments

US Military's cyber command unit grapples with cluster of deaths by suicide

https://www.bloomberg.com/news/articles/2026-08-06/us-military-s-cyber-command-unit-grapples-with...
262•rbanffy•17h ago•412 comments

Building a local positioning system to track runners using Ultra-Wideband

https://zeus.ugent.be/blog/25-26/12urenloop-uwb/
50•robinpdev•1w ago•3 comments

Preventing Misfolding by Preventing Folding

https://www.science.org/content/blog-post/preventing-misfolding-preventing-folding
49•surprisetalk•4d ago•3 comments

ChatGPT starts blocking direct requests to copy an author's style

https://arstechnica.com/ai/2026/07/chatgpt-stops-cloning-famous-writers-voices-but-may-capture-a-...
11•Eloissssss•1h ago•0 comments

DDisasm: Reversible (bi-directional) Disassembler

https://github.com/GrammaTech/ddisasm
25•aboardRat4•5d ago•4 comments

Maryland Closes More of Cunningham Falls State Park After Second Beaver Attack

https://news.maryland.gov/dnr/2026/08/05/dnr-closes-additional-areas-of-cunningham-falls-state-pa...
99•bookofjoe•6h ago•62 comments

TinySol, a tiny solitaire game for DOS

https://classicbits.net/coding-and-software/my-software/monosol/
50•skibz•9h ago•14 comments

Danish high schoolers will have to verbally defend written assignments

https://mezha.net/eng/bukvy/ca117584_denmark_requires_oral/
530•theanonymousone•9h ago•248 comments

Lost my phone at the office. Claude suggested tracking Bluetooth signal strength

https://twitter.com/un1c0rnioz/status/2084686552299634805
233•ilamont•1d ago•168 comments

“Code was never the hard part” is an insult to all programmers

https://blog.senko.net/code-was-never-the-hard-part-is-an-insult-to-all-programmers
612•senko•12h ago•383 comments

Gateway 2000's hilariously bad ads in the 90s (Part II)

https://buttondown.com/suchbadtechads/archive/gateway-2000-part-2/
108•rfarley04•14h ago•84 comments

Message your other Claude Code sessions

https://code.claude.com/docs/en/cross-session-messaging
74•mfiguiere•11h ago•35 comments

DeepMind's WeatherNext model achieves breakthrough forecasting cyclones

https://deepmind.google/blog/weathernext-ai-model-achieves-breakthrough-in-forecasting-cyclones/
395•bhavansig•18h ago•121 comments

Voyager 1 FDS Computer Emulator

https://zaneham.github.io/voyager-fds-emulator/
79•rahen•14h ago•13 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.