frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Alberta startup sells no-tech tractors for half price

https://wheelfront.com/this-alberta-startup-sells-no-tech-tractors-for-half-price/
849•Kaibeezy•4h ago•308 comments

Over-editing refers to a model modifying code beyond what is necessary

https://nrehiew.github.io/blog/minimal_editing/
192•pella•2h ago•102 comments

We found a stable Firefox identifier linking all your private Tor identities

https://fingerprint.com/blog/firefox-tor-indexeddb-privacy-vulnerability/
148•danpinto•3h ago•48 comments

Qwen3.6-27B: Flagship-Level Coding in a 27B Dense Model

https://qwen.ai/blog?id=qwen3.6-27b
503•mfiguiere•7h ago•245 comments

5x5 Pixel font for tiny screens

https://maurycyz.com/projects/mcufont/
252•zdw•3d ago•62 comments

Scores decline again for 13-year-old students in reading and mathematics

https://www.nationsreportcard.gov/highlights/ltt/2023/
94•u1hcw9nx•1h ago•97 comments

Windows 9x Subsystem for Linux

https://social.hails.org/@hailey/116446826733136456
798•sohkamyung•10h ago•185 comments

You don't need advice from editors on rejected manuscripts

https://twitter.com/orsonscottcard/status/2046702294406680751
52•MrBuddyCasino•12h ago•30 comments

Ping-pong robot beats top-level human players

https://www.reuters.com/sports/ping-pong-robot-ace-makes-history-by-beating-top-level-human-playe...
10•wslh•5h ago•2 comments

Martin Fowler: Technical, Cognitive, and Intent Debt

https://martinfowler.com/fragments/2026-04-14.html
122•theorchid•4h ago•21 comments

Our eighth generation TPUs: two chips for the agentic era

https://blog.google/innovation-and-ai/infrastructure-and-cloud/google-cloud/eighth-generation-tpu...
337•xnx•8h ago•164 comments

Surveillance Pricing: Exploiting Information Asymmetries

https://lpeproject.org/blog/surveillance-pricing-exploiting-information-asymmetries/
56•cainxinth•3h ago•22 comments

The great Scouse pasty war

https://www.livpost.co.uk/the-great-scouse-pasty-war/
11•DamonHD•2d ago•0 comments

Website streamed live directly from a model

https://flipbook.page/
37•sethbannon•2h ago•15 comments

Workspace Agents in ChatGPT

https://openai.com/index/introducing-workspace-agents-in-chatgpt/
52•mfiguiere•2h ago•18 comments

Bodega cats of New York

https://bodegacatsofnewyork.com
114•zdw•4d ago•45 comments

Ultraviolet corona discharges on treetops during storms

https://www.psu.edu/news/earth-and-mineral-sciences/story/treetops-glowing-during-storms-captured...
166•t-3•7h ago•45 comments

3.4M Solar Panels

https://tech.marksblogg.com/american-solar-farms-v2.html
250•marklit•8h ago•182 comments

GitHub CLI now collects pseudoanonymous telemetry

https://cli.github.com/telemetry
353•ingve•8h ago•272 comments

Parallel Agents in Zed

https://zed.dev/blog/parallel-agents
98•ajeetdsouza•3h ago•53 comments

Show HN: Broccoli, one shot coding agent on the cloud

https://github.com/besimple-oss/broccoli
31•yzhong94•4h ago•28 comments

The Illuminated Man: an unconventional portrait of JG Ballard

https://www.theguardian.com/books/2026/apr/20/the-illuminated-man-by-christopher-priest-and-nina-...
5•agronaut•19m ago•0 comments

Columnar Storage Is Normalization

https://buttondown.com/jaffray/archive/columnar-storage-is-normalization/
86•ibobev•8h ago•33 comments

Anonymous credentials: an illustrated primer (Part 2)

https://blog.cryptographyengineering.com/2026/04/17/anonymous-credentials-an-illustrated-primer-p...
10•kkl•2d ago•0 comments

Scoring Show HN submissions for AI design patterns

https://www.adriankrebs.ch/blog/design-slop/
242•hubraumhugo•5h ago•187 comments

New study compares growing corn for energy to solar production. It's no contest

https://www.anthropocenemagazine.org/2025/04/new-study-compares-growing-corn-for-energy-to-solar-...
36•dotcoma•1h ago•41 comments

How does GPS work?

https://perthirtysix.com/how-the-heck-does-gps-work
202•alfanick•11h ago•45 comments

Youth Suicides Declined After Creation of National Hotline

https://www.nytimes.com/2026/04/22/science/988-youth-suicides-decline.html
157•marojejian•4h ago•92 comments

XOR'ing a register with itself is the idiom for zeroing it out. Why not sub?

https://devblogs.microsoft.com/oldnewthing/20260421-00/?p=112247
184•ingve•14h ago•191 comments

Homegrown – An interactive map of every 2025 FBS college football player

https://torch.football/homegrown
13•brockbedard•3h ago•7 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.