frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The Waymo effect: how AI is quietly making research less collaborative

https://www.researchagenda.news/articles/the-waymo-effect.html
217•JohnHammersley•3h ago•158 comments

If coding is solved, what now?: Measuring the sloppiness of code

https://earendil.com/posts/measuring-code-sloppiness/
23•doppp•38m ago•8 comments

Houthis 'take control' of key island in global shipping route

https://www.bbc.com/news/live/cmd683p01eljt
74•consumer451•38m ago•36 comments

RTK reports token savings, but our cost benchmarks disagree

https://quesma.com/blog/does-rtk-make-ai-coding-cheaper/
72•michalwarda•3h ago•40 comments

Logo Programming Language

https://el.media.mit.edu/logo-foundation/what_is_logo/logo_programming.html
19•azhenley•2d ago•2 comments

So you want to use OpenRouter?

https://mmoustafa.com/blog/so-you-want-to-use-openrouter/
349•player85•2d ago•87 comments

Cherenkov Radiation - traveling faster than light

http://www.iaea.org/newscenter/news/what-is-cherenkov-radiation
147•andsoitis•5h ago•75 comments

Shopify is moving from React Native back to Swift and Kotlin

https://shopify.engineering/back-to-native
1161•fnthawar2•1d ago•846 comments

Show HN: ClaudeStatsBar: your session is 486k deep and nothing told you

https://github.com/Field-Logic-Ltd/ClaudeStatsBar
8•edf13•36m ago•3 comments

Re-Engineering YouTube for the Living Room: Bringing "Chrobalt" to RDK

https://www.collabora.com/news-and-blog/news-and-events/re-engineering-youtube-for-the-living-roo...
5•losgehts•38m ago•0 comments

iPod Classic 6G in QEMU

https://www.reddit.com/r/emulation/s/VL4Au2HGxq
77•dmonterocrespo•2d ago•12 comments

Don't let anyone take away your big box of cables

https://blog.jim-nielsen.com/2026/hands-off-my-cables/
651•Brajeshwar•22h ago•403 comments

RISC-V Emulator and Linux System from Scratch

https://github.com/WerWolv/riscv-emulator
21•Bluestein•3d ago•2 comments

Diesel prices in U.S. top $6 a gallon for first time

https://www.cbsnews.com/news/rising-diesel-prices-consumer-impact/
60•ck2•45m ago•63 comments

Experiment – Projectional Viewer

https://programmingsimplicity.substack.com/p/experiment-projectional-viewer
8•surprisetalk•3d ago•1 comments

Ask HN: Can we please limit the AI news flood?

268•cromka•1h ago•155 comments

CSS Curiosities of the Past

https://vale.rocks/posts/css-relics
43•robin_reala•6h ago•23 comments

OpenAI Agents API

https://developers.openai.com/api/docs/guides/agents-api/overview
302•aquir•18h ago•160 comments

Working with Git Worktrees in Magit

https://emacsredux.com/blog/2026/09/02/working-with-git-worktrees-in-magit/
82•srijan4•3d ago•33 comments

Claude is no longer available for minors

https://support.claude.com/en/articles/15171100-age-assurance-on-claude
225•Muhammad523•3h ago•300 comments

Technique for Manipulating Satellite Photos Now Reveals Ancient Images (2025)

https://spinoff.nasa.gov/Manipulating_Satellite_Photos_Now_Reveals_Ancient_Images
357•gumby•22h ago•57 comments

Mexican student creates an acoustic fire extinguisher to put out fire in seconds

https://www.upsocl.com/en/16-year-old-mexican-student-creates-an-acoustic-fire-extinguisher-that-...
297•rguiscard•13h ago•95 comments

The Deathray: A simple way for an untrusted site to freeze a Mac

https://auberon.xyz/blog/posts/deathray/
238•auberonedu•18h ago•159 comments

An interactive tour of the spanning tree protocol

https://vincent.bernat.ch/en/blog/2026-spanning-tree
38•zdw•3d ago•4 comments

More questions about whether researchers can trust OpenAI with unpublished math

https://mathstodon.xyz/@andreasthom/117240535270608201
837•pred_•1d ago•780 comments

Music Theory for the 21st-Century Classroom

https://musictheory.pugetsound.edu/mt21c/MusicTheory.html
254•aanet•21h ago•118 comments

NTSB issues investigative update on B-767 runway excursion accident in Miami

https://www.ntsb.gov:443/news/press-releases/Pages/NR20260909.aspx
130•mckn1ght•16h ago•228 comments

Nine coding harnesses vs. your laptop

https://nasutton.notion.site/Nine-coding-harnesses-vs-your-laptop-3d139990182b80d59fa3cf500f0450b...
139•nasutton12•15h ago•46 comments

Neki – Sharded Postgres

https://planetscale.com/blog/introducing-neki
258•simon_weber•22h ago•140 comments

Forgejo <=16.0.3 Critical RCE

https://codeberg.org/forgejo/forgejo/src/branch/forgejo/release-notes-published/16.0.4.md
199•weierstass•22h ago•77 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.