frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Compression is prediction

https://ngrok.com/blog/compression-is-prediction
379•nikolay•9h ago•147 comments

The hardest working font in Manhattan (2025)

https://aresluna.org/the-hardest-working-font-in-manhattan/
71•dcminter•5d ago•7 comments

The lifesaving secret hidden inside a horseshoe crab's blue blood

https://whdh.com/news/the-lifesaving-secret-hidden-inside-a-horseshoe-crabs-blue-blood-and-the-ra...
36•andsoitis•3h ago•7 comments

WorldClaw Agentic 3D open-world generation at scale

https://tencent-hunyuan.github.io/Hunyuan3D-WorldClaw/
168•EwanG•7h ago•53 comments

Nvidia Nemotron 3.5 Lightning and NeMo Switchyard

https://blogs.nvidia.com/blog/nemotron-lightning-switchyard-rtx-dgx/
199•droidjj•9h ago•107 comments

Mojo 1.0

https://www.modular.com/blog/modular-26-5-mojo-1-0-is-here
336•dayanruben•12h ago•155 comments

Stealing Reasoning Traces from Proprietary LLM APIs

https://stolen-thoughts.com/
557•quantumgarbage•15h ago•238 comments

The Human Is the Loop

https://brentfitzgerald.com/posts/the-human-is-the-loop/
27•burnto•2h ago•4 comments

OpenAI’s head of ethics leaves less than a year after joining

https://www.ft.com/content/e49dfb75-f841-4466-a577-f7aaff8779a0
346•ilamont•16h ago•364 comments

Company Offering '100% Human-Written, Never AI' Medical Research Is 100% AI

https://www.404media.co/company-offering-100-human-written-never-ai-peer-review-is-entirely-ai/
84•Anon84•2h ago•18 comments

New Bedford police officer accused of using Flock cameras to track ex-partner

https://newbedfordlight.org/new-bedford-police-officer-accused-of-using-flock-cameras-to-track-an...
108•newsomix9xl•3h ago•56 comments

Grok Bot

https://x.ai/bot
208•rvz•11h ago•175 comments

Making holograms with a pen plotter

https://blog.jordan.matelsky.com/Penplotter-holography/
135•DemiGuru•10h ago•14 comments

Neutrinos from Deep Inside Earth Provide a New Picture of the Mantle

https://www.quantamagazine.org/neutrinos-from-deep-inside-earth-provide-a-new-picture-of-the-mant...
21•rbanffy•15h ago•1 comments

Show HN: iPhone app takes simultaneous images from 2 lenses, fuses into 1 photo

https://photosynthesis.camera
238•sajomes•3d ago•237 comments

Show HN: Tamron Lens Utility Alternative on Linux

https://github.com/yikerman/tamron-lens-control
44•xiaoyu2006•4d ago•0 comments

Show HN: Line9 – A Mermaid rendering engine with its own layout

https://line9.ai/diagram
45•jumpalongjim•5d ago•11 comments

Go is an ideal language for AI-assisted software engineering

https://developers.googleblog.com/why-go-is-an-ideal-language-for-ai-assisted-software-engineering/
309•0xedb•12h ago•367 comments

Jolt: Clojure compiler implemented with Chez Scheme

https://jolt-lang.github.io
170•mark_l_watson•3d ago•60 comments

England set to be one of the first countries to eliminate hepatitis C

https://www.bbc.com/news/articles/c75gk620r22o
503•stevekemp•16h ago•364 comments

London Underground begins scanning passengers' faces

https://www.btp.police.uk/news/btp/news/england/btp-expands-live-facial-recognition-lfr-trial-int...
265•BlueBerry2001•19h ago•271 comments

Show HN: Find stale, orphaned, deleted-but-retrievable RAG vectors

https://github.com/rimironenko/rag-staleness-check
3•rimironenko•5d ago•0 comments

How we used to get jobs: A newspaper classifieds story

https://ironicsans.ghost.io/how-we-used-to-get-jobs/
123•speckx•10h ago•98 comments

Nvidia's Risky Business

https://stratechery.com/2026/nvidias-risky-business/
316•jonbaer•18h ago•151 comments

pg_clickhouse v0.10: Subquery pushdown and 1000x faster TPC-H queries

https://clickhouse.com/blog/pg_clickhouse-whats-new-july-2026
45•saisrirampur•7h ago•3 comments

CSS properties you should know for better text designs

https://master.dev/blog/typographic-css-tricks/
95•ibobev•11h ago•10 comments

Manus will return to operating as an independent company

https://manus.im/blog/a-note-to-our-users
145•thm•14h ago•70 comments

Emergent Introspective Awareness in Large Language Models

https://arxiv.org/abs/2601.01828
43•doener•7h ago•20 comments

Show HN: Git-knife – Edit commit messages, authors, and dates like a spreadsheet

https://github.com/TheRealYT/git-knife
144•YonathanTesfaye•13h ago•93 comments

RSI Simulator

https://www.paradigm.xyz/writing/rsi-simulator
37•ckraeuter•11h ago•14 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.