frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Autoresearch on an old research idea

https://ykumar.me/blog/eclip-autoresearch/
219•ykumards•4h ago•64 comments

FCC Updates Covered List to Include Foreign-Made Consumer Routers

https://www.fcc.gov/document/fcc-updates-covered-list-include-foreign-made-consumer-routers
51•moonka•1h ago•12 comments

Printable Claude Code Cheat Sheet (auto-updated daily)

https://cc.storyfox.cz
37•phasE89•1h ago•11 comments

iPhone 17 Pro Demonstrated Running a 400B LLM

https://twitter.com/anemll/status/2035901335984611412
429•anemll•8h ago•225 comments

How I'm Productive with Claude Code

https://neilkakkar.com/productive-with-claude-code.html
79•neilkakkar•2h ago•49 comments

Hacker Mints $80M USD Worth of USR Stablecoins

https://bfmtimes.com/hacker-mints-80-million-worth-of-fake-stablecoins-and-swaps-them-for-eth/
13•timbowhite•1h ago•1 comments

Local Stack Archived their GitHub repo and requires an account to run

https://github.com/localstack/localstack
121•ecshafer•4h ago•59 comments

Finding all regex matches has always been O(n²)

https://iev.ee/blog/the-quadratic-problem-nobody-fixed/
132•lalitmaganti•4d ago•30 comments

Dune3d: A parametric 3D CAD application

https://github.com/dune3d/dune3d
71•luu•1d ago•19 comments

Trivy under attack again: Widespread GitHub Actions tag compromise secrets

https://socket.dev/blog/trivy-under-attack-again-github-actions-compromise
134•jicea•1d ago•48 comments

Show HN: Cq – Stack Overflow for AI coding agents

https://blog.mozilla.ai/cq-stack-overflow-for-agents/
4•peteski22•6h ago•0 comments

Ju Ci (锔瓷): The Ancient Art of Repairing Porcelain

https://thesublimeblog.org/2025/03/13/ju-ci-the-ancient-art-of-repairing-porcelain/
9•lawrenceyan•2d ago•0 comments

Two pilots dead after plane and ground vehicle collide at LaGuardia

https://www.bbc.com/news/articles/cy01g522ww4o
291•mememememememo•15h ago•473 comments

An incoherent Rust

https://www.boxyuwu.blog/posts/an-incoherent-rust/
79•emschwartz•7h ago•23 comments

BIO: The Bao I/O Coprocessor

https://www.bunniestudios.com/blog/2026/bio-the-bao-i-o-coprocessor/
107•zdw•3d ago•26 comments

US and TotalEnergies reach 'nearly $1B' deal to end offshore wind projects

https://www.lemonde.fr/en/international/article/2026/03/23/us-and-totalenergies-reach-nearly-1-bi...
277•lode•5h ago•190 comments

I built an AI receptionist for a mechanic shop

https://www.itsthatlady.dev/blog/building-an-ai-receptionist-for-my-brother/
190•mooreds•12h ago•211 comments

AI Risks "Hypernormal" Science

https://www.asimov.press/p/ai-science
48•mailyk•4h ago•30 comments

An unsolicited guide to being a researcher [pdf]

https://emerge-lab.github.io/papers/an-unsolicited-guide-to-good-research.pdf
150•sebg•4d ago•21 comments

Bombadil: Property-based testing for web UIs

https://github.com/antithesishq/bombadil
215•Klaster_1•4d ago•87 comments

Walmart: ChatGPT checkout converted 3x worse than website

https://searchengineland.com/walmart-chatgpt-checkout-converted-worse-472071
391•speckx•4d ago•256 comments

Digs: iOS app that syncs your Discogs collection and lets you browse it offline

https://lustin.fr/blog/building-digs/
37•rlustin•14h ago•16 comments

Migrating to the EU

https://rz01.org/eu-migration/
802•exitnode•12h ago•620 comments

Chat GPT 5.2 cannot explain the German word "geschniegelt"

https://old.reddit.com/r/ChatGPT/comments/1r4goxh/chat_gpt_52_cannot_explain_the_word_geschniegelt/
24•doener•1h ago•4 comments

America tells private firms to “hack back”

https://www.economist.com/united-states/2026/03/22/america-tells-private-firms-to-hack-back
81•andsoitis•9h ago•90 comments

“Collaboration” is bullshit

https://www.joanwestenberg.com/collaboration-is-bullshit/
267•mitchbob•21h ago•143 comments

Is it a pint?

https://isitapint.com/
167•cainxinth•6h ago•141 comments

General Motors is assisting with the restoration of a rare EV1

https://evinfo.net/2026/03/general-motors-is-assisting-with-the-restoration-of-an-1996-ev1/
86•betacollector64•3d ago•101 comments

GitHub appears to be struggling with measly three nines availability

https://www.theregister.com/2026/02/10/github_outages/
421•richtr•12h ago•219 comments

Can you get root with only a cigarette lighter? (2024)

https://www.da.vidbuchanan.co.uk/blog/dram-emfi.html
172•HeliumHydride•3d ago•31 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.