frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

GPT-5.6 used a prompt to close a 30-year gap in convex optimization

https://old.reddit.com/r/math/comments/1uxj3cy/after_openais_cdc_proof_announcement_gpt56_used_a/
384•mbustamanter•6h ago•234 comments

The Kimi K3 Moment

https://stephen.bochinski.dev/blog/2026/07/18/the-kimi-k3-moment/
54•sbochins•2h ago•41 comments

Gleam Is Now on Tangled

https://tangled.org/gleam.run/gleam
125•nerdypepper•3h ago•74 comments

Goodbye, and Thanks for All the Bikesheds

https://queue.acm.org/detail.cfm?id=3818307
116•Ygg2•2h ago•97 comments

If You Build It, They Will Come

https://www.benlandautaylor.com/p/if-you-build-it-they-will-come
90•barry-cotter•4h ago•33 comments

Is this the end of the once-mighty GoPro?

https://amateurphotographer.com/latest/photo-news/going-going-gone-is-this-the-end-of-the-once-mi...
144•aanet•3d ago•257 comments

Our Approach to Bioresilience: Isomorphic Labs and Google DeepMind

https://deepmind.google/blog/our-approach-to-bioresilience/
35•bookofjoe•3h ago•18 comments

Elixir-lang.org has a new design

https://elixir-lang.org/
101•bbg2401•4h ago•68 comments

Setting up your spare Mac for Claude Code to control, a step-by-step guide

https://ykdojo.github.io/claude-controls-mac/
104•ykev•3h ago•77 comments

Fable 5 vs. GPT-5.6 Sol on an NP-Hard Problem: Does /goal help?

https://charlesazam.com/blog/fable-5-gpt-5-6-sol-goal/
169•couAUIA•8h ago•86 comments

REO Trucks I4 4WD Pickup Truck Starts at $21,500

https://reotrucks.com
51•b_mc2•1h ago•55 comments

Regressive JPEGs

https://maurycyz.com/projects/bad_jpeg/
599•vitaut•16h ago•62 comments

LG monitors silently install software through Windows Update without consent

https://videocardz.com/newz/lg-monitors-silently-install-software-through-windows-update-without-...
817•baranul•9h ago•409 comments

What's the deal with all the random weekly quota resets for agents lately?

https://minimaxir.com/2026/07/agent-quota-reset/
10•minimaxir•35m ago•2 comments

Tech note: making your own V-I plots at home

https://lcamtuf.substack.com/p/tech-note-making-your-own-v-i-plots
45•zdw•23h ago•7 comments

A Second-Grade Teacher Revived a Beloved Video Game

https://www.nytimes.com/2026/07/13/style/backyard-baseball-video-game-teacher.html
39•danso•5d ago•15 comments

I'm Making Strandfall, a Solarpunk Orienteering Larp

https://mssv.net/2026/04/29/im-making-strandfall-a-solarpunk-orienteering-larp/
6•surprisetalk•5d ago•0 comments

Show HN: Q3Edit – Edit and play Quake 3 maps in the browser

https://q3edit.com
34•drdator•4h ago•8 comments

Show HN: Get alerts for good seats at 70mm IMAX showings of The Odyssey

https://imaxxing.io/
14•andrewtorkbaker•1h ago•11 comments

What AI did to stackoverflow in a graph

https://data.stackexchange.com/stackoverflow/query/1953768#graph
305•secretslol•8h ago•362 comments

How GitHub gave every repository a durable owner

https://github.blog/security/application-security/how-github-gave-every-repository-a-durable-owner/
38•ascertain•1w ago•5 comments

Thanks HN for 15 years of support and helping me find my life's work

769•nicholasjbs•1d ago•97 comments

The Fermi Paradox, Percolation, and Inbreeding

https://reactormag.com/the-fermi-paradox-percolation-and-inbreeding/
19•bryanrasmussen•4h ago•25 comments

GTX 1080s: Testing a Legend

https://www.lttlabs.com/articles/2026/07/15/gtx-1080s-revisiting-legends
52•LabsLucas•2d ago•18 comments

The Computer at the Bottom of a Canal

https://negroniventurestudios.com/2026/07/18/the-computer-at-the-bottom-of-a-canal/
117•Kudos•11h ago•27 comments

Reviving a 15-year-old netbook with Arch Linux

https://parksb.github.io/en/article/41.html
198•parksb•4d ago•134 comments

Fake food delivery site for the dopamine

https://old.reddit.com/r/BingeEatingDisorder/comments/1uzr3ui/fake_food_delivery_site_for_the_dop...
64•guerrilla•3h ago•28 comments

No link between acetaminophen use during pregnancy and adverse birth outcomes

https://sph.unc.edu/sph-news/no-link-between-acetaminophen-use-during-pregnancy-and-adverse-birth...
46•geox•3h ago•25 comments

Qubes OS Security in the Public Record

https://arxiv.org/abs/2607.14587
65•sciences44•10h ago•9 comments

British runner Josh Kerr breaks world record for mile which stood for 27 years

https://news.sky.com/story/british-runner-josh-kerr-breaks-world-record-for-mile-which-had-stood-...
74•austinallegro•4h ago•49 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.