frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

The Three Pillars of JavaScript Bloat

https://43081j.com/2026/03/three-pillars-of-javascript-bloat
139•onlyspaceghost•4h ago•65 comments

Tinybox – Offline AI device 120B parameters

https://tinygrad.org/#tinybox
426•albelfio•10h ago•257 comments

Some things just take time

https://lucumr.pocoo.org/2026/3/20/some-things-just-take-time/
612•vaylian•16h ago•193 comments

Professional video editing, right in the browser with WebGPU and WASM

https://tooscut.app/
212•mohebifar•9h ago•60 comments

Chest Fridge (2009)

https://mtbest.net/chest-fridge/
67•wolfi1•5h ago•49 comments

Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2

https://radar.cloudflare.com/domains/domain/archive.today
76•winkelmann•3h ago•30 comments

Floci – A free, open-source local AWS emulator

https://github.com/hectorvent/floci
140•shaicoleman•8h ago•31 comments

Boomloom: Think with your hands

https://www.theboomloom.com
87•rasengan0•1d ago•7 comments

Electronics for Kids, 2nd Edition

https://nostarch.com/electronics-for-kids-2e
155•0x54MUR41•3d ago•29 comments

Do Not Turn Child Protection into Internet Access Control

https://news.dyne.org/child-protection-is-not-access-control/
615•smartmic•10h ago•325 comments

Bayesian statistics for confused data scientists

https://nchagnet.pages.dev/blog/bayesian-statistics-for-confused-data-scientists/
89•speckx•3d ago•24 comments

Grafeo – A fast, lean, embeddable graph database built in Rust

https://grafeo.dev/
209•0x1997•15h ago•68 comments

Alpha Micro AM-1000E and AM-1200

http://oldvcr.blogspot.com/2026/03/refurb-weekend-double-header-alpha.html
9•goldenskye•3h ago•0 comments

Trivy ecosystem supply chain briefly compromised

https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23
55•batch12•2d ago•20 comments

Hide macOS Tahoe's Menu Icons

https://512pixels.net/2026/03/hide-macos-tahoes-menu-icons-with-this-one-simple-trick/
169•soheilpro•13h ago•58 comments

It's Their Mona Lisa

https://ironicsans.ghost.io/its-t-mona-lisa/
14•ramimac•3d ago•0 comments

Show HN: Termcraft – terminal-first 2D sandbox survival in Rust

https://github.com/pagel-s/termcraft
108•sebosch•12h ago•19 comments

Common Lisp Development Tooling

https://www.creativetension.co/posts/common-lisp-development-tooling
76•0bytematt•10h ago•14 comments

Sashiko: An agentic Linux kernel code review system

https://sashiko.dev/
11•Lwrless•2h ago•0 comments

How Invisalign became the biggest user of 3D printers

https://www.wired.com/story/how-invisalign-became-the-worlds-biggest-3d-printing-company/
153•mikhael•3d ago•115 comments

The paddle wheel aircraft carriers of Lake Michigan

https://signoregalilei.com/2026/03/08/the-paddle-wheel-aircraft-carriers-of-lake-michigan/
72•surprisetalk•4d ago•6 comments

Thinking Fast, Slow, and Artificial: How AI Is Reshaping Human Reasoning

https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6097646
120•Anon84•15h ago•68 comments

Training Center for Maneuvering on Manned Model Ships

https://www.portrevel.com/
5•mhb•1d ago•0 comments

Ubuntu 26.04 Ends 46 Years of Silent sudo Passwords

https://pbxscience.com/ubuntu-26-04-ends-46-years-of-silent-sudo-passwords/
353•akersten•1d ago•346 comments

Show HN: Atomic – Self-hosted, semantically-connected personal knowledge base

https://github.com/kenforthewin/atomic
84•kenforthewin•11h ago•15 comments

How Ford burned $12B in Brazil (2021)

https://www.reuters.com/business/autos-transportation/how-ford-burned-12-billion-brazil-2021-05-20/
46•kaycebasques•15h ago•21 comments

A digital resource for studying the graffiti of Herculaneum and Pompeii

https://ancientgraffiti.org/Graffiti/
17•thomassmith65•4d ago•1 comments

Sandboxing: Foolproof Boundaries vs. Unbounded Foolishness (2025)

https://spawn-queue.acm.org/doi/10.1145/3733699
18•antlai•4d ago•0 comments

ZJIT removes redundant object loads and stores

https://railsatscale.com/2026-03-18-how-zjit-removes-redundant-object-loads-and-stores/
82•tekknolagi•3d ago•15 comments

Meta's Omnilingual MT for 1,600 Languages

https://ai.meta.com/research/publications/omnilingual-mt-machine-translation-for-1600-languages/?...
129•j0e1•4d ago•37 comments
Open in hackernews

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

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

Comments

MacsHeadroom•10mo 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.