frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The labor share of income in the US is at its lowest post-war level

https://libertystreeteconomics.newyorkfed.org/2026/06/the-post-covid-decline-in-the-labor-share/
107•loughnane•21m ago•23 comments

Looking Ahead to Postgres 19

https://www.snowflake.com/en/blog/engineering/postgresql-19-features-beta/
95•thinkingemote•1h ago•53 comments

Memoirs of Extraordinary Popular Delusions and the Madness of Crowds (1852)

https://www.gutenberg.org/ebooks/24518
95•lstodd•3h ago•22 comments

Building a custom octocopter from scratch with no prior hardware experience

https://karolina.mgdubiel.com/drone/
214•noleary•2d ago•49 comments

European digital ID wallets rely on safety services of Google and Apple

https://waag.org/en/article/european-digital-id-wallets-are-gift-google-and-apple/
546•donohoe•5h ago•231 comments

Open Source Low Tech

https://opensourcelowtech.org/
477•grep_it•4d ago•101 comments

Knoppix

https://www.knopper.net/knoppix/index-en.html
53•hoangvmpc•3h ago•31 comments

Zluda 6 release (run unmodified CUDA applications on non-Nvidia GPUs)

https://vosen.github.io/ZLUDA/blog/zluda-update-q1q2-2026/
71•Tiberium•5h ago•6 comments

Claude Code Is Steganographically Marking Requests

https://thereallo.dev/blog/claude-code-prompt-steganography
5•kirushik•11m ago•0 comments

Qwen 3.6 27B is the sweet spot for local development

https://quesma.com/blog/qwen-36-is-awesome/
1056•stared•22h ago•682 comments

Exercise intensity influences body composition in healthy older adults (2025)

https://www.maturitas.org/article/S0378-5122(25)00571-7/fulltext
136•bookofjoe•5h ago•110 comments

We moved our Bluesky data to Eurosky

https://waag.org/en/article/why-we-moved-our-bluesky-data-eurosky/
28•dotcoma•39m ago•11 comments

.self: A new top-level domain designed to support self-hosting

https://hccf.onmy.cloud/2026/06/21/reclaiming-our-digital-selves-hccfs-vision-for-a-human-centere...
596•HumanCCF•20h ago•342 comments

Free the Icons

https://weblog.rogueamoeba.com/2026/06/26/free-the-icons/
592•zdw•3d ago•216 comments

Mathematics: Its Content, Methods and Meaning

https://old.maa.org/press/maa-reviews/mathematics-its-content-methods-and-meaning
12•teleforce•3d ago•3 comments

Parse, Don't Validate – In a Language That Doesn't Want You To

https://cekrem.github.io/posts/parse-dont-validate-typescript/
100•fagnerbrack•5h ago•79 comments

Memory Safe Context Switching

https://fil-c.org/context_switches
174•modeless•15h ago•28 comments

Who are the fire-tamers?

https://aeon.co/essays/who-are-the-fire-taming-healers-of-modern-france
23•Caiero•1d ago•15 comments

All Logic, No Bite

https://lcamtuf.substack.com/p/all-logic-no-bite
34•surprisetalk•3d ago•7 comments

I'm building a Space Cadet Pinball Machine! [video]

https://www.youtube.com/watch?v=lHQ8c8i42VE
33•skibz•3d ago•7 comments

LongCat-2.0, a large-scale MoE model with 1.6T total and 48B Active

https://longcat.chat/blog/longcat-2.0/
217•benjiro29•15h ago•60 comments

Rocketlab acquires Iridium

https://investors.rocketlabcorp.com/news-releases/news-release-details/rocket-lab-acquire-iridium...
442•everfrustrated•1d ago•293 comments

Linux for the Sega MegaDrive

https://github.com/LinuxMD/linuxmd
180•HardwareLust•1d ago•45 comments

Why problem statements aren't enough

https://letters.unchartedpathbreakthroughs.com/posts/why-problem-statements-arent-enough
27•mooreds•4d ago•5 comments

One million passports leaked online

https://www.theverge.com/tech/947157/passports-data-breach-cannabis-club-systems-nefos-puffpal
385•jruohonen•2d ago•221 comments

Old Computer Challenge

http://occ.sdf.org/
95•wrxd•2d ago•52 comments

Ornith-1.0: self-improving open-source models for agentic coding

https://github.com/deepreinforce-ai/Ornith-1
244•danboarder•22h ago•45 comments

Exploring PDP-1 Lisp (1960)

https://obsolescence.dev/pdp1-lisp-introduction.html
99•ozymandiax•14h ago•23 comments

The US ambassador had Belgian police stop our reporting

https://europeancorrespondent.com/en/r/the-us-ambassador-had-belgian-police-stop-our-reporting
586•robtherobber•5h ago•236 comments

How to corrupt an SQLite database file

https://www.sqlite.org/howtocorrupt.html
139•tosh•3d ago•35 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.