frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

GitHub: Git Operation Failures

https://www.githubstatus.com/incidents/5q7nmlxz30sk
175•wilhelmklopp•41m ago•79 comments

Gemini 3

https://blog.google/products/gemini/gemini-3/
816•preek•6h ago•583 comments

Google Antigravity

https://antigravity.google/
472•Fysi•5h ago•568 comments

Pebble, Rebble, and a path forward

https://ericmigi.com/blog/pebble-rebble-and-a-path-forward/
218•phoronixrly•3h ago•87 comments

I am stepping down as the CEO of Mastodon

https://blog.joinmastodon.org/2025/11/my-next-chapter-with-mastodon/
116•Tomte•3h ago•36 comments

The Final Straw: Why Companies Replace Once-Beloved Technology Brands

https://www.functionize.com/blog/the-final-straw-why-companies-replace-once-beloved-technology-br...
19•ohjeez•1h ago•4 comments

GitHub Down

88•mikeocool•39m ago•29 comments

OrthoRoute – GPU-accelerated autorouting for KiCad

https://bbenchoff.github.io/pages/OrthoRoute.html
34•wanderingjew•2h ago•6 comments

Cloudflare Global Network experiencing issues

https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
2223•imdsm•9h ago•1416 comments

The code and open-source tools I used to produce a science fiction anthology

https://compellingsciencefiction.com/posts/the-code-and-open-source-tools-i-used-to-produce-a-sci...
7•mojoe•5h ago•0 comments

Show HN: Guts – convert Golang types to TypeScript

https://github.com/coder/guts
57•emyrk•3h ago•14 comments

Solving a million-step LLM task with zero errors

https://arxiv.org/abs/2511.09030
85•Anon84•4h ago•35 comments

How Quake.exe got its TCP/IP stack

https://fabiensanglard.net/quake_chunnel/index.html
424•billiob•13h ago•101 comments

Show HN: RowboatX – open-source Claude Code for everyday automations

https://github.com/rowboatlabs/rowboat
24•segmenta•2h ago•4 comments

Chuck Moore: Colorforth has stopped working [video]

https://www.youtube.com/watch?v=MvkGBWXb2oQ#t=22
20•netten•1d ago•2 comments

Trying out Gemini 3 Pro with audio transcription and a new pelican benchmark

https://simonwillison.net/2025/Nov/18/gemini-3/
57•nabla9•2h ago•25 comments

Oracle is underwater on its 'astonishing' $300B OpenAI deal

https://www.ft.com/content/064bbca0-1cb2-45ab-85f4-25fdfc318d89
59•busymom0•52m ago•10 comments

Strix Halo's Memory Subsystem: Tackling iGPU Challenges

https://chipsandcheese.com/p/strix-halos-memory-subsystem-tackling
49•PaulHoule•4h ago•22 comments

Short Little Difficult Books

https://countercraft.substack.com/p/short-little-difficult-books
121•crescit_eundo•6h ago•75 comments

When 1+1+1 Equals 1

https://mathenchant.wordpress.com/2024/12/19/when-111-equals-1/
22•surprisetalk•5d ago•7 comments

Mysterious holes in the Andes may have been an ancient marketplace

https://www.sydney.edu.au/news-opinion/news/2025/11/10/mysterious-holes-in-the-andes-may-have-bee...
4•gmays•6d ago•0 comments

A 'small' vanilla Kubernetes install on NixOS

https://stephank.nl/p/2025-11-17-a-small-vanilla-kubernetes-install-on-nixos.html
9•todsacerdoti•10h ago•2 comments

Nearly all UK drivers say headlights are too bright

https://www.bbc.com/news/articles/c1j8ewy1p86o
574•YeGoblynQueenne•7h ago•588 comments

Show HN: Tokenflood – simulate arbitrary loads on instruction-tuned LLMs

https://github.com/twerkmeister/tokenflood
9•twerkmeister•6d ago•0 comments

Google boss says AI investment boom has 'elements of irrationality'

https://www.bbc.com/news/articles/cwy7vrd8k4eo
79•jillesvangurp•15h ago•163 comments

Experiment: Making TypeScript immutable-by-default

https://evanhahn.com/typescript-immutability-experiment/
78•ingve•7h ago•65 comments

The Miracle of Wörgl

https://scf.green/story-of-worgl-and-others/
119•simonebrunozzi•10h ago•63 comments

Mathematics and Computation (2019) [pdf]

https://www.math.ias.edu/files/Book-online-Aug0619.pdf
59•nill0•8h ago•13 comments

A day at Hetzner Online in the Falkenstein data center

https://www.igorslab.de/en/a-day-at-hetzner-online-in-the-falkenstein-data-center-insights-into-s...
149•speckx•5h ago•59 comments

Do not put your site behind Cloudflare if you don't need to

https://huijzer.xyz/posts/123/do-not-put-your-site-behind-cloudflare-if-you-dont
417•huijzer•8h ago•298 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.