frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Project Gutenberg – keeps getting better

https://www.gutenberg.org/
374•JSeiko•3h ago•114 comments

A 0-click exploit chain for the Pixel 10

https://projectzero.google/2026/05/pixel-10-exploit.html
241•happyhardcore•5h ago•99 comments

Bun Rust rewrite: "codebase fails basic miri checks, allows for UB in safe rust"

https://github.com/oven-sh/bun/issues/30719
183•ndiddy•2h ago•107 comments

I designed a nibble-oriented CPU in Verilog to build a scientific calculator

https://github.com/gdevic/FPGA-Calculator
39•gdevic•2h ago•4 comments

U.S. DOJ demands Apple and Google unmask over 100k users of car-tinkering app

https://macdailynews.com/2026/05/15/u-s-doj-demands-apple-and-google-unmask-over-100000-users-of-...
146•tencentshill•1h ago•74 comments

Image-blaster: Creates 3D environments, SFX, and meshes from a single image

https://github.com/neilsonnn/image-blaster
56•MattRogish•3h ago•11 comments

I built Zenith: a live local-first fixed viewport planetarium

https://smorgasb.org/zenith-tech/
47•surprisetalk•3h ago•7 comments

Show HN: Watch a neural net learn to play Snake

https://ppo.gradexp.xyz/
67•c1b•1d ago•16 comments

O(x)Caml in Space

https://gazagnaire.org/blog/2026-05-14-borealis.html
200•yminsky•8h ago•46 comments

Explore Wikipedia Like a Windows XP Desktop

https://explorer.samismith.com/
412•smusamashah•10h ago•104 comments

Hightouch (YC S19) Is Hiring

https://hightouch.com/careers
1•joshwget•2h ago

ASCII by Jason Scott

https://ascii.textfiles.com/
101•bookofjoe•5h ago•19 comments

Radicle: Sovereign {code forge} built on Git

https://radicle.dev/
172•KolmogorovComp•7h ago•45 comments

High dimensional geometry is transforming the MRI industry (2017) [pdf]

https://www.ams.org/government/DonohoPresentation06-28-17Final.pdf
65•nill0•5h ago•23 comments

Feedr v0.8.0 – a TUI RSS reader, now read the full article from your terminal

https://github.com/bahdotsh/feedr
12•bahdotshxx•1h ago•4 comments

A new book on Steve Jobs at NeXT

https://spectrum.ieee.org/steve-jobs-next-computer
132•rbanffy•8h ago•113 comments

Amazon workers under pressure to up their AI usage are making up tasks

https://www.fastcompany.com/91541586/amazon-workers-pressured-to-up-ai-use-extraneous-tasks
244•hackernj•5h ago•242 comments

Show HN: Sx – an open-source package manager for AI skills, MCPs, and commands

https://github.com/sleuth-io/sx
16•detkin•2h ago•5 comments

The nuclear-physics infrastructure behind PET scans

https://www.lanl.gov/media/publications/1663/proton-power-for-public-health
3•LAsteNERD•2d ago•0 comments

Waymo recalls 3,800 robotaxis after they drive into flood waters

https://www.cnbc.com/2026/05/12/waymo-recalls-3800-robotaxis-after-able-drive-into-standing-water...
39•drob518•1h ago•42 comments

A few words on DS4

https://antirez.com/news/165
401•caust1c•20h ago•168 comments

ABC News has taken all FiveThirtyEight articles offline

https://twitter.com/baseballot/status/2055309076209492208
8•cmsparks•12m ago•1 comments

Ask HN: How to be SOC2 Type 2 compliant as a solo-entreprenuer?

95•sochix•12h ago•89 comments

We don't know why Malawi is poor

https://newsletter.deenamousa.com/p/we-dont-know-why-malawi-is-poor
69•alphabetatango•2h ago•74 comments

Details of the Daring Airdrop at Tristan Da Cunha

https://www.tristandc.com/government/news-2026-05-11-airdrop.php
239•kspacewalk2•15h ago•90 comments

NanoTDB – Golang Append-Only Time Series DB

https://github.com/aymanhs/nanotdb
45•aymanhs72•8h ago•6 comments

Building ML framework with Rust and Category Theory

https://hghalebi.github.io/category_theory_transformer_rs/
86•adamnemecek•1d ago•19 comments

First public macOS kernel memory corruption exploit on Apple M5

https://blog.calif.io/p/first-public-kernel-memory-corruption
426•quadrige•1d ago•116 comments

Codex is now in the ChatGPT mobile app

https://openai.com/index/work-with-codex-from-anywhere/
450•mikeevans•23h ago•226 comments

New Nginx Exploit

https://github.com/DepthFirstDisclosures/Nginx-Rift
427•hetsaraiya•1d ago•97 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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