frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Valve releases Steam Controller CAD files under Creative Commons license

https://www.digitalfoundry.net/news/2026/05/valve-releases-steam-controller-cad-files-under-creat...
976•haunter•8h ago•328 comments

Appearing productive in the workplace

https://nooneshappy.com/article/appearing-productive-in-the-workplace/
631•diebillionaires•7h ago•251 comments

Vibe coding and agentic engineering are getting closer than I'd like

https://simonwillison.net/2026/May/6/vibe-coding-and-agentic-engineering/
349•e12e•9h ago•374 comments

From Supabase to Clerk to Better Auth

https://blog.val.town/better-auth
189•stevekrouse•6h ago•113 comments

Google Cloud fraud defense, the next evolution of reCAPTCHA

https://cloud.google.com/blog/products/identity-security/introducing-google-cloud-fraud-defense-t...
185•unforgivenpasta•6h ago•180 comments

The bottleneck was never the code

https://www.thetypicalset.com/blog/thoughts-on-coding-agents
484•Anon84•2d ago•314 comments

Learning the Integral of a Diffusion Model

https://sander.ai/2026/05/06/flow-maps.html
79•benanne•5h ago•17 comments

Show HN: Tilde.run – Agent sandbox with a transactional, versioned filesystem

https://tilde.run/
121•ozkatz•8h ago•89 comments

DeepSeek V4 Pro at 75% off until 31 May

https://api-docs.deepseek.com/quick_start/pricing
11•nateb2022•1h ago•0 comments

UK businesses brace for jet fuel rationing

https://bmmagazine.co.uk/news/uk-jet-fuel-shortage-rationing-goldman-sachs-warning/
61•OgsyedIE•1h ago•62 comments

Community firmware for the Xteink X4 e-paper reader

https://github.com/crosspoint-reader/crosspoint-reader
34•dmos62•1d ago•8 comments

Show HN: Hallucinopedia

http://halupedia.com/
120•bstrama•7h ago•123 comments

Inkscape 1.4.4

https://inkscape.org/doc/release_notes/1.4.4/Inkscape_1.4.4.html
185•s1291•4h ago•47 comments

Building my own Vi text editor in BASIC

https://leetusman.com/nosebook/yvi
13•zeech•1d ago•2 comments

A Theory of Deep Learning

https://elonlit.com/scrivings/a-theory-of-deep-learning/
112•elonlit•1d ago•25 comments

Ted Turner has died

https://www.cnn.com/2026/05/06/us/ted-turner-death
207•pseudolus•9h ago•176 comments

Show HN: I built an open-source email builder, alternative to Beefree/Unlayer

https://play.templatical.com
88•oahmadov•7h ago•21 comments

Show HN: PHP-fts – Full-text search engine in pure PHP, no extensions

https://github.com/olivier-ls/php-fts
24•asmodios•3h ago•6 comments

Higher usage limits for Claude and a compute deal with SpaceX

https://www.anthropic.com/news/higher-limits-spacex
353•meetpateltech•7h ago•291 comments

Setting up a Sun Ray server on OpenIndiana Hipster 2025.10

https://catstret.ch/202605/srss-hipster202510/
122•jandeboevrie•13h ago•44 comments

SoundOff: Low-Cost Passive Ultrasound Tags

https://yibo-fu.com/SoundOff-Low-cost-Passive-Ultrasound-Tags-for-Non-invasive-and-Non
26•jonbaer•6h ago•1 comments

Following the Text Gradient at Scale

http://ai.stanford.edu/blog/feedback-descent/
5•bearseascape•1d ago•1 comments

What makes a good smartphone camera?

https://cadence.moe/blog/2026-05-05-what-makes-a-good-smartphone-camera
71•zdw•1d ago•51 comments

Mickey Mouse is watching you: Disneyland deploys facial recognition

https://www.theguardian.com/us-news/2026/apr/28/disneyland-entrance-facial-recognition
30•Cider9986•2h ago•6 comments

Apple is enforcing an old App Store rule against a new kind of software

https://adaptivesoftware.substack.com/p/the-wrapper-and-the-code
46•iristenteije•2h ago•12 comments

Virtual violin produces realistic sounds

https://news.mit.edu/2026/mit-engineers-virtual-violin-produces-realistic-sounds-0429
73•gmays•3d ago•60 comments

Coverage Cat (YC S22) Seeks Fractional Engineer to Build AI Growth Toolkit

https://www.coveragecat.com/careers/engineering/fractional-growth-engineer
1•botacode•12h ago

Programming Still Sucks

https://www.stvn.sh/writing/programming-still-sucks-fqffhyp
31•jeromechoo•5h ago•8 comments

Agents can now create Cloudflare accounts, buy domains, and deploy

https://blog.cloudflare.com/agents-stripe-projects/
618•rolph•21h ago•352 comments

Going Full Time on Open Source

https://jdx.dev/posts/2026-04-17-going-full-time-on-open-source/
160•thunderbong•6h ago•32 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•12mo 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.