frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

How Bluesky draws its logo on screenshots

https://timmarinin.net/2026/bluesky-screenshots/
414•gavide•8h ago•277 comments

GPT-5.6 Sol Pricing Cut by 50%

https://openrouter.ai/openai/gpt-5.6-sol
356•Topfi•9h ago•192 comments

Quake Shareware, a CD-ROM just a little too full

https://fabiensanglard.net/quake_shareware_cd/index.html
285•shdon•8h ago•119 comments

Fairphone 6 and PostmarketOS working main camera

https://catcrafts.net/posts/fairphone-6-postmarketos-working-main-camera
144•pizzaiolo•9h ago•32 comments

Shattered skeleton is first confirmed death from trebuchet

https://www.science.org/content/article/shattered-skeleton-scottish-castle-first-confirmed-death-...
54•hermitcrab•4d ago•34 comments

The Benchmarkpocalypse

https://danluu.com/benchpocalypse/
64•cyndunlop•4h ago•8 comments

A Preview of DuckDB v2.0

https://duckdb.org/2026/08/17/duckdb-20-highlights
605•ibotty•17h ago•110 comments

The 37signals Manager Playbook

https://basecamp.com/managers
41•tosh•4d ago•3 comments

AI-Generated GitHub Copilot “Autofix” Allowed Compromise of Snowflake's Jira

https://www.wiz.io/blog/red-agent-snowflake-copilot-cicd-bug
354•galnagli•16h ago•138 comments

Olo (Color)

https://en.wikipedia.org/wiki/Olo_(color)
399•inigyou•5d ago•74 comments

GPU Offload in Rust: Portable, Safe, and Fast

https://arxiv.org/abs/2608.13759
195•linggen•13h ago•37 comments

The Road to MS-DOS 2.0

https://nemanjatrifunovic.substack.com/p/the-road-to-ms-dos-2
56•whobre•5d ago•19 comments

An update on leaving Gmail for Fastmail

https://moddedbear.com/an-update-on-leaving-gmail-for-fastmail/
187•neogodless•13h ago•124 comments

Israel creates fake think tank in likely attempt to dupe AI chatbots

https://responsiblestatecraft.org/israel-influence-chatgpt/
360•DeepLogin•10h ago•225 comments

GPT 5.6 Sol is the best "vision" model OpenAI ever released

https://blog.roboflow.com/openai-gpt-5-6/
329•plurby•18h ago•159 comments

AI;DR (AI; Didn't Read)

https://www.rickmanelius.com/p/aidr-ai-didnt-read
789•mooreds•11h ago•497 comments

Judge sets framework for Nine PBS to retrieve archival data

https://current.org/2026/08/judge-sets-framework-for-nine-pbs-to-retrieve-archival-data/
155•qingcharles•14h ago•61 comments

India has paved the way for charging merchants a fee on UPI transactions

https://www.bbc.com/news/articles/c8xnwqe00v1o
136•monkey_monkey•11h ago•157 comments

Los Puesteros, solitary men who look after ranches and livestock in Patagonia

https://www.newyorker.com/culture/photo-booth/the-lonely-men-at-the-end-of-the-world
136•bookofjoe•12h ago•46 comments

How to disable or avoid intrusive AI

https://www.librarian.net/notoai/
282•ColinWright•16h ago•165 comments

Sun Clock

https://sunclock.net/
212•Gecko4072•14h ago•69 comments

Repair Cafe – Fix Your Broken Items

https://www.repaircafe.org/
83•rglover•7h ago•11 comments

How do functions like alloca allocate memory from the stack?

https://devblogs.microsoft.com/oldnewthing/20260817-40/?p=112617
49•ingve•9h ago•24 comments

Launch HN: Speko (YC S26) – OpenRouter for Voice AI

https://speko.ai/
100•abdik•15h ago•58 comments

A particle made of force: physicists say they've found mysterious 'glueball'

https://www.nature.com/articles/d41586-026-02498-1
125•Brajeshwar•5d ago•30 comments

A digestion of the proof of Sendov's conjecture

https://terrytao.wordpress.com/2026/08/12/a-digestion-of-the-proof-of-sendovs-conjecture/
24•surprisetalk•4d ago•9 comments

Ghosts of the Past and Devils of the Present

https://thenewcuriosityshop.substack.com/p/ghosts-of-the-past-and-devils-of
5•benbreen•1d ago•0 comments

Ask HN: Alternatives to GitHub

570•dhruv3006•17h ago•360 comments

scScript for Linux

https://scapplications.com/
31•OptionOfT•8h ago•11 comments

Expert Witness to ChatGPT: "Show how 3M is 0 percent at fault"

https://www.404media.co/show-how-3m-is-0-at-fault-expert-witness-used-chatgpt-to-write-report-def...
31•kristjansson•3h ago•11 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.