frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

.de TLD offline due to DNSSEC?

https://dnssec-analyzer.verisignlabs.com/nic.de
202•warpspin•56m ago•60 comments

Accelerating Gemma 4: faster inference with multi-token prediction drafters

https://blog.google/innovation-and-ai/technology/developers-tools/multi-token-prediction-gemma-4/
337•amrrs•4h ago•148 comments

Computer Use is 45x more expensive than structured APIs

https://reflex.dev/blog/computer-use-is-45x-more-expensive-than-structured-apis/
206•palashawas•4h ago•116 comments

Three Inverse Laws of AI

https://susam.net/inverse-laws-of-robotics.html
289•blenderob•5h ago•194 comments

Google Chrome silently installs a 4 GB AI model on your device without consent

https://www.thatprivacyguy.com/blog/chrome-silent-nano-install/
1055•john-doe•13h ago•718 comments

EEVblog: The 555 Timer is 55 years old [video]

https://www.youtube.com/watch?v=6JhK8iCQuqI
162•brudgers•5h ago•37 comments

Show HN: Explore color palettes inspired by 3000 master painter artworks

https://paletteinspiration.com/
53•ouli•2h ago•19 comments

GLM-5V-Turbo: Toward a Native Foundation Model for Multimodal Agents

https://arxiv.org/abs/2604.26752
80•gmays•3h ago•19 comments

Agents for financial services and insurance

https://www.anthropic.com/news/finance-agents
164•louiereederson•6h ago•117 comments

California farmers to destroy 420k peach trees following Del Monte bankruptcy

https://www.sfgate.com/centralcoast/article/usda-aid-california-farmers-22240694.php
162•littlexsparkee•2h ago•194 comments

The extended predicative Mahlo universe in Martin-Löf type theory

https://academic.oup.com/logcom/article/34/6/1032/7158523
12•danny00•2d ago•0 comments

IBM didn't want Microsoft to use the Tab key to move between dialog fields

https://devblogs.microsoft.com/oldnewthing/20260505-00/?p=112298
227•SeenNotHeard•3h ago•134 comments

When everyone has AI and the company still learns nothing

https://www.robert-glaser.de/when-everyone-has-ai-and-the-company-still-learns-nothing/
268•youngbrioche•11h ago•182 comments

Proliferate (YC S25) Is Hiring- 200k for junior engineers

https://www.ycombinator.com/companies/proliferate/jobs/L3copvK-founding-engineer
1•pablo24602•4h ago

Researchers print structural colour with an inkjet printer

https://physicsworld.com/a/researchers-print-structural-colour-with-an-inkjet-printer/
26•zeristor•2d ago•5 comments

Should I Run Plain Docker Compose in Production in 2026?

https://distr.sh/blog/running-docker-in-production/
311•pmig•5d ago•236 comments

Async Rust never left the MVP state

https://tweedegolf.nl/en/blog/237/async-rust-never-left-the-mvp-state
408•pjmlp•13h ago•219 comments

Show HN: Airbyte Agents – context for agents across multiple data sources

71•mtricot•6h ago•11 comments

iOS 27 is adding a 'Create a Pass' button to Apple Wallet

https://walletwallet.alen.ro/blog/ios-27-wallet-create-pass/
347•alentodorov•8h ago•264 comments

Today I've made the difficult decision to reduce the size of Coinbase by ~14%

https://twitter.com/brian_armstrong/status/2051616759145185723
147•adrianmsmith•9h ago•161 comments

Zuckerberg 'Personally Authorized and Encouraged' Meta's Copyright Infringement

https://variety.com/2026/digital/news/meta-ai-mark-zuckerberg-copyright-infringement-lawsuit-publ...
88•spankibalt•3h ago•47 comments

Collaborative Editing in CodeMirror (2020)

https://marijnhaverbeke.nl/blog/collaborative-editing-cm.html
46•luu•2d ago•6 comments

Quantum Key Distribution (QKD) and Quantum Cryptography (QC)

https://www.nsa.gov/Cybersecurity/Quantum-Key-Distribution-QKD-and-Quantum-Cryptography-QC/
34•mooreds•3h ago•10 comments

Docker 29 has changed its default image store for new installs

https://docs.docker.com/engine/storage/containerd
111•neitsab•3d ago•61 comments

Comparing the Z80 and 6502 to Their Relatives

https://bumbershootsoft.wordpress.com/2026/05/02/comparing-the-z80-and-6502-to-their-relatives/
94•ibobev•2d ago•18 comments

Simple Meta-Harness on Islo.dev

https://zozo123.github.io/meta-harness-on-islo-page/
44•zozo123-IB•7h ago•17 comments

The first photo published in a newspaper, in 1848 (2023)

https://phsne.org/the-first-photograph-published-in-a-newspaper-1848/
50•geuis•2d ago•19 comments

I'm scared about biological computing

https://kuber.studio/blog/Reflections/I%27m-Scared-About-Biological-Computing
107•kuberwastaken•5h ago•90 comments

Lessons for Agentic Coding: What should we do when code is cheap?

https://www.dbreunig.com/2026/05/04/10-lessons-for-agentic-coding.html
215•ingve•14h ago•212 comments

Apple Cuts More Mac Studio and Mac Mini RAM Options as Memory Shortage Worsens

https://www.macrumors.com/2026/05/05/apple-mac-studio-mac-mini-ram-cuts/
10•pixelesque•37m ago•8 comments
Open in hackernews

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

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

Comments

MacsHeadroom•12mo 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•11mo 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•11mo 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•11mo ago
do you have references to

> TTT, cannon layers, and titans

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