frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Domain expertise has always been the real moat

https://www.brethorsting.com/blog/2026/05/domain-expertise-has-always-been-the-real-moat/
472•aaronbrethorst•10h ago•290 comments

A Gentle Introduction to Lattice-Based Cryptography [pdf]

https://cryptography101.ca/wp-content/uploads/lattice-based-cryptography.pdf
54•jayhoon•2d ago•0 comments

Ahoy, DECmate II the little PDP-8 that could

http://oldvcr.blogspot.com/2026/05/ahoy-decmate-ii-little-pdp-8-that-could.html
23•TMWNN•2h ago•1 comments

Shantell Sans (2023)

https://shantellsans.com/process
195•aleda145•8h ago•16 comments

Avian Visitors

https://theodore.net/projects/AvianVisitors/
5•fdb•40m ago•0 comments

Associative learning turns DEET from aversive to appetitive in Aedes aegypti

https://journals.biologists.com/jeb/article/229/10/jeb251935/371741/Associative-learning-switches...
16•croes•2d ago•2 comments

I found a seashell in the middle of the desert

https://github.com/Hawzen/I-found-a-seashell-in-the-middle-of-the-desert
291•Hawzen•2d ago•77 comments

Microsoft Office 2019 and 2021 for Mac view-only conversion

https://consumerrights.wiki/w/Microsoft_Office_2019_and_2021_for_Mac_view-only_conversion_(2026)
783•antipurist•7h ago•272 comments

Racket v9.2 is now available

https://blog.racket-lang.org/2026/05/racket-v9-2.html
90•spdegabrielle•2d ago•12 comments

The AV2 Video Standard Has Released (Final v1.0 Specification)

https://av2.aomedia.org
143•ksec•9h ago•39 comments

Accenture to acquire Ookla

https://newsroom.accenture.com/news/2026/accenture-to-acquire-ookla-to-strengthen-network-intelli...
268•Garbage•14h ago•136 comments

Cheese Paper: a text editor specifically designed for writing

https://brie.gay/cheese-paper/
94•sohkamyung•7h ago•21 comments

Voxel Space (2017)

https://s-macke.github.io/VoxelSpace/
274•davikr•16h ago•58 comments

wolfSSL releases a new product; wolfCOSE a zero alloc C embbedded COSE stack

https://github.com/wolfSSL/wolfCOSE
83•aidangarske•10h ago•15 comments

Jef Raskin, the Visionary Behind the Mac (2013)

https://lowendmac.com/2013/jef-raskin-the-visionary-behind-the-mac/
96•tylerdane•11h ago•42 comments

Zig ELF Linker Improvements Devlog

https://ziglang.org/devlog/2026/#2026-05-30
194•kristoff_it•13h ago•57 comments

Mechanical Pencin: A website about the hidden engineering in everyday objects

https://mechanical-pencil.com/
43•Muhammad523•6h ago•6 comments

Openrsync: An implementation of rsync, by the OpenBSD team

https://github.com/kristapsdz/openrsync
364•sph•20h ago•151 comments

Parallel Reconstruction of Lawful TLS Wiretapping

https://remyhax.xyz/posts/reproducing-lawful-tls-wiretapping/
84•jerrythegerbil•11h ago•38 comments

OpenRouter raises $113M Series B

https://openrouter.ai/announcements/series-b
403•freeCandy•13h ago•196 comments

Microcode inside the Intel 8087 floating-point chip: register exchange

https://www.righto.com/2026/05/microcode-inside-intel-8087-floating.html
110•pwg•13h ago•18 comments

Building a LangGraph pipeline for production data engineering

https://labyrinthanalyticsconsulting.com/blog/building-first-langgraph-pipeline
11•labyrinthAC•2h ago•0 comments

Pandoc Templates

https://pandoc-templates.org/
387•ankitg12•20h ago•50 comments

Show HN: 500 years of Joseon court omens as an observability dashboard

https://ajin.im/is/building/omen.ops/
111•poppypetalmask•11h ago•17 comments

Gustav Klimt and Egon Schiele in Conversation (2018)

https://www.theparisreview.org/blog/2018/01/31/the-drawings-of-klimt-and-schiele/
34•rballpug•2d ago•4 comments

Show HN: Komi-learn – continuous memory and self-improvement for coding agents

https://github.com/kurikomi-labs/komi-learn
6•rainxchzed•1h ago•1 comments

90% of the T Distribution

https://entropicthoughts.com/ninety-percent-of-the-t-distribution
47•ibobev•3d ago•13 comments

Zig: Build System Reworked

https://ziglang.org/devlog/2026/#2026-05-26
341•tosh•22h ago•224 comments

Dusklight – GC Twilight Princess Decompiled

https://twilitrealm.dev/
89•shepherdjerred•10h ago•11 comments

Leo's first encyclical attacks technological messianism

https://www.economist.com/europe/2026/05/28/leos-first-encyclical-attacks-technological-messianism
210•1vuio0pswjnm7•20h ago•253 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•1y 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.