frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: Terminal Phone – E2EE Walkie Talkie from the Command Line

https://gitlab.com/here_forawhile/terminalphone
86•smalltorch•2h ago•19 comments

Google API keys weren't secrets, but then Gemini changed the rules

https://trufflesecurity.com/blog/google-api-keys-werent-secrets-but-then-gemini-changed-the-rules
815•hiisthisthingon•17h ago•171 comments

Fentanyl makeover: Core structural redesign could lead to safer pain medications

https://www.scripps.edu/news-and-events/press-room/2026/20260211-janda-molecule.html
7•littlexsparkee•16m ago•0 comments

Show HN: Agent Swarm – Multi-agent self-learning teams (OSS)

https://github.com/desplega-ai/agent-swarm
9•tarasyarema•44m ago•3 comments

The Physics and Economics of Moving 44 Tonnes at 56mph

https://www.mikeayles.com/blog/heavy-haulage-basics/
35•mikeayles•2d ago•20 comments

Technical Excellence Is Not Enough

https://raccoon.land/posts/technical-excellence-is-not-enough/
19•bo0tzz•3h ago•5 comments

Jimi Hendrix was a systems engineer

https://spectrum.ieee.org/jimi-hendrix-systems-engineer
537•tintinnabula•16h ago•165 comments

Hightouch (YC S19) Is Hiring

https://hightouch.com/careers#open-positions
1•joshwget•58m ago

Tell HN: YC companies scrape GitHub activity, send spam emails to users

132•miki123211•3h ago•49 comments

Men in their 50s may be aging faster due to toxic 'forever chemicals'

https://www.cnn.com/2026/02/26/health/forever-chemicals-aging-men-wellness
38•jb1991•1h ago•15 comments

How will OpenAI compete?

https://www.ben-evans.com/benedictevans/2026/2/19/how-will-openai-compete-nkg2x
299•iamskeole•14h ago•402 comments

Banned in California

https://www.bannedincalifornia.org/
210•pie_flavor•13h ago•239 comments

First Website (1992)

https://info.cern.ch
246•shrikaranhanda•13h ago•69 comments

Windows 11 Notepad to support Markdown

https://blogs.windows.com/windows-insider/2026/01/21/notepad-and-paint-updates-begin-rolling-out-...
304•andreynering•19h ago•457 comments

Making MCP cheaper via CLI

https://kanyilmaz.me/2026/02/23/cli-vs-mcp.html
247•thellimist•16h ago•99 comments

Artist who “paints” portraits on glass by hitting it with a hammer

https://simonbergerart.com
198•cs702•3d ago•84 comments

You Want to Visit the UK? You Better Have a Google Play or App Store Account

https://www.heltweg.org/posts/you-want-to-visit-the-uk-you-better-have-a-google-play-or-app-store...
118•rhazn•1h ago•160 comments

Bus stop balancing is fast, cheap, and effective

https://worksinprogress.co/issue/the-united-states-needs-fewer-bus-stops/
375•surprisetalk•20h ago•542 comments

Large-Scale Online Deanonymization with LLMs

https://simonlermen.substack.com/p/large-scale-online-deanonymization
292•DalasNoin•1d ago•212 comments

Nihilistic Violent Extremism

https://en.wikipedia.org/wiki/Nihilistic_violent_extremism
9•doener•47m ago•0 comments

Show HN: Respectify – A comment moderator that teaches people to argue better

https://respectify.org/
184•vintagedave•22h ago•185 comments

Out of Light Adjust Share: Caravaggio, La Tour, and the Art of Attention

https://harpers.org/archive/2026/03/out-of-light-nicole-krauss-caravaggio-georges-de-la-tour/
24•prismatic•3d ago•1 comments

RAM now represents 35 percent of bill of materials for HP PCs

https://arstechnica.com/gadgets/2026/02/ram-now-represents-35-percent-of-bill-of-materials-for-hp...
299•jnord•10h ago•236 comments

A 26-Gram Butterfly-Inspired Robot Achieving Autonomous Tailless Flight

https://arxiv.org/abs/2602.06811
17•Terretta•3d ago•3 comments

The First Fully General Computer Action Model

https://si.inc/posts/fdm1/
272•nee1r•2d ago•69 comments

Anthropic ditches its core safety promise

https://www.cnn.com/2026/02/25/tech/anthropic-safety-policy-change
4•motbus3•7m ago•0 comments

Writers and Their Day Jobs

https://lithub.com/the-work-behind-the-writing-on-writers-and-their-day-jobs/
42•simplegeek•4d ago•13 comments

Tech companies shouldn't be bullied into doing surveillance

https://www.eff.org/deeplinks/2026/02/tech-companies-shouldnt-be-bullied-doing-surveillance
332•pseudolus•12h ago•106 comments

The Om Programming Language

https://www.om-language.com/
279•tosh•19h ago•77 comments

Number of UK workers on zero-hours contracts hits record high ahead of crackdown

https://www.bbc.co.uk/news/articles/czj1m7d4gxpo
4•robtherobber•42m ago•0 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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