frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Public Sans – A strong, neutral typeface

https://public-sans.digital.gov/
160•mhb•2h ago•53 comments

Netflix: Open Content

https://opencontent.netflix.com/
402•tosh•6h ago•72 comments

Non-Zero-Sum Games

https://nonzerosum.games/
204•8organicbits•5h ago•71 comments

The British Empire's Resilient Subsea Telegraph Network

https://subseacables.blogspot.com/2025/12/the-british-empires-resilient-subsea.html
75•giuliomagnifico•3h ago•9 comments

The Legacy of Undersea Cables

https://blog.sciencemuseumgroup.org.uk/the-legacy-of-undersea-cables/
24•teleforce•2h ago•3 comments

Postgres extension complements pgvector for performance and scale

https://github.com/timescale/pgvectorscale
55•flyaway123•5d ago•4 comments

Approachable Swift Concurrency

https://fuckingapproachableswiftconcurrency.com/en/
71•wrxd•3h ago•31 comments

Go away Python

https://lorentz.app/blog-item.html?id=go-shebang
198•baalimago•8h ago•149 comments

GOG is getting acquired by its original co-founder

https://www.gog.com/blog/gog-is-getting-acquired-by-its-original-co-founder-what-it-means-for-you/
798•haunter•1d ago•474 comments

No strcpy either

https://daniel.haxx.se/blog/2025/12/29/no-strcpy-either/
124•firesteelrain•3h ago•58 comments

Hive (YC S14) Is Hiring a Staff Software Engineer (Data Systems)

https://jobs.ashbyhq.com/hive.co/cb0dc490-0e32-4734-8d91-8b56a31ed497
1•patman_h•2h ago

Stranger Things creator says turn off "garbage" settings

https://screenrant.com/stranger-things-creator-turn-off-settings-premiere/
309•1970-01-01•17h ago•553 comments

Times New American: A Tale of Two Fonts

https://hsu.cy/2025/12/times-new-american/
108•firexcy•4h ago•64 comments

Show HN: One clean, developer-focused page for every Unicode symbol

https://fontgenerator.design/symbols
108•yarlinghe•5d ago•45 comments

Tesla's 4680 battery supply chain collapses as partner writes down deal by 99%

https://electrek.co/2025/12/29/tesla-4680-battery-supply-chain-collapses-partner-writes-down-dea/
578•coloneltcb•23h ago•634 comments

Hacking Washing Machines [video]

https://media.ccc.de/v/39c3-hacking-washing-machines
172•clausecker•15h ago•36 comments

Nicolas Guillou, French ICC judge sanctioned by the US and “debanked”

https://www.lemonde.fr/en/international/article/2025/11/19/nicolas-guillou-french-icc-judge-sanct...
239•lifeisstillgood•5h ago•171 comments

ManusAI Joins Meta

https://manus.im/blog/manus-joins-meta-for-next-era-of-innovation
284•gniting•18h ago•175 comments

The future of software development is software developers

https://codemanship.wordpress.com/2025/11/25/the-future-of-software-development-is-software-devel...
326•cdrnsf•21h ago•360 comments

Charm Ruby – Glamorous Terminal Libraries for Ruby

https://charm-ruby.dev/
79•todsacerdoti•9h ago•11 comments

Reverse Engineering a Mysterious UDP Stream in My Hotel (2016)

https://www.gkbrk.com/hotel-music
5•bayesnet•1w ago•0 comments

Concurrent Hash Table Designs

https://bluuewhale.github.io/posts/concurrent-hashmap-designs/
23•signa11•3d ago•1 comments

UNIX Fourth Edition

http://squoze.net/UNIX/v4/README
88•dcminter•1w ago•8 comments

What Happened to Abit Motherboards

https://dfarq.homeip.net/what-happened-to-abit-motherboards/
3•zdw•2h ago•0 comments

AI is forcing us to write good code

https://bits.logic.inc/p/ai-is-forcing-us-to-write-good-code
261•sgk284•21h ago•193 comments

Turning an old Amazon Kindle into a eInk development platform (2021)

https://blog.lidskialf.net/2021/02/08/turning-an-old-kindle-into-a-eink-development-platform/
55•fanf2•4d ago•8 comments

Singapore Study Links Heavy Infant Screen Time to Teen Anxiety

https://www.bloomberg.com/news/articles/2025-12-30/singapore-study-links-heavy-infant-screen-time...
58•1vuio0pswjnm7•4h ago•30 comments

Google is dead. Where do we go now?

https://www.circusscientist.com/2025/12/29/google-is-dead-where-do-we-go-now/
978•tomjuggler•20h ago•777 comments

Graph Algorithms in Rayon

https://davidlattimore.github.io/posts/2025/11/27/graph-algorithms-in-rayon.html
37•PaulHoule•4d ago•0 comments

MongoDB Server Security Update, December 2025

https://www.mongodb.com/company/blog/news/mongodb-server-security-update-december-2025
100•plorkyeran•16h ago•41 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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