frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Making RAM at Home [video]

https://www.youtube.com/watch?v=h6GWikWlAQA
220•kaipereira•1d ago•49 comments

ChatGPT Images 2.0

https://openai.com/index/introducing-chatgpt-images-2-0/
720•wahnfrieden•12h ago•553 comments

Acetaminophen vs. ibuprofen

https://asteriskmag.com/issues/14/the-mystery-in-the-medicine-cabinet
280•nkurz•1d ago•132 comments

Diverse organic molecules on Mars revealed by the first SAM TMAH experiment

https://www.courthousenews.com/preserved-for-billions-of-years-organic-compounds-found-on-mars/
58•geox•20h ago•1 comments

Laws of Software Engineering

https://lawsofsoftwareengineering.com
937•milanm081•20h ago•451 comments

SpaceX says it has agreement to acquire Cursor for $60B

https://twitter.com/spacex/status/2046713419978453374
519•dmarcos•9h ago•629 comments

Garbage Collection Without Unsafe Code

https://fitzgen.com/2024/02/06/safe-gc.html
19•foota•3d ago•1 comments

The Vercel breach: OAuth attack exposes risk in platform environment variables

https://www.trendmicro.com/en_us/research/26/d/vercel-breach-oauth-supply-chain.html
303•queenelvis•14h ago•106 comments

Drunk post: Things I've learned as a senior engineer (2021)

https://luminousmen.substack.com/p/drunk-post-things-ive-learned-as
118•zdw•7h ago•71 comments

Windows Server 2025 Runs Better on ARM

https://jasoneckert.github.io/myblog/server-2025-arm64/
106•jasoneckert•3d ago•85 comments

Britannica11.org – a structured edition of the 1911 Encyclopædia Britannica

https://britannica11.org/
270•ahaspel•13h ago•95 comments

Contact Lens Uses Microfluidics to Monitor and Treat Glaucoma

https://spectrum.ieee.org/smart-contact-lens-glaucoma-microfluidics
5•pseudolus•2d ago•0 comments

Stephen's Sausage Roll remains one of the most influential puzzle games

https://thinkygames.com/features/10-years-of-grilling-stephens-sausage-roll-remains-one-of-the-mo...
178•tobr•3d ago•88 comments

Meta to start capturing employee mouse movements, keystrokes for AI training

https://www.reuters.com/sustainability/boards-policy-regulation/meta-start-capturing-employee-mou...
484•dlx•13h ago•361 comments

Changes to GitHub Copilot individual plans

https://github.blog/news-insights/company-news/changes-to-github-copilot-individual-plans/
405•zorrn•1d ago•156 comments

Fusion Power Plant Simulator

https://www.fusionenergybase.com/fusion-power-plant-simulator
146•sam•16h ago•92 comments

Framework Laptop 13 Pro

https://frame.work/laptop13pro
1161•Trollmann•13h ago•592 comments

A printing press for biological data

https://www.owlposting.com/p/the-printing-press-for-biological
21•crescit_eundo•1d ago•0 comments

Cal.diy: open-source community edition of cal.com

https://github.com/calcom/cal.diy
187•petecooper•13h ago•48 comments

CrabTrap: An LLM-as-a-judge HTTP proxy to secure agents in production

https://www.brex.com/crabtrap
109•pedrofranceschi•15h ago•36 comments

Hunting a 34 year old pointer bug in EtherSlip

https://www.brutman.com/Adventures_In_Code/EtherSlip_ARP/EtherSlip_ARP.html
25•mbbrutman•2d ago•4 comments

Edit store price tags using Flipper Zero

https://github.com/i12bp8/TagTinker
328•trueduke•2d ago•299 comments

FBI looks into dead or missing scientists tied to NASA, Blue Origin, SpaceX

https://fortune.com/2026/04/21/scientists-disappear-die-nasa-space-blue-origin-spacex/
113•ineedasername•4h ago•34 comments

Some secret management belongs in your HTTP proxy

https://blog.exe.dev/http-proxy-secrets
17•tosh•2d ago•3 comments

Kuri – Zig based agent-browser alternative

https://github.com/justrach/kuri
13•sorcercode•4h ago•2 comments

Claude Code to be removed from Anthropic's Pro plan?

https://bsky.app/profile/edzitron.com/post/3mjzxwfx3qs2a
506•JamesMcMinn•10h ago•492 comments

20000 Gates and 20 MIPS [pdf]

https://bitsavers.org/pdf/amdahl/history/20000_Gates_and_20_MIPS_199011.pdf
8•ingve•3d ago•3 comments

Running a Minecraft Server and more on a 1960s UNIVAC Computer

https://farlow.dev/2026/04/17/running-a-minecraft-server-and-more-on-a-1960s-univac-computer
212•brilee•3d ago•33 comments

Show HN: VidStudio, a browser based video editor that doesn't upload your files

https://vidstudio.app/video-editor
268•kolx•19h ago•86 comments

Global growth in solar "the largest ever observed for any source"

https://arstechnica.com/science/2026/04/global-growth-in-solar-the-largest-ever-observed-for-any-...
71•tambourine_man•5h 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•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•11mo 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•11mo 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•11mo ago
do you have references to

> TTT, cannon layers, and titans

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