frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Artemis II crew see first glimpse of far side of Moon [video]

https://www.bbc.com/news/videos/ce3d5gkd2geo
150•mooreds•2h ago•104 comments

Eight years of wanting, three months of building with AI

https://lalitm.com/post/building-syntaqlite-ai/
211•brilee•4h ago•41 comments

A tail-call interpreter in (nightly) Rust

https://www.mattkeeter.com/blog/2026-04-05-tailcall/
33•g0xA52A2A•1h ago•1 comments

Codex is switching to API pricing based usage for all users

https://help.openai.com/en/articles/20001106-codex-rate-card
58•ccmcarey•1h ago•32 comments

A Claude Code skill that makes Claude talk like a caveman, cutting token use

https://github.com/JuliusBrussee/caveman
407•tosh•8h ago•242 comments

Computational Physics (2nd Edition)

https://websites.umich.edu/~mejn/cp2/
10•teleforce•1h ago•1 comments

Nanocode: The best Claude Code that $200 can buy in pure JAX on TPUs

https://github.com/salmanmohammadi/nanocode/discussions/1
26•desideratum•2h ago•4 comments

Finnish sauna heat exposure induces stronger immune cell than cytokine responses

https://www.tandfonline.com/doi/full/10.1080/23328940.2026.2645467#abstract
169•Growtika•3h ago•92 comments

Baby's Second Garbage Collector

https://www.matheusmoreira.com/articles/babys-second-garbage-collector
19•matheusmoreira•3d ago•2 comments

Someone at BrowserStack Is Leaking Users' Email Address

https://shkspr.mobi/blog/2026/04/someone-at-browserstack-is-leaking-users-email-address/
299•m_km•3h ago•79 comments

Lisette a little language inspired by Rust that compiles to Go

https://lisette.run/
197•jspdown•10h ago•98 comments

The threat is comfortable drift toward not understanding what you're doing

https://ergosphere.blog/posts/the-machines-are-fine/
581•zaikunzhang•7h ago•409 comments

German implementation of eIDAS will require an Apple/Google account to function

https://bmi.usercontent.opencode.de/eudi-wallet/wallet-development-documentation-public/latest/ar...
471•DyslexicAtheist•18h ago•431 comments

Friendica – A Decentralized Social Network

https://friendi.ca/
65•janandonly•6h ago•29 comments

Hightouch (YC S19) Is Hiring

https://hightouch.com/careers#open-positions
1•joshwget•5h ago

My Google Workspace account suspension

https://zencapital.substack.com/p/sad-story-of-my-google-workspace
217•zenincognito•5h ago•105 comments

OpenScreen is an open-source alternative to Screen Studio

https://github.com/siddharthvaddem/openscreen
397•jskopek•4d ago•68 comments

Iguanaworks has closed and our products are no longer sold

http://iguanaworks.net/products/usb-ir-transceiver.html
71•ripe•3h ago•10 comments

Phone-free bars and restaurants on the rise across the U.S.

https://www.axios.com/2026/04/05/phone-free-restaurants-bars-bans-restrictions-offline
37•Brajeshwar•2h ago•23 comments

Introduction to Computer Music (2009) [pdf]

https://composerprogrammer.com/introductiontocomputermusic.pdf
201•luu•15h ago•61 comments

Tracing Goroutines in Realtime with eBPF

https://sazak.io/articles/tracing-goroutines-in-realtime-with-ebpf-2026-03-31
20•darccio•3d ago•3 comments

Aegis – open-source FPGA silicon

https://github.com/MidstallSoftware/aegis
89•rosscomputerguy•11h ago•8 comments

Shared mutable state in Rust (2022)

https://draft.ryhl.io/blog/shared-mutable-state/
28•vinhnx•3d ago•6 comments

StackOverflow: Retiring the Beta Site

https://meta.stackoverflow.com/questions/438628/retiring-the-beta-site
28•stefankuehnel•1h ago•17 comments

Perfmon – Consolidate your favorite CLI monitoring tools into a single TUI

https://github.com/sumant1122/Perfmon
10•paperplaneflyr•2h ago•2 comments

Scientists Figured Out How Eels Reproduce (2022)

https://www.intelligentliving.co/scientists-finally-figured-out-how-eels-reproduce/
74•thunderbong•3d ago•16 comments

Show HN: OsintRadar – Curated directory for osint tools

https://osintradar.com/
51•lexalizer•11h ago•5 comments

Common drug tests lead to tens of thousands wrongful arrests a year

https://www.cnn.com/2026/04/05/us/colorado-field-drug-test-law
82•rawgabbit•5h ago•52 comments

SPF/PC v4 for MS-DOS, FreeDOS, x86

https://github.com/moshix/SPFPC
16•hggh•2h ago•4 comments

Show HN: A game where you build a GPU

https://jaso1024.com/mvidia/
869•Jaso1024•1d ago•171 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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