frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Kimi K2.6 just beat Claude, GPT-5.5, and Gemini in a coding challenge

https://thinkpol.ca/2026/04/30/an-open-weights-chinese-model-just-beat-claude-gpt-5-5-and-gemini-...
158•bazlightyear•2h ago•72 comments

Clandestine network smuggling Starlink tech into Iran to beat internet blackout

https://www.bbc.com/news/articles/cvgzk91leweo
134•1659447091•4h ago•63 comments

A Couple Million Lines of Haskell: Production Engineering at Mercury

https://blog.haskell.org/a-couple-million-lines-of-haskell/
134•unignorant•6h ago•55 comments

This Month in Ladybird - April 2026

https://ladybird.org/newsletter/2026-04-30/
248•richardboegli•9h ago•41 comments

The IBM Granite 4.1 family of models

https://research.ibm.com/blog/granite-4-1-ai-foundation-models
39•wglb•2d ago•4 comments

Six Years Perfecting Maps on WatchOS

https://www.david-smith.org/blog/2026/04/29/maps-on-watchos/
244•valzevul•9h ago•53 comments

Dav2d

https://code.videolan.org/videolan/dav2d
420•dabinat•12h ago•120 comments

Neanderthals ran 'fat factories' 125,000 years ago (2025)

https://www.universiteitleiden.nl/en/news/2025/07/neanderthals-ran-fat-factories-125000-years-ago
148•andsoitis•9h ago•52 comments

Do_not_track

https://donottrack.sh/
265•RubyGuy•12h ago•87 comments

Windows API Is Successful Cross-Platform API

https://retrocoding.net/windows-api-is-successful-cross-platform-api
55•phendrenad2•3h ago•39 comments

VS Code inserting 'Co-Authored-by Copilot' into commits regardless of usage

https://github.com/microsoft/vscode/pull/310226
1037•indrora•10h ago•492 comments

The Reality of Being a Man in Your 50s in South Korea

https://indignified.com/the-hidden-realities-of-midlife-masculinity-in-south-korea/
3•ZguideZ•58m ago•1 comments

Inventions for battery reuse and recycling increase seven-fold in last decade

https://www.epo.org/en/news-events/news/inventions-battery-reuse-and-recycling-increase-more-seve...
182•JeanKage•2d ago•11 comments

Maryland Is First to Ban A.I.-Driven Price Increases in Grocery Stores

https://www.nytimes.com/2026/05/01/business/surveillance-pricing-groceries-maryland.html
115•doener•4h ago•61 comments

Clojurists Together – Q2 2026 Open Source Funding Announcement

https://www.clojuriststogether.org/news/q2-2026-funding-announcement/
83•dragandj•8h ago•8 comments

The agent harness belongs outside the sandbox

https://www.mendral.com/blog/agent-harness-belongs-outside-sandbox
90•shad42•9h ago•69 comments

San Francisco streets with confusingly similar names

https://j-nelson.net/san-francisco-streets-with-similar-names/
9•SeenNotHeard•2d ago•12 comments

A more efficient implementation of Shor's algorithm

https://lwn.net/Articles/1066156/
54•signa11•1d ago•7 comments

Care Homes and Hotels in Japan Shut as Expansion Strategy Unravels

https://www.newsonjapan.com/article/149075.php
22•mikhael•4h ago•2 comments

Show HN: State of the Art of Coding Models, According to Hacker News Commenters

https://hnup.date/hn-sota
87•yunusabd•8h ago•43 comments

A Physics Engine with Incremental Rollback for Multiplayer Games

https://easel.games/blog/2026-rollback-physics
71•BSTRhino•1d ago•22 comments

How fast is a macOS VM, and how small could it be?

https://eclecticlight.co/2026/05/02/how-fast-is-a-macos-vm-and-how-small-could-it-be/
237•moosia•20h ago•86 comments

Simple and Correct Snapshot Isolation

https://remy.wang/blog/si.html
15•remywang•2d ago•1 comments

When Dawkins met Claude – Could this AI be conscious?

https://unherd.com/2026/04/is-ai-the-next-phase-of-evolution/
19•pentestercrab•1d ago•94 comments

Open source does not imply open community

https://blog.feld.me/posts/2026/04/open-source-does-not-imply-open-community/
115•RohanAdwankar•3h ago•26 comments

Barman – Backup and Recovery Manager for PostgreSQL

https://github.com/EnterpriseDB/barman
151•nateb2022•3d ago•23 comments

NetHack 5.0.0

https://nethack.org/v500/release.html
426•rsaarelm•12h ago•130 comments

Little Magazines Are Back

https://wsjfreeexpression.substack.com/p/little-magazines-are-back
81•prismatic•2d ago•28 comments

Dabbling in Erlang, part 2: A minimal introduction (2013)

https://agis.io/post/dabbling-in-erlang-a-minimal-introduction/
23•pasxizeis•21h ago•2 comments

The USB Situation

https://randsinrepose.com/archives/the-usb-situation/
116•herbertl•3d ago•130 comments
Open in hackernews

EM-LLM: Human-Inspired Episodic Memory for Infinite Context LLMs

https://github.com/em-llm/EM-LLM-model
113•jbotz•11mo ago

Comments

MacsHeadroom•11mo 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•11mo 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•11mo 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•11mo ago
do you have references to

> TTT, cannon layers, and titans

najarvg•11mo 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•11mo ago
is titans replicated? I feel like lucidrains couldn't replicate.
logicchains•11mo 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•11mo 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•11mo 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•11mo 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•11mo 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.