frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

DSpark: Speculative decoding accelerates LLM inference [pdf]

https://github.com/deepseek-ai/DeepSpec/blob/main/DSpark_paper.pdf
548•aurenvale•5h ago•212 comments

OpenRA

https://www.openra.net/
141•tosh•2h ago•37 comments

Fintech Engineering Handbook

https://w.pitula.me/fintech-engineering-handbook/
210•signa11•4h ago•65 comments

Post-Mythos Cybersecurity: Keep calm and carry on

https://cephalosec.com/blog/cybersecurity-in-the-post-mythos-era-keep-calm-and-carry-on/
6•Versipelle•18m ago•1 comments

Long Wave radio era set to end with switch-off

https://www.economist.com/britain/2026/06/25/the-bbc-switches-off-its-oldest-service
98•edward•1d ago•100 comments

Previewing GPT‑5.6 Sol: a next-generation model

https://openai.com/index/previewing-gpt-5-6-sol/
1051•minimaxir•21h ago•670 comments

How H-E-B Became Texas' Most Beloved Brand (2024)

https://texashighways.com/culture/how-heb-became-texas-most-beloved-brand/
18•NaOH•2d ago•7 comments

Beer CSS – Build material design in record time

https://www.beercss.com
77•Seb-C•5h ago•31 comments

The US Army Issued Ocarinas to Soldiers in World War II

https://www.flutetunes.com/articles/my-flute-goes-to-war/
63•tomcam•2d ago•30 comments

How Many Elementary Particles Are There, Really?

https://www.quantamagazine.org/how-many-elementary-particles-are-there-really-20260615/
19•rwmj•2h ago•4 comments

Nox Metals (YC S25) Is Hiring SWE

https://www.ycombinator.com/companies/nox-metals/jobs/M1f1enD-software-engineer
1•zane_heng•2h ago

Streaming services' obnoxiously loud ads become illegal on July 1 in California

https://arstechnica.com/gadgets/2026/06/streaming-services-obnoxiously-loud-ads-become-illegal-on...
48•speckx•1h ago•7 comments

Linux on Older Hardware: The Complete Revival Guide

https://www.fosslinux.com/158206/linux-on-older-hardware-revival-guide.htm
119•tapanjk•2d ago•66 comments

Asian AI startups launch Mythos-like models

https://techcrunch.com/2026/06/27/asian-ai-startups-launch-mythos-like-models-as-anthropics-expor...
42•bogdiyan•1h ago•35 comments

Task Failed Successfully: Saturating NIC and Disk Bandwidth

https://blog.mrcroxx.com/posts/task-failed-successfully-saturating-nic-and-disk-bandwidth/
8•MrCroxx•4d ago•3 comments

Why does kinetic energy increase quadratically, not linearly, with speed? (2011)

https://physics.stackexchange.com/questions/535/why-does-kinetic-energy-increase-quadratically-no...
295•ProxyTracer•15h ago•147 comments

WordStar: A Writer's Word Processor (1996)

https://www.sfwriter.com/wordstar.htm
129•droidjj•11h ago•63 comments

Cultures of Making and Relating

https://blog.khinsen.net/posts/2026/06/25/cultures.html
21•akkartik•1d ago•1 comments

Faster KNN search in Manticore: 2-pass HNSW, batched distances, and AVX-512

https://medium.com/@s_nikolaev/faster-knn-search-in-manticore-2-pass-hnsw-batched-distances-and-a...
35•snikolaev•1d ago•2 comments

If you can't hold it, you don't own it

https://dervis.de/physical/
110•cemdervis•3h ago•73 comments

MicroVMs: Run isolated sandboxes with full lifecycle control

https://aws.amazon.com/blogs/aws/run-isolated-sandboxes-with-full-lifecycle-control-aws-lambda-in...
350•justincormack•4d ago•192 comments

U.S. allows Anthropic to release Mythos AI to ‘trusted’ US organizations

https://www.semafor.com/article/06/27/2026/us-releases-powerful-anthropic-model-mythos-to-some-us...
502•bobrenjc93•15h ago•661 comments

Jest/Vitest interactive course (runs in the browser)

https://howtotestfrontend.com/courses/jest-vitest-fundamentals
26•howToTestFE•2d ago•10 comments

AI in mathematics is forcing big questions

https://spectrum.ieee.org/ai-in-mathematics
162•rbanffy•16h ago•140 comments

Anatomy of a Failed (Nation-State?) Attack

https://grack.com/blog/2026/06/25/dissecting-a-failed-nation-state-attack/
95•signa11•12h ago•20 comments

International investment and local rules push prices up faster than supply

https://news.mccombs.utexas.edu/research/foreign-funds-help-make-housing-unaffordable/
112•hhs•15h ago•44 comments

The gap between open weights LLMs and closed source LLMs

https://blog.doubleword.ai/frontier-os-llm
257•kkm•17h ago•199 comments

OpenTTD 16.0-Beta1

https://www.openttd.org/news/2026/06/25/openttd-16-0-beta1
201•untilted•10h ago•36 comments

Hellishly Slow Level 13 Deflate Compression

https://kirill.korins.ky/articles/hellishly-slow-level-13-deflate-compression/
81•zX41ZdbW•4d ago•22 comments

U.S. government will decide who gets to use GPT-5.6

https://www.washingtonpost.com/technology/2026/06/26/openai-says-us-government-will-vet-users-its...
1101•alain94040•20h ago•1163 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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