frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Google releases Gemma 4 open models

https://deepmind.google/models/gemma/gemma-4/
1045•jeffmcjunkin•7h ago•327 comments

Tailscale's new macOS home

https://tailscale.com/blog/macos-notch-escape
275•tosh•5h ago•139 comments

Decisions that eroded trust in Azure – by a former Azure Core engineer

https://isolveproblems.substack.com/p/how-microsoft-vaporized-a-trillion
210•axelriet•8h ago•53 comments

Artemis II's toilet is a moon mission milestone

https://www.scientificamerican.com/article/artemis-iis-toilet-is-a-moon-mission-milestone/
104•1659447091•21h ago•37 comments

Cursor 3

https://cursor.com/blog/cursor-3
258•adamfeldman•5h ago•221 comments

Qwen3.6-Plus: Towards real world agents

https://qwen.ai/blog?id=qwen3.6
406•pretext•9h ago•142 comments

Good ideas do not need lots of lies in order to gain public acceptance (2008)

https://blog.danieldavies.com/2004/05/d-squared-digest-one-minute-mba.html
128•sedev•6h ago•56 comments

George Goble has died

https://www.legacy.com/us/obituaries/wlfi/name/george-goble-obituary?id=61144779
94•finaard•5h ago•18 comments

Lemonade by AMD: a fast and open source local LLM server using GPU and NPU

https://lemonade-server.ai
420•AbuAssar•12h ago•94 comments

ParadeDB (YC S23) Is Hiring Database Internal Engineers (Rust)

https://paradedb.notion.site/
1•philippemnoel•1h ago

The Australian government has announced gambling advertising reforms

https://www.bbc.com/news/articles/c62492e925lo
75•gostsamo•5h ago•50 comments

LinkedIn is searching your browser extensions

https://browsergate.eu/
1526•digitalWestie•10h ago•674 comments

JSON Canvas Spec (2024)

https://jsoncanvas.org/spec/1.0/
81•tobr•3d ago•28 comments

Significant progress made on Xbox 360 recompilation

https://readonlymemo.com/rexglue-xbox-360-recompilation-interview/
55•tetrisgm•4d ago•15 comments

Memo: A language that remembers only the last 12 lines of code

https://danieltemkin.com/Esolangs/Memo/
8•notem•1h ago•0 comments

OpenAI Acquires TBPN

https://openai.com/index/openai-acquires-tbpn/
132•surprisetalk•6h ago•119 comments

Prefer do notation over Applicative operators when assembling records (2024)

https://haskellforall.com/2024/05/prefer-do-notation-over-applicative
13•wazHFsRy•2d ago•2 comments

Significant raise of reports

https://lwn.net/Articles/1065620/
272•stratos123•14h ago•145 comments

Inside Nepal's Fake Rescue Racket

https://kathmandupost.com/money/2026/03/27/inside-nepal-s-fake-rescue-racket
244•lode•12h ago•112 comments

Show HN: Made a little Artemis II tracker

https://artemis-ii-tracker.com/
5•codingmoh•47m ago•0 comments

Artemis computer running two instances of MS outlook; they can't figure out why

https://bsky.app/profile/nikigrayson.com/post/3miik2wzosk25
291•mooreds•8h ago•214 comments

IBM Announces Strategic Collaboration with Arm

https://newsroom.ibm.com/2026-04-02-ibm-announces-strategic-collaboration-with-arm-to-shape-the-f...
259•bonzini•15h ago•167 comments

Magic the Gathering Deck Shuffler

https://mtg.jessitron.honeydemo.io/
29•mooreds•3d ago•14 comments

Foxing aspires to be an eBPF-powered replication engine for Linux filesystems

https://codeberg.org/aenertia/foxing
33•tanelpoder•3d ago•4 comments

Queueing Requests Queues Your Capacity Problems, Too

https://pushtoprod.substack.com/p/queueing-requests-queues-your-capacity-problems-too
7•mhawthorne•3d ago•2 comments

'Backrooms' and the Rise of the Institutional Gothic

https://thereader.mitpress.mit.edu/backrooms-and-the-rise-of-the-institutional-gothic/
164•anarbadalov•10h ago•73 comments

Show HN: A P2P messenger with dual network modes (Fast and Tor)

https://github.com/Realman78/Kiyeovo/
27•Realman78•8h ago•16 comments

Sweden goes back to basics, swapping screens for books in the classroom

https://undark.org/2026/04/01/sweden-schools-books/
721•novaRom•13h ago•376 comments

Amazon is adding a fuel surcharge to fees it collects from third-party sellers

https://www.cnbc.com/2026/04/02/amazon-add-3point5percent-fuel-and-logistics-surcharge-for-seller...
126•lehi•5h ago•71 comments

Artemis II will use laser beams to live-stream 4K moon footage at 260 Mbps

https://www.tomshardware.com/networking/artemis-ii-will-use-laser-beams-to-live-stream-4k-moon-fo...
315•speckx•8h ago•139 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.