frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

ASCII characters are not pixels: a deep dive into ASCII rendering

https://alexharri.com/blog/ascii-rendering
580•alexharri•8h ago•69 comments

We put Claude Code in Rollercoaster Tycoon

https://labs.ramp.com/rct
222•iamwil•5d ago•122 comments

Show HN: Minikv – Distributed key-value and object store in Rust (Raft, S3 API)

https://github.com/whispem/minikv
13•whispem•28m ago•7 comments

An Elizabethan mansion's secrets for staying warm

https://www.bbc.com/future/article/20260116-an-elizabethan-mansions-secrets-for-staying-warm
47•Tachyooon•3h ago•51 comments

There's no single best way to store information

https://www.quantamagazine.org/why-theres-no-single-best-way-to-store-information-20260116/
47•7777777phil•3h ago•18 comments

The recurring dream of replacing developers

https://www.caimito.net/en/blog/2025/12/07/the-recurring-dream-of-replacing-developers.html
122•glimshe•5h ago•123 comments

The Olivetti Company – By Bradford Morgan White

https://www.abortretry.fail/p/the-olivetti-company
25•rbanffy•6d ago•7 comments

Canada's deal with China signals it is serious about shift from US

https://www.bbc.com/news/articles/cm24k6kk1rko
34•breve•39m ago•6 comments

Common misunderstandings about large software companies

https://philipotoole.com/common-misunderstandings-about-large-software-companies/
11•otoolep•5d ago•1 comments

Counterfactual evaluation for recommendation systems

https://eugeneyan.com/writing/counterfactual-evaluation/
36•kurinikku•14h ago•2 comments

M8SBC-486 (Homebrew 486 computer)

https://maniek86.xyz/projects/m8sbc_486.php
30•rasz•6d ago•5 comments

East Germany balloon escape

https://en.wikipedia.org/wiki/East_Germany_balloon_escape
640•robertvc•1d ago•274 comments

The Dilbert Afterlife

https://www.astralcodexten.com/p/the-dilbert-afterlife
353•rendall•1d ago•216 comments

The 600-year-old origins of the word 'hello'

https://www.bbc.com/culture/article/20260113-hello-hiya-aloha-what-our-greetings-reveal
79•1659447091•8h ago•46 comments

ClickHouse acquires Langfuse

https://langfuse.com/blog/joining-clickhouse
171•tin7in•10h ago•77 comments

Apples, Trees, and Quasimodes

https://systemstack.dev/2025/09/humane-computing/
12•entaloneralie•3h ago•1 comments

16 Best Practices for Reducing Dependabot Noise

https://nesbitt.io/2026/01/10/16-best-practices-for-reducing-dependabot-noise.html
27•zdw•5d ago•18 comments

Show HN: What if your menu bar was a keyboard-controlled command center?

https://extrabar.app/
37•pugdogdev•2h ago•22 comments

The Resonant Computing Manifesto

https://resonantcomputing.org/
31•sinak•3h ago•8 comments

Show HN: Streaming gigabyte medical images from S3 without downloading them

https://github.com/PABannier/WSIStreamer
118•el_pa_b•11h ago•41 comments

Map To Poster – Create Art of your favourite city

https://github.com/originalankur/maptoposter
173•originalankur•9h ago•50 comments

The 'untouchable hacker god' behind Finland's biggest crime

https://www.theguardian.com/technology/2026/jan/17/vastaamo-hack-finland-therapy-notes
123•c420•12h ago•122 comments

Cursor's latest “browser experiment” implied success without evidence

https://embedding-shapes.github.io/cursor-implied-success-without-evidence/
669•embedding-shape•1d ago•294 comments

2025 was the third hottest year on record

https://www.economist.com/science-and-technology/2026/01/14/2025-was-the-third-hottest-year-on-re...
135•andsoitis•2h ago•114 comments

OpenAI to test ads in ChatGPT as it burns through billions

https://arstechnica.com/information-technology/2026/01/openai-to-test-ads-in-chatgpt-as-it-burns-...
6•Terretta•36m ago•0 comments

High-Level Is the Goal

https://bvisness.me/high-level/
218•tobr•2d ago•105 comments

6-Day and IP Address Certificates Are Generally Available

https://letsencrypt.org/2026/01/15/6day-and-ip-general-availability
468•jaas•1d ago•258 comments

US electricity demand surged in 2025 – solar handled 61% of it

https://electrek.co/2026/01/16/us-electricity-demand-surged-in-2025-solar-handled-61-percent/
291•doener•9h ago•269 comments

Show HN: I built a tool to assist AI agents to know when a PR is good to go

https://dsifry.github.io/goodtogo/
17•dsifry•10h ago•9 comments

PCs refuse to shut down after Microsoft patch

https://www.theregister.com/2026/01/16/patch_tuesday_secure_launch_bug_no_shutdown/
199•smurda•9h ago•211 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.