frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Markets are competitive if and only if P = NP

https://arxiv.org/abs/2602.20415
53•kscarlet•35m ago•25 comments

Half-Baked Product

https://weli.dev/blog/half-baked-product/
870•weli•7h ago•260 comments

Jamesob's guide to running SOTA LLMs locally

https://github.com/jamesob/local-llm
25•livestyle•1h ago•6 comments

PostgreSQL and the OOM Killer: Why We Use Strict Memory Overcommit

https://www.ubicloud.com/blog/postgresql-and-the-oom-killer-why-we-use-strict-memory-overcommit
75•furkansahin•3h ago•19 comments

America, 1926: What a Forgotten 100-Year-Old Report Says About Who We Are

https://www.derekthompson.org/p/america-1926-an-absurdly-deep-dive
12•momentmaker•1h ago•0 comments

Give Smart People the Tools to Do Smart Things

https://superuserdone.com/posts/2026-07-03-give-smart-people-the-tools/
16•SuperUserDone•1h ago•5 comments

Valve open source the Steam Machine e-ink screen so you can make your own

https://www.gamingonlinux.com/2026/07/valve-open-source-the-steam-machine-e-ink-screen-so-you-can...
234•ahlCVA•3h ago•32 comments

Hunting a 16-year-old SQLite WAL bug with TLA+

https://ubuntu.com/blog/hunting-a-16-year-old-sqlite-bug-with-tla-is-dqlite-affected
34•peterparker204•3d ago•2 comments

Wordgard: The new in-browser rich-text editor from the creator of ProseMirror

https://wordgard.net/
142•indy•7h ago•67 comments

Best Simple System for Now

https://dannorth.net/blog/best-simple-system-for-now/
13•daan-k•1h ago•2 comments

Right to Local Intelligence

https://righttointelligence.org/
412•thoughtpeddler•16h ago•143 comments

The Fall and Rise of Screwworm

https://www.construction-physics.com/p/the-fall-and-rise-of-screwworm
39•crescit_eundo•3h ago•15 comments

Factories Are Just Rooms

https://interconnected.org/home/2026/07/03/factories
13•arbesman•1h ago•1 comments

CarPlay Is Additive

https://www.caseyliss.com/2026/7/2/carplay-is-additive-you-dolts
464•sprawl_•15h ago•621 comments

Anatomy of Persistent Memory's 3 Layers: Comparing ContextNest, Mem0 and Zep

https://promptowl.ai/resources/persistent-memory-ai-agents/
6•sparkystacey•1h ago•0 comments

The Safari MCP server for web developers

https://webkit.org/blog/18136/introducing-the-safari-mcp-server-for-web-developers/
198•coloneltcb•14h ago•56 comments

How working with a blind client revealed invisible accessibility gaps

https://iinteractive.com/resources/blog/read-only
64•fortyseven•3d ago•49 comments

crustc: entirety of `rustc`, translated to C

https://github.com/FractalFir/crustc
346•Philpax•17h ago•73 comments

Since Linux 6.9, LUKS suspend stopped wiping disk-encryption keys from memory

https://mathstodon.xyz/@iblech/116769502749142438
515•IngoBlechschmid•1d ago•217 comments

Commodore 64 Basic for PostgreSQL

https://thombrown.blogspot.com/2026/07/load-plcbmbasic81-commodore-64-basic.html
41•hans_castorp•7h ago•8 comments

My Dad Helped Build North America's Oat Supply Chain: Can It Be Remade?

https://ambrook.com/offrange/perspective/how-we-lost-our-oats
6•surprisetalk•3d ago•1 comments

Reality has a surprising amount of detail (2017)

https://johnsalvatier.org/blog/2017/reality-has-a-surprising-amount-of-detail
338•vinhnx•5d ago•124 comments

Quake in 13 Kilobytes (2021)

https://js13kgames.com/games/q1k3
104•mortenjorck•6d ago•14 comments

Local Reasoning for Global Properties

https://tratt.net/laurie/blog/2026/local_reasoning_for_global_properties.html
20•mpweiher•2d ago•2 comments

Hackers shoveled snow for company, were rewarded with network admin access

https://www.theregister.com/security/2026/07/02/hackers-shoveled-snow-for-company-were-rewarded-w...
48•ike_usawa•2h ago•21 comments

Program-as-Weights: A Programming Paradigm for Fuzzy Functions

https://arxiv.org/abs/2607.02512
12•simonpure•3h ago•1 comments

Alibaba to ban Claude Code in workplace over alleged backdoor risks, source says

https://www.reuters.com/world/china/alibaba-ban-claude-code-workplace-over-alleged-backdoor-risks...
260•nsoonhui•7h ago•216 comments

Exapunks (2018)

https://www.zachtronics.com/exapunks/
315•yu3zhou4•21h ago•108 comments

Show HN: TaskPeace – a task queue my AI coding agents pull work from over MCP

https://taskpeace.com/
3•JulianQuinn•1h ago•1 comments

Gemini Code Assist will be shut down on July 17

https://docs.cloud.google.com/gemini/docs/code-review/review-repo-code
43•ushakov•3h ago•31 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.