frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Google Safe Browsing missed 84% of phishing sites we found in February

https://www.norn-labs.com/blog/huginn-report-feb-2026
39•jdup7•57m ago•11 comments

Judge Orders Government to Begin Refunding More Than $130B in Tariffs

https://www.wsj.com/politics/policy/judge-orders-government-to-begin-refunding-more-than-130-bill...
410•JumpCrisscross•1h ago•312 comments

Show HN: Jido 2.0, Elixir Agent Framework

https://jido.run/blog/jido-2-0-is-here
15•mikehostetler•12m ago•1 comments

Nvidia PersonaPlex 7B on Apple Silicon: Full-Duplex Speech-to-Speech in Swift

https://blog.ivan.digital/nvidia-personaplex-7b-on-apple-silicon-full-duplex-speech-to-speech-in-...
255•ipotapov•8h ago•83 comments

Fast-Servers

https://geocar.sdf1.org/fast-servers.html
20•tosh•1h ago•7 comments

Google Workspace CLI

https://github.com/googleworkspace/cli
768•gonzalovargas•15h ago•257 comments

Good software knows when to stop

https://ogirardot.writizzy.com/p/good-software-knows-when-to-stop
28•ssaboum•2h ago•17 comments

Palantir and other tech companies are stocking offices with tobacco products

https://fortune.com/2026/03/04/palantir-tech-companies-offices-vending-machines-tobacco-worker-pr...
45•donutshop•44m ago•33 comments

Relicensing with AI-Assisted Rewrite

https://tuananh.net/2026/03/05/relicensing-with-ai-assisted-rewrite/
280•tuananh•10h ago•273 comments

The L in "LLM" Stands for Lying

https://acko.net/blog/the-l-in-llm-stands-for-lying/
482•LorenDB•11h ago•307 comments

World-first gigabit laser link between aircraft and geostationary satellite

https://www.esa.int/Applications/Connectivity_and_Secure_Communications/World-first_gigabit-per-s...
80•giuliomagnifico•3d ago•32 comments

Poor Man's Polaroid

https://boxart.lt/blog/poor_mans_polaroid
117•ZacnyLos•8h ago•39 comments

Rising carbon dioxide levels now detected in human blood

https://phys.org/news/2026-02-carbon-dioxide-human-blood.html
72•wkrsz•1h ago•63 comments

Intelligence is a commodity. Context is the real AI Moat

https://adlrocha.substack.com/p/adlrocha-intelligence-is-a-commodity
33•adlrocha•4d ago•2 comments

Smalltalk's Browser: Unbeatable, yet Not Enough

https://blog.lorenzano.eu/smalltalks-browser-unbeatable-yet-not-enough/
90•mpweiher•8h ago•34 comments

AMD will bring its “Ryzen AI” processors to standard desktop PCs for first time

https://arstechnica.com/gadgets/2026/03/amd-ryzen-ai-400-cpus-will-bring-upgraded-graphics-to-soc...
157•Bender•3d ago•141 comments

The Man Who Broke into Jail

https://www.newyorker.com/magazine/2026/03/09/alexander-friedmann-profile-prison-reform
19•fortran77•1d ago•6 comments

Building a new Flash

https://bill.newgrounds.com/news/post/1607118
633•TechPlasma•19h ago•207 comments

Billy bookshelves as a retro motherboard "rack"

https://rubenerd.com/billy-bookcase-as-a-retro-motherboard-rack/
37•ingve•4d ago•30 comments

Jails for NetBSD – Kernel Enforced Isolation and Native Resource Control

https://netbsd-jails.petermann-digital.de/
65•vermaden•8h ago•16 comments

Arabic document from 17th-cent. rubbish heap confirms semi-legendary Nubian king

https://phys.org/news/2026-02-arabic-document-17th-century-rubbish.html
94•wglb•2d ago•30 comments

OpenBSD on SGI: A Rollercoaster Story

http://miod.online.fr/software/openbsd/stories/sgiall.html
59•brynet•9h ago•2 comments

Something is afoot in the land of Qwen

https://simonwillison.net/2026/Mar/4/qwen/
741•simonw•1d ago•319 comments

No right to relicense this project

https://github.com/chardet/chardet/issues/327
367•robin_reala•7h ago•237 comments

MacBook Neo

https://www.apple.com/newsroom/2026/03/say-hello-to-macbook-neo/
1867•dm•1d ago•2168 comments

Earth Garden: Field Recordings Around the World

https://earth-garden.alen.ro/
33•alentodorov•1d ago•10 comments

BBC says 'irreversible' trends mean it will not survive without major overhaul

https://www.theguardian.com/media/2026/mar/05/bbc-charter-renewal-tv-licence-major-overhaul
10•beardyw•40m ago•5 comments

BMW Group to deploy humanoid robots in production in Germany for the first time

https://www.press.bmwgroup.com/global/article/detail/T0455864EN/bmw-group-to-deploy-humanoid-robo...
188•JeanKage•18h ago•206 comments

US tech firms pledge at White House to bear costs of energy for datacenters

https://www.theguardian.com/us-news/2026/mar/04/us-tech-companies-energy-cost-pledge-white-house
132•geox•14h ago•151 comments

Picking Up a Zillion Pieces of Litter

https://www.sixstepstobetterhealth.com/litter.html
179•colinbartlett•3d ago•63 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.