frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

CP/M-386 – CP/M for 386 protected mode, derived from CP/M‑68K

https://github.com/johnsonjh/cpm386
33•TMWNN•2h ago•9 comments

Karpathy’s Pelican

https://twitter.com/karpathy/status/2083749667410727319
459•delichon•22h ago•351 comments

Show HN: Isopolis – isometric pixel map of SF

https://sf.isopolis.city/
40•nuwandavek•2h ago•14 comments

Why Book Corners won't sync contributions back to OpenStreetMap

https://www.andreagrandi.it/posts/why-book-corners-wont-sync-contributions-back-to-openstreetmap/
47•pizzaiolo•2h ago•27 comments

Autoregressive Language Model on the 6502 Processor

https://mattbeton.com/blog/bitnet-6502.html
66•nmstoker•2d ago•7 comments

Show HN: ssh ssh.place

https://ssh.place
30•jeninh•2h ago•14 comments

RFC 9851: TLS 1.2 is in Feature Freeze

https://www.rfc-editor.org/rfc/rfc9851.html
14•Jimmc414•1h ago•3 comments

Show HN: Kakehashi – Experimental userspace to run macOS binaries on Linux ARM

https://github.com/wie-project/kakehashi
186•vlad_kalinkin•10h ago•40 comments

Note-Taking and Personal Knowledge Management

https://unattributed.cc/note-taking-and-personal-knowledge-management
140•surprisetalk•5d ago•41 comments

Developers are attached to tools because tools encode trust

https://stackoverflow.blog/2026/07/29/developers-are-attached-to-tools-because-tools-encode-trust/
164•HieronymusBosch•4d ago•85 comments

SwiftUI After 7 Years

https://ykvm.com/2026/07/swiftui-a-story-of-mediocrity/
118•mpweiher•7h ago•100 comments

Read the Novels and Forget Everything Else

https://hedgehogreview.com/web-features/thr/posts/read-the-novels-and-forget-everything-else
61•samclemens•2d ago•30 comments

The Computational Theory of Mind (2015)

https://plato.stanford.edu/entries/computational-mind/
35•cyanregiment•4h ago•12 comments

How the words we teach English language learners changed

https://pudding.cool/2026/07/essential-words/
193•c-oreills•11h ago•133 comments

Show HN: Mu – Tools for Agents

https://github.com/micro/mu
37•asim•4h ago•11 comments

Show HN: Make your Framework 12 sound like a creaky door

https://github.com/ArcaEge/creakwork12
57•arcaege•6h ago•7 comments

Show HN: NixOS-DGX-Spark – Nix and NixOS on the DGX Spark

https://github.com/graham33/nixos-dgx-spark
99•graham33•9h ago•29 comments

Show HN: A Handwritten Blogging Platform

https://handwritten.blog/
9•emilesilvis•2d ago•5 comments

TinyNES Review – A Super Niche NES Console

https://blog.lon.tv/2023/02/05/tinynes-review-a-super-niche-nes-console/
36•throwoutway•6h ago•7 comments

F*: A general-purpose proof-oriented programming language

https://fstar-lang.org/
160•ducktective•14h ago•70 comments

Twenty Years of RISC OS Open

https://www.riscosopen.org/news/articles/2026/06/20/twenty-years-of-risc-os-open
153•AlexeyBrin•14h ago•29 comments

Californians' data deletion requests, DROP, become enforceable Aug. 1

https://www.nbcsandiego.com/nbc-7-responds-2/californians-data-deletion-requests-drop-become-enfo...
98•MilnerRoute•4h ago•39 comments

Show HN: Shitty – fast terminal. Memory-unsafe and faster than yours

https://github.com/pg83/shitty
91•pshirshov•3h ago•89 comments

A tool for finding the causes of unstable Python tests

https://github.com/mgaitan/pytest-leak-finder
15•pomponchik•3d ago•0 comments

When transit passes were designed by hand (2022)

https://letterformarchive.org/news/milwaukee-transit-passes/
109•nate•2d ago•28 comments

The Myth of Snow Leopard

https://www.rubenerd.au/the-myth-of-snow-leopard/
47•speckx•8h ago•42 comments

My personal AI benchmark: "Generate an SVG of a frog with a Habsburg jaw."

https://frogs.vaguespac.es/
112•thebigship•7h ago•52 comments

Sharing an X11 Server Across Hosts with FamilyWild

https://dobrowolski.dev/article/sharing-an-x-server-across-hosts-with-familywild/
36•shirozuki•6h ago•10 comments

Playing with Georgia

https://mighil.com/playing-with-georgia
11•surprisetalk•4d ago•6 comments

'Crush this lady': how eBay harassment campaign led to $56M payout

https://www.ft.com/content/06ec1b03-d4af-40cf-b12a-4ba5a410f6d2
198•JumpCrisscross•7h ago•94 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.