frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Vercel says internal systems hit in breach

https://decipher.sc/2026/04/19/vercel-says-internal-systems-hit-in-breach/
307•whiteyford•3h ago•68 comments

Archive of Byte magazine, starting with issue #1 in 1975

https://archive.org/details/byte-magazine-1975-09
455•DamnInteresting•2d ago•112 comments

Show HN: Faceoff – A terminal UI for following NHL games

https://www.vincentgregoire.com/faceoff/
31•vcf•1h ago•14 comments

The Bromine Chokepoint: How Strife Could Halt Production of World’s Memory Chips

https://warontherocks.com/cogs-of-war/the-bromine-chokepoint-how-strife-in-the-middle-east-could-...
19•crescit_eundo•1h ago•3 comments

Notion leaks email addresses of all editors of any public page

https://twitter.com/weezerOSINT/status/2045849358462222720
191•Tiberium•3h ago•55 comments

Nanopass Framework: Clean Compiler Creation Language

https://nanopass.org/
90•NordStreamYacht•4d ago•17 comments

Game devs explain the tricks involved with letting you pause a game

https://kotaku.com/video-game-devs-explain-how-pausing-works-and-sometimes-it-gets-weird-2000686339
351•speckx•3d ago•192 comments

The seven programming ur-languages (2022)

https://madhadron.com/programming/seven_ur_languages.html
204•helloplanets•11h ago•81 comments

KTaO3-Based Supercurrent Diode

https://pubs.acs.org/doi/10.1021/acs.nanolett.5c05590
10•PaulHoule•3d ago•0 comments

SPEAKE(a)R: Turn Speakers to Microphones for Fun and Profit [pdf] (2017)

https://www.usenix.org/system/files/conference/woot17/woot17-paper-guri.pdf
136•Eridanus2•10h ago•60 comments

Uber's AI Push Hits a Wall–CTO Says Budget Struggles Despite $3.4B Spend

https://finance.yahoo.com/sectors/technology/articles/ubers-anthropic-ai-push-hits-223109852.html
18•dakiol•1h ago•14 comments

Show HN: Shader Lab, like Photoshop but for shaders

https://eng.basement.studio/tools/shader-lab
109•ragojose•3d ago•27 comments

What are skiplists good for?

https://antithesis.com/blog/2026/skiptrees/
228•mfiguiere•2d ago•48 comments

College instructor turns to typewriters to curb AI-written work

https://sentinelcolorado.com/uncategorized/a-college-instructor-turns-to-typewriters-to-curb-ai-w...
419•gnabgib•1d ago•378 comments

Reading Input from an USB RFID Card Reader

https://kevwe.com/blog/usb-rfid-reader
18•kevwedotse•2d ago•4 comments

NIST scientists create 'any wavelength' lasers

https://www.nist.gov/news-events/news/2026/04/any-color-you-nist-scientists-create-any-wavelength...
392•rbanffy•22h ago•175 comments

Claude Brain

https://github.com/memvid/claude-brain
14•DeathArrow•3h ago•0 comments

Reverse Engineering ME2's USB with a Heat Gun and a Knife

https://github.com/coremaze/ME2-Writeup
17•Bawoosette•1d ago•1 comments

Show HN: Prompt-to-Excalidraw demo with Gemma 4 E2B in the browser (3.1GB)

https://teamchong.github.io/turboquant-wasm/draw.html
60•teamchong•7h ago•25 comments

Anonymous request-token comparisons from Opus 4.6 and Opus 4.7

https://tokens.billchambers.me/leaderboard
590•anabranch•1d ago•554 comments

Notes from the SF Peptide Scene

https://12gramsofcarbon.com/p/notes-from-the-sf-peptide-scene
95•theahura•4h ago•73 comments

The electromechanical angle computer inside the B-52 bomber's star tracker

https://www.righto.com/2026/04/B-52-star-tracker-angle-computer.html
396•NelsonMinar•1d ago•101 comments

Why Japan has such good railways

https://worksinprogress.co/issue/why-japan-has-such-good-railways/
515•RickJWagner•1d ago•479 comments

When moving fast, talking is the first thing to break

https://daverupert.com/2026/04/more-talk-less-grok/
79•Brajeshwar•4h ago•38 comments

Turtle WoW classic server announces shutdown after Blizzard wins injunction

https://www.pcgamer.com/games/world-of-warcraft/turtle-wow-classic-server-announces-shutdown-afte...
87•Brajeshwar•3h ago•62 comments

Minimal Viable Programs (2014)

https://joearms.github.io/published/2014-06-25-minimal-viable-program.html
32•bachmeier•4d ago•6 comments

Ask HN: How did you land your first projects as a solo engineer/consultant?

207•modelcroissant•9h ago•96 comments

The world in which IPv6 was a good design (2017)

https://apenwarr.ca/log/20170810
168•signa11•16h ago•69 comments

Binary GCD

https://en.algorithmica.org/hpc/algorithms/gcd/#binary-gcd
64•tosh•10h ago•1 comments

It's cool to care (2025)

https://alexwlchan.net/2025/cool-to-care/
73•surprisetalk•4d ago•34 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•11mo 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.