frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Netflix to Acquire Warner Bros

https://about.netflix.com/en/news/netflix-to-acquire-warner-bros
979•meetpateltech•6h ago•807 comments

Cloudflare outage on December 5, 2025

https://blog.cloudflare.com/5-december-2025-outage/
293•meetpateltech•2h ago•176 comments

I'm Peter Roberts, immigration attorney who does work for YC and startups. AMA

62•proberts•2h ago•44 comments

Shingles vaccination prevented or delayed dementia

https://www.cell.com/cell/fulltext/S0092-8674(25)01256-5
46•Archelaos•37m ago•11 comments

Making RSS More Fun

https://matduggan.com/making-rss-more-fun/
115•salmon•5h ago•62 comments

Framework Laptop 13 gets ARM processor with 12 cores via upgrade kit

https://www.notebookcheck.net/Framework-Laptop-13-gets-ARM-processor-with-12-cores-via-upgrade-ki...
140•woodrowbarlow•2h ago•72 comments

Patterns for Defensive Programming in Rust

https://corrode.dev/blog/defensive-programming/
23•PaulHoule•1h ago•2 comments

UniFi 5G

https://blog.ui.com/article/introducing-unifi-5g
288•janandonly•11h ago•227 comments

Onlook (YC W25) the Cursor for Designers Is Hiring a Founding Fullstack Engineer

1•D_R_Farrell•1h ago

The AI Backlash Is Here: Why Public Patience with Tech Giants Is Running Out

https://www.newsweek.com/ai-backlash-openai-meta-friend-10807425
45•zerosizedweasle•54m ago•16 comments

Synadia and TigerBeetle Pledge $512,000 to the Zig Software Foundation

https://tigerbeetle.com/blog/2025-10-25-synadia-and-tigerbeetle-pledge-512k-to-the-zig-software-f...
13•cratermoon•1h ago•0 comments

Most technical problems are people problems

https://blog.joeschrag.com/2023/11/most-technical-problems-are-really.html
205•mooreds•5h ago•185 comments

Show HN: Kraa – Writing App for Everything

https://kraa.io/about
78•levmiseri•1d ago•44 comments

Netflix’s AV1 Journey: From Android to TVs and Beyond

https://netflixtechblog.com/av1-now-powering-30-of-netflix-streaming-02f592242d80
466•CharlesW•18h ago•241 comments

BMW PHEV: Safety fuse replacement is extremely expensive

https://evclinic.eu/2025/12/04/2021-phev-bmw-ibmucp-21f37e-post-crash-recovery-when-eu-engineerin...
380•mikelabatt•17h ago•411 comments

I have been writing a niche history blog for 15 years

https://resobscura.substack.com/p/why-i-have-been-writing-a-niche-history
219•benbreen•23h ago•40 comments

Jony Ive's OpenAI Device Barred from Using 'Io' Name

https://www.macrumors.com/2025/12/05/openai-device-barred-from-io-name/
32•thm•1h ago•6 comments

Nimony (Nim 3.0) Design Principles

https://nim-lang.org/araq/nimony.html
97•andsoitis•3d ago•58 comments

Show HN: Pbnj – A minimal, self-hosted pastebin you can deploy in 60 seconds

https://pbnj.sh/
29•bhavnicksm•5h ago•8 comments

New 3D scan reveals a hidden network of moai carvers on Easter Island

https://www.sciencedaily.com/releases/2025/11/251130050717.htm
24•saikatsg•4d ago•4 comments

After 40 years of adventure games, Ron Gilbert pivots to outrunning Death

https://arstechnica.com/gaming/2025/12/after-40-years-of-adventure-games-ron-gilbert-pivots-to-ou...
168•mikhael•4d ago•66 comments

Trick users and bypass warnings – Modern SVG Clickjacking attacks

https://lyra.horse/blog/2025/12/svg-clickjacking/
297•spartanatreyu•18h ago•41 comments

The Forgotten Roman Ruins of the ‘Pompeii of the Middle East’

https://news.artnet.com/art-world/huge-jerash-jordan-pompeii-middle-easy-2708480
6•pseudolus•6d ago•0 comments

Kenyan court declares law banning seed sharing unconstitutional

https://apnews.com/article/kenya-seed-sharing-law-ruling-ad4df5a364299b3a9f8515c0f52d5f80
244•thunderbong•9h ago•71 comments

Show HN: Tacopy – Tail Call Optimization for Python

https://github.com/raaidrt/tacopy
81•raaid-rt•5d ago•38 comments

Influential study on glyphosate safety retracted 25 years after publication

https://www.lemonde.fr/en/environment/article/2025/12/03/influential-study-on-glyphosate-safety-r...
178•isolli•4h ago•145 comments

CSS now has an if() conditional function

https://caniuse.com/?search=if
244•aanthonymax•5d ago•200 comments

WikiFlix: Full Movies Hosted on Wikimedia Commons

https://commons.wikimedia.org/wiki/User:Spinster/WikiFlix
5•netule•16m ago•1 comments

How elites could shape mass preferences as AI reduces persuasion costs

https://arxiv.org/abs/2512.04047
661•50kIters•1d ago•618 comments

Covid-19 mRNA Vaccination and 4-Year All-Cause Mortality

https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2842305
215•bpierre•3h ago•201 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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