frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Gaussian Splatting – A$AP Rocky "Helicopter" music video

https://radiancefields.com/a-ap-rocky-releases-helicopter-music-video-featuring-gaussian-splatting
250•ChrisArchitect•3h ago•92 comments

Flux 2 Klein pure C inference

https://github.com/antirez/flux2.c
123•antirez•3h ago•43 comments

Breaking the Zimmermann Telegram (2018)

https://medium.com/lapsed-historian/breaking-the-zimmermann-telegram-b34ed1d73614
31•tony-allan•1h ago•2 comments

A Social Filesystem

https://overreacted.io/a-social-filesystem/
140•icy•12h ago•79 comments

Stirling Cycle Machine Analysis

https://ohioopen.library.ohio.edu/opentextbooks/9/
4•akshatjiwan•27m ago•0 comments

Show HN: Lume 0.2 – Build and Run macOS VMs with unattended setup

https://cua.ai/docs/lume/guide/getting-started/introduction
50•frabonacci•3h ago•5 comments

Sins of the Children (Adrian Tchaikovsky)

https://asteriskmag.com/issues/07/sins-of-the-children
51•maxall4•4h ago•24 comments

jQuery 4

https://blog.jquery.com/2026/01/17/jquery-4-0-0/
615•OuterVale•16h ago•201 comments

Command-line Tools can be 235x Faster than your Hadoop Cluster (2014)

https://adamdrake.com/command-line-tools-can-be-235x-faster-than-your-hadoop-cluster.html
256•tosh•12h ago•174 comments

The Cathedral, the Megachurch, and the Bazaar

https://opensourcesecurity.io/2026/01-cathedral-megachurch-bazaar/
80•todsacerdoti•4d ago•60 comments

Overlapping Markup

https://en.wikipedia.org/wiki/Overlapping_markup
39•ripe•10h ago•7 comments

Show HN: Xenia – A monospaced font built with a custom Python engine

https://github.com/Loretta1982/xenia
29•xeniafont•10h ago•9 comments

A free and open-source rootkit for Linux

https://lwn.net/SubscriberLink/1053099/19c2e8180aeb0438/
131•jwilk•11h ago•30 comments

More sustainable epoxy thanks to phosphorus

https://www.empa.ch/web/s604/flamm-hemmendes-epoxidharz-nachhaltiger-machen
56•JeanKage•4d ago•20 comments

Starting from scratch: Training a 30M Topological Transformer

https://www.tuned.org.uk/posts/013_the_topological_transformer_training_tauformer
111•tuned•9h ago•26 comments

Predicting OpenAI's ad strategy

https://ossa-ma.github.io/blog/openads
417•calcifer•6h ago•330 comments

Show HN: Figma-use – CLI to control Figma for AI agents

https://github.com/dannote/figma-use
79•dannote•15h ago•32 comments

ThinkNext Design

https://thinknextdesign.com/home.html
209•__patchbit__•14h ago•102 comments

Show HN: HTTP:COLON – A quick HTTP header/directive inspector and reference

https://httpcolon.dev/
11•ultimoo•3h ago•3 comments

Police Invested Millions in Shadowy Phone-Tracking Software Won't Say How Used

https://www.texasobserver.org/texas-police-invest-tangles-sheriff-surveillance/
4•nobody9999•7m ago•2 comments

Keystone (YC S25) Is Hiring

1•pablo24602•9h ago

Software engineers can no longer neglect their soft skills

https://www.qu8n.com/posts/most-important-software-engineering-skill-2026
100•quanwinn•7h ago•114 comments

Evolution Unleashed (2018)

https://aeon.co/essays/science-in-flux-is-a-revolution-brewing-in-evolutionary-theory
6•DiabloD3•1h ago•0 comments

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

https://alexharri.com/blog/ascii-rendering
1137•alexharri•1d ago•126 comments

Cardputer uLisp Machine (2024)

http://www.ulisp.com/show?52G4
6•tosh•3d ago•0 comments

Iconify: Library of Open Source Icons

https://icon-sets.iconify.design/
462•sea-gold•14h ago•53 comments

Erdos 281 solved with ChatGPT 5.2 Pro

https://twitter.com/neelsomani/status/2012695714187325745
280•nl•17h ago•262 comments

Echo Chess: The Quest for Solvability (2023)

https://web.archive.org/web/20230920164939/https://samiramly.com/chess
7•kurinikku•10h ago•1 comments

What is Plan 9?

https://fqa.9front.org/fqa0.html#0.1
138•AlexeyBrin•7h ago•56 comments

Profession by Isaac Asimov (1957)

https://www.abelard.org/asimov.php
163•bkudria•18h ago•52 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.