frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Click (2016)

https://clickclickclick.click/
207•andrewzeno•3h ago•44 comments

Anthropic co-founder to present AI encyclical alongside Pope Leo XIV

https://www.vaticannews.va/en/pope/news/2026-05/pope-leo-xiv-first-encyclical-magnifica-humanitas...
114•cucho•3h ago•69 comments

Anthropic acquires Stainless

https://www.anthropic.com/news/anthropic-acquires-stainless
370•tomeraberbach•9h ago•255 comments

Hyperpolyglot Lisp: Common Lisp, Racket, Clojure, Emacs Lisp

https://hyperpolyglot.org/lisp
134•veqq•7h ago•28 comments

We stopped AI bot spam in our GitHub repo using Git's –author flag

https://archestra.ai/blog/only-responsible-ai
419•ildari•11h ago•190 comments

Regex Chess: A 2-ply minimax chess engine in 84,688 regular expressions

https://nicholas.carlini.com/writing/2025/regex-chess.html
9•surprisetalk•4d ago•0 comments

We let AIs run radio stations

https://andonlabs.com/blog/andon-fm
176•lukaspetersson•8h ago•162 comments

The Quiet Renovation at Bitwarden

https://blog.ppb1701.com/the-quiet-renovation-at-bitwarden
539•DaSHacka•2d ago•247 comments

Show HN: Files.md – Open-source alternative to Obsidian

https://github.com/zakirullin/files.md
557•zakirullin•12h ago•281 comments

Show HN: Number Gacha, a gacha game distilled to its essence

https://isabisabel.com/gacha/
51•babel16•5d ago•18 comments

Earth's Radio Bubble: Every signal we've ever sent into space

https://www.thescientificdrop.com/2026/05/earths-radio-bubble-every-signal-weve.html
32•jonbaer•17h ago•23 comments

Project Glasswing: what Mythos showed us

https://blog.cloudflare.com/cyber-frontier-models/
290•Fysi•12h ago•108 comments

Elon Musk has lost his lawsuit against Sam Altman and OpenAI

https://techcrunch.com/2026/05/18/elon-musk-has-lost-his-lawsuit-against-sam-altman-and-openai/
802•nycdatasci•8h ago•421 comments

The Futility of Lava Lamps: What Random Means

https://loup-vaillant.fr/articles/lava-lamps-and-randomness
52•birdculture•2d ago•37 comments

Agora-1: The Multi-Agent World Model

https://odyssey.ml/introducing-agora-1
83•olivercameron•7h ago•16 comments

When can the C++ compiler devirtualize a call?

https://quuxplusone.github.io/blog/2021/02/15/devirtualization/
15•lionkor•1d ago•1 comments

Designing an FPGA Calculator from Scratch

https://baltazarstudios.com/calculator/
51•zdw•1d ago•5 comments

Two computers, one monitor, zero fiddling (2025)

https://alexplescan.com/posts/2025/08/16/kvm/
176•ankitg12•3d ago•97 comments

The FBI Wants to Buy Nationwide Access to License Plate Readers

https://www.404media.co/the-fbi-wants-to-buy-nationwide-access-to-license-plate-readers/
230•cdrnsf•6h ago•92 comments

The Fil-C Optimized Calling Convention

https://fil-c.org/calling_convention
115•pizlonator•2d ago•21 comments

Coding on Paper

https://wickstrom.tech/2026-05-16-coding-on-paper.html
44•owickstrom•1d ago•8 comments

Loopmaster – Livecoding Music IDE

https://loopmaster.xyz/
71•stagas•7h ago•19 comments

Show HN: InsForge – Open-source Heroku for coding agents

https://github.com/InsForge/InsForge
34•mrcoldbrew•10h ago•6 comments

Cutting inference cold starts by 40x with LP, FUSE, C/R, and CUDA-checkpoint

https://modal.com/blog/truly-serverless-gpus
73•charles_irl•8h ago•16 comments

Alignment pretraining: AI discourse creates self-fulfilling (mis)alignment

https://arxiv.org/abs/2601.10160
25•anigbrowl•4h ago•10 comments

Iran starts Bitcoin-backed ship insurance for Hormuz strait

https://www.bloomberg.com/news/articles/2026-05-18/iran-starts-bitcoin-backed-shipping-insurance-...
266•srameshc•9h ago•437 comments

Shutterstock to pay $35M over hard-to-cancel subscriptions

https://www.ftc.gov/news-events/news/press-releases/2026/05/shutterstock-pay-35-million-settle-ft...
136•Lihh27•6h ago•62 comments

What Is Date:Italy?

http://aesthetikx.info/blog/date_italy.html
133•jollyjerry•2d ago•54 comments

Understanding Singleflight in Go

https://www.codingexplorations.com/blog/understanding-singleflight-in-golang-a-solution-for-elimi...
55•ghostbit•2d ago•8 comments

Microsoft surprises with its first server Linux distribution: Azure Linux 4.0

https://www.zdnet.com/article/microsoft-releases-its-first-server-linux-distribution-azure-linux-...
19•CrankyBear•2h ago•5 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•12mo 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.