frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

How NASA built Artemis II’s fault-tolerant computer

https://cacm.acm.org/news/how-nasa-built-artemis-iis-fault-tolerant-computer/
377•speckx•18h ago•133 comments

I still prefer MCP over skills

https://david.coffee/i-still-prefer-mcp-over-skills/
175•gmays•7h ago•150 comments

Native Instant Space Switching on macOS

https://arhan.sh/blog/native-instant-space-switching-on-macos/
508•PaulHoule•14h ago•237 comments

ETH Zurich demonstrates 17,000 qubit array with 99.91% fidelity

https://ethz.ch/en/news-and-events/eth-news/news/2026/04/a-new-trick-brings-stability-to-quantum-...
57•joko42•5h ago•9 comments

We've raised $17M to build what comes after Git

https://blog.gitbutler.com/series-a
130•ellieh•7h ago•271 comments

Generative art over the years

https://blog.veitheller.de/Generative_art_over_the_years.html
148•evakhoury•2d ago•38 comments

Scientists invented a fake disease. AI told people it was real

https://www.nature.com/articles/d41586-026-01100-y
29•latexr•1h ago•12 comments

Charcuterie – Visual similarity Unicode explorer

https://charcuterie.elastiq.ch/
232•rickcarlino•13h ago•42 comments

War on Raze

https://gist.github.com/chrispsn/af6844b80687462814fc39d4b97399a6
10•tosh•3d ago•3 comments

The Art of Risk Management (2017)

https://www.bcg.com/publications/2017/finance-function-excellence-corporate-development-art-risk-...
6•walterbell•2d ago•0 comments

RAM Has a Design Flaw from 1966. I Bypassed It [video]

https://www.youtube.com/watch?v=KKbgulTp3FE
222•surprisetalk•2d ago•59 comments

Artemis II and the invisible hazard on the way to the Moon

https://www.ansto.gov.au/news/artemis-ii-and-invisible-hazard-on-way-to-moon-part-1
8•zeristor•2h ago•7 comments

Unfolder for Mac – A 3D model unfolding tool for creating papercraft

https://www.unfolder.app/
234•codazoda•16h ago•45 comments

Zero-build privacy policies with Astro

https://www.openpolicy.sh/blog/no-build-astro
5•jamie_davenport•1h ago•4 comments

Old laptops in a colo as low cost servers

https://colaptop.pages.dev/
271•argentum47•15h ago•160 comments

CollectWise (YC F24) Is Hiring

https://www.ycombinator.com/companies/collectwise/jobs/Ktc6m6o-ai-agent-engineer
1•OBrien_1107•5h ago

Penguin 'Toxicologists' Find PFAS Chemicals in Remote Patagonia

https://www.ucdavis.edu/health/news/penguin-toxicologists-find-pfas-chemicals-remote-patagonia
9•giuliomagnifico•3h ago•5 comments

Principles of Mechanical Sympathy

https://martinfowler.com/articles/mechanical-sympathy-principles.html
58•zdw•2d ago•7 comments

Afrika Bambaataa, hip-hop pioneer, has died

https://www.bbc.co.uk/news/articles/c2evppm30p7o
122•mellosouls•5h ago•27 comments

Instant 1.0, a backend for AI-coded apps

https://www.instantdb.com/essays/architecture
150•stopachka•15h ago•78 comments

PicoZ80 – Drop-In Z80 Replacement

https://eaw.app/picoz80/
192•rickcarlino•14h ago•31 comments

Research-Driven Agents: When an agent reads before it codes

https://blog.skypilot.co/research-driven-agents/
178•hopechong•16h ago•48 comments

The Raft consensus algorithm explained through "Mean Girls" (2019)

https://www.cockroachlabs.com/blog/raft-is-so-fetch/
82•vermilingua•6h ago•21 comments

VFX HQ: Visual Effects Headquarters (2000)

https://www.vfxhq.com/index.html
11•exvi•2d ago•0 comments

YouTube locked my accounts and I can't cancel my subscription

https://pocketables.com/2026/04/ai-music-corporate-control-and-the-creator-who-cant-even-leave.html
112•digitalhigh•4h ago•72 comments

Hegel, a universal property-based testing protocol and family of PBT libraries

https://hegel.dev
114•PaulHoule•15h ago•32 comments

An AI robot in my home

https://allevato.me/2026/04/07/an-ai-robot-in-my-home
36•kukanani•2d ago•13 comments

Reverse engineering Gemini's SynthID detection

https://github.com/aloshdenny/reverse-SynthID
151•_tk_•13h ago•51 comments

Will I ever own a zettaflop?

https://geohot.github.io//blog/jekyll/update/2026/01/26/own-a-zettaflop.html
96•surprisetalk•3d ago•62 comments

Kagi Product Tips – Customize Your Search Results with URL Redirects

https://blog.kagi.com/tips/redirects
84•treetalker•12h ago•13 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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