frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

List animals until failure

https://rose.systems/animalist/
46•l1n•4h ago•25 comments

Mobile carriers can get your GPS location

https://an.dywa.ng/carrier-gnss.html
526•cbeuw•11h ago•334 comments

Cells use 'bioelectricity' to coordinate and make group decisions

https://www.quantamagazine.org/cells-use-bioelectricity-to-coordinate-and-make-group-decisions-20...
17•marojejian•5h ago•1 comments

pg_tracing: Distributed Tracing for PostgreSQL

https://github.com/DataDog/pg_tracing
14•tanelpoder•3d ago•1 comments

In praise of –dry-run

https://henrikwarne.com/2026/01/31/in-praise-of-dry-run/
96•ingve•8h ago•62 comments

Generative AI and Wikipedia editing: What we learned in 2025

https://wikiedu.org/blog/2026/01/29/generative-ai-and-wikipedia-editing-what-we-learned-in-2025/
108•ColinWright•7h ago•48 comments

Scientist who helped eradicate smallpox dies at age 89

https://www.scientificamerican.com/article/smallpox-eradication-champion-william-foege-dies-at-89/
166•CrossVR•3d ago•34 comments

Opentrees.org (2024)

https://opentrees.org/#pos=1/-37.8/145
33•surprisetalk•4d ago•3 comments

Outsourcing thinking

https://erikjohannes.no/posts/20260130-outsourcing-thinking/index.html
103•todsacerdoti•8h ago•88 comments

Data Processing Benchmark Featuring Rust, Go, Swift, Zig, Julia etc.

https://github.com/zupat/related_post_gen
73•behnamoh•8h ago•32 comments

The Saddest Moment (2013) [pdf]

https://www.usenix.org/system/files/login-logout_1305_mickens.pdf
100•tosh•9h ago•19 comments

Sparse File LRU Cache

http://ternarysearch.blogspot.com/2026/01/sparse-file-lru-cache.html
6•paladin314159•4h ago•0 comments

Demystifying ARM SME to Optimize General Matrix Multiplications

https://arxiv.org/abs/2512.21473
66•matt_d•9h ago•14 comments

Apple-1 Computer Prototype Board #0 sold for $2.75M

https://www.rrauction.com/auctions/lot-detail/350902407346003-apple-1-computer-prototype-board-0-...
38•qingcharles•2h ago•19 comments

Nintendo DS code editor and scriptable game engine

https://crl.io/ds-game-engine/
117•Antibabelic•10h ago•28 comments

Show HN: Minimal – Open-Source Community driven Hardened Container Images

https://github.com/rtvkiz/minimal
78•ritvikarya98•9h ago•24 comments

Finland looks to introduce Australia-style ban on social media

https://yle.fi/a/74-20207494
544•Teever•12h ago•397 comments

Wikipedia: Sandbox

https://en.wikipedia.org/wiki/Wikipedia:Sandbox
65•zaptrem•1d ago•16 comments

Browser Agent Benchmark: Comparing LLM models for web automation

https://browser-use.com/posts/ai-browser-agent-benchmark
3•MagMueller•13h ago•0 comments

Ferrari vs. Markets

https://ferrari-imports.enigmatechnologies.dev/
49•merinid•2d ago•26 comments

Swift is a more convenient Rust (2023)

https://nmn.sh/blog/2023-10-02-swift-is-the-more-convenient-rust
252•behnamoh•7h ago•233 comments

CollectWise (YC F24) Is Hiring

https://www.ycombinator.com/companies/collectwise/jobs/ZunnO6k-ai-agent-engineer
1•OBrien_1107•8h ago

Nvidia's 10-year effort to make the Shield TV the most updated Android device

https://arstechnica.com/gadgets/2026/01/inside-nvidias-10-year-effort-to-make-the-shield-tv-the-m...
117•qmr•13h ago•99 comments

Best of Moltbook

https://www.astralcodexten.com/p/best-of-moltbook
28•feross•7h ago•8 comments

Apple Platform Security (Jan 2026) [pdf]

https://help.apple.com/pdf/security/en_US/apple-platform-security-guide.pdf
147•pieterr•13h ago•109 comments

CPython Internals Explained

https://github.com/zpoint/CPython-Internals
182•yufiz•4d ago•43 comments

Writing a .NET Garbage Collector in C# – Part 6: Mark and Sweep

https://minidump.net/writing-a-net-gc-in-c-part-6/
53•pjmlp•4d ago•1 comments

EV-1 for Lease (1996)

https://www.loe.org/shows/shows.html?programID=96-P13-00047#feature4
6•1970-01-01•2d ago•1 comments

Show HN: Moltbook – A social network for moltbots (clawdbots) to hang out

https://www.moltbook.com/
163•schlichtm•3d ago•815 comments

Noctia: A sleek and minimal desktop shell thoughtfully crafted for Wayland

https://github.com/noctalia-dev/noctalia-shell
49•doener•9h ago•19 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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