frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Googlebook

https://googlebook.google/
486•tambourine_man•5h ago•799 comments

How to make your text look futuristic (2016)

https://typesetinthefuture.com/2016/02/18/futuristic/
128•_vaporwave_•2h ago•12 comments

CERT is releasing six CVEs for serious security vulnerabilities in dnsmasq

https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2026q2/018471.html
185•chizhik-pyzhik•4h ago•79 comments

Show HN: Needle: We Distilled Gemini Tool Calling into a 26M Model

https://github.com/cactus-compute/needle
207•HenryNdubuaku•4h ago•67 comments

Why senior developers fail to communicate their expertise

https://www.nair.sh/guides-and-opinions/communicating-your-expertise/why-senior-developers-fail-t...
293•nilirl•7h ago•147 comments

Quack: The DuckDB Client-Server Protocol

https://duckdb.org/2026/05/12/quack-remote-protocol
130•aduffy•4h ago•28 comments

The Future of Obsidian Plugins

https://obsidian.md/blog/future-of-plugins/
264•xz18r•6h ago•105 comments

Rendering the Sky, Sunsets, and Planets

https://blog.maximeheckel.com/posts/on-rendering-the-sky-sunsets-and-planets/
377•ibobev•9h ago•34 comments

Reimagining the mouse pointer for the AI era

https://deepmind.google/blog/ai-pointer/
95•devhouse•5h ago•85 comments

Learning Software Architecture

https://matklad.github.io/2026/05/12/software-architecture.html
499•surprisetalk•13h ago•101 comments

Is this why science advances one funeral at a time?

https://nautil.us/is-this-why-science-advances-one-funeral-at-a-time-1280650
18•Brajeshwar•5h ago•24 comments

Beyond Semantic Similarity

https://arxiv.org/abs/2605.05242
26•44za12•2h ago•3 comments

Launch HN: Voker (YC S24) – Analytics for AI Agents

https://voker.ai
33•ttpost•6h ago•19 comments

Bambu Lab is abusing the open source social contract

https://www.jeffgeerling.com/blog/2026/bambu-lab-abusing-open-source-social-contract/
987•rubenbe•7h ago•336 comments

Dead.Letter (CVE-2026-45185) – How XBOW found an unauthenticated RCE on Exim

https://xbow.com/blog/dead-letter-cve-2026-45185-xbow-found-rce-exim
48•fedek_•4h ago•23 comments

Show HN: Statewright – Visual state machines that make AI agents reliable

https://github.com/statewright/statewright
53•azurewraith•8h ago•14 comments

Show HN: Agentic interface for mainframes and COBOL

https://www.hypercubic.ai/hopper
40•sai18•5h ago•23 comments

Riding the D in Los Angeles: city hopes new subway stations will be game changer

https://www.theguardian.com/us-news/2026/may/09/los-angeles-subway-public-transportation
35•raybb•1d ago•10 comments

When life gives you lemons, write better error messages

https://wix-ux.com/when-life-gives-you-lemons-write-better-error-messages-46c5223e1a2f
92•luispa•4d ago•27 comments

Show HN: Gigacatalyst – Extend your SaaS with an embedded AI builder

33•namanyayg•6h ago•8 comments

Canada’s Bill C-22 Is a Repackaged Version of Last Year’s Surveillance Nightmare

https://www.eff.org/deeplinks/2026/05/canadas-bill-c-22-repackaged-version-last-years-surveillanc...
198•Brajeshwar•5h ago•62 comments

Instructure pays ransom to Canvas hackers

https://www.insidehighered.com/news/tech-innovation/administrative-tech/2026/05/11/instructure-pa...
204•Cider9986•19h ago•193 comments

SQL: Incorrect by Construction

https://chreke.com/posts/sql-incorrect-by-construction
29•ingve•4h ago•26 comments

We accidentally recreated old Facebook

https://amrshawky.com/posts/we-accidentally-recreated-fb/
40•amr_shawky•2d ago•24 comments

The Moth Story Map

https://themoth.org/dispatches/story-map
22•jxmorris12•4d ago•3 comments

Text Blaze (YC W21) Is Hiring for a No-AI Summer Internship

https://www.ycombinator.com/companies/text-blaze/jobs/P4CCN62-the-blaze-no-ai-summer-internship
1•scottfr•10h ago

The Real Story of Troy

https://storica.club/blog/troy-was-real/
47•cemsakarya•2d ago•20 comments

The Surprisingly Long Life of the Vacuum Tube

https://www.construction-physics.com/p/the-surprisingly-long-life-of-the
58•surprisetalk•1d ago•38 comments

Snowflake Postgres, Lakebase, HorizonDB: Picking the Lock-In You Want

https://thebuild.com/blog/2026/05/12/snowflake-postgres-lakebase-horizondb-picking-the-lock-in-yo...
17•samaysharma•2h ago•4 comments

Screenshots of Old Desktop OSes

http://www.typewritten.org/Media/
629•adunk•17h ago•331 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•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•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•12mo ago
do you have references to

> TTT, cannon layers, and titans

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