frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Old and new apps, via modern coding agents

https://terrytao.wordpress.com/2026/07/11/old-and-new-apps-via-modern-coding-agents/
321•subset•7h ago•87 comments

Don't You Mean Extinct?

https://fabiensanglard.net/extinct/index.html
82•zdw•2h ago•31 comments

Claude Code May–July 2026 weekly limits promotion

https://support.claude.com/en/articles/15910845-claude-code-may-july-2026-weekly-limits-promotion
6•alvis•13m ago•3 comments

Show HN: Shirei, cross-platform GUI framework in native Go

https://github.com/hasenj/go-shirei/
29•hsn915•1h ago•12 comments

Automation Without Understanding

https://arxiv.org/abs/2607.06377
22•root-parent•1h ago•5 comments

How to Read More Books

https://scotto.me/blog/2026-07-12-how-to-read-more-books/
130•silcoon•2h ago•65 comments

Understanding the Odin Programming Language

https://odinbook.com/
112•AlexeyBrin•6h ago•50 comments

Why study Diophantine equations?

https://hidden-phenomena.com/articles/modular
30•mb1699•2h ago•9 comments

Against Usefulness

https://www.motivenotes.ai/p/against-usefulness
6•supo•27m ago•0 comments

The power of collaboration: How we can reduce traffic congestion

https://research.google/blog/the-power-of-collaboration-how-we-can-reduce-traffic-congestion/
22•raahelb•2h ago•15 comments

Ghostel.el: Terminal emulator powered by libghostty

https://dakra.github.io/ghostel/
195•signa11•9h ago•32 comments

Vint Cerf, “father of the Internet”, is retiring

https://techcrunch.com/2026/06/30/the-father-of-the-internet-is-finally-retiring/
244•compiler-guy•2d ago•132 comments

AI Boosts Research Careers but Flattens Scientific Discovery

https://spectrum.ieee.org/ai-science-research-flattens-discovery
102•zaikunzhang•4h ago•79 comments

Unauthenticated RCE in Motorola's MR2600 Router

https://mrbruh.com/motorola/
61•MrBruh•6h ago•21 comments

Autoresearch, Claude and Constrained Optimization

https://www.elliotcsmith.com/autoresearch-claude-and-constrained-optimization/
16•gmays•3h ago•4 comments

Morphometrics: Introduction to the Analysis of Shape

https://www.geol.umd.edu/~tholtz/G331/lectures/331biomech.html
12•num42•1w ago•0 comments

Theo de Raadt: "You've been smoking something mind altering" (2007)

https://marc.info/?l=openbsd-misc&m=119318909016582
28•turrini•2h ago•11 comments

Abject Praise

https://infrequently.org/2026/07/abject-praise/
5•genericlemon24•5d ago•1 comments

Satteri: A Markdown pipeline forged in Rust for the JavaScript world

https://satteri.bruits.org/
34•nateb2022•4d ago•5 comments

Mesh LLM: distributed AI computing on iroh

https://www.iroh.computer/blog/mesh-llm
323•tionis•19h ago•74 comments

Lessons from the Vasa Shipwreck

https://www.ft.com/content/200a6c44-9b66-4af3-82eb-98acb53898e4
22•bookofjoe•3d ago•26 comments

Show HN: Mindwalk – Replay coding-agent sessions on a 3D map of your codebase

https://github.com/cosmtrek/mindwalk
135•cosmtrek•12h ago•57 comments

Ditching Zotero for a Text File

https://atthis.link/blog/2026/57207.html
47•speckx•5d ago•29 comments

Croc: Securely transfer files and folders between two computers

https://github.com/schollz/croc/
4•gregsadetsky•2h ago•0 comments

Protobuf-py: Protobuf for Python, without compromises

https://buf.build/blog/protobuf-py
120•ming13•4d ago•34 comments

A no-brainer for protecting your brain

https://www.economist.com/leaders/2026/07/09/a-no-brainer-for-protecting-your-brain
69•saikatsg•2h ago•50 comments

Nvidia, CoreWeave, and Nebius: Inside the Circular Financing of the GPU Boom

https://io-fund.com/ai-stocks/nvidia-coreweave-nebius-circular-financing-gpu-boom
351•adletbalzhanov•1d ago•152 comments

TK, or the secret to effortless writing (2024)

https://atthis.link/blog/2024/49629.html
29•Tomte•2h ago•15 comments

Show HN: Kurvengefahr – browser CAD/CAM for pen plotters

https://kurvengefahr.org/
8•tibordp•4h ago•2 comments

Show HN: Skillscript – A declarative, sandboxed language for tool orchestration

https://github.com/sshwarts/skillscript
11•sshwarts•4h ago•6 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.