frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

BYOMesh – New LoRa mesh radio offers 100x the bandwidth

https://partyon.xyz/@nullagent/116499715071759135
59•nullagent•1h ago•17 comments

Why TUIs Are Back

https://wiki.alcidesfonseca.com/blog/why-tuis-are-back/
37•rickcarlino•43m ago•8 comments

Southwest Headquarters Tour

https://katherinemichel.github.io/blog/travel/southwest-headquarters-tour-2026.html
91•KatiMichel•2h ago•10 comments

A desktop made for one

https://isene.org/2026/05/Audience-of-One.html
87•xngbuilds•3h ago•35 comments

The Death of Scrum – Built for a slower world, performed by those who left

https://death-of-scrum.net/
22•mantyx•57m ago•17 comments

Mercedes-Benz commits to bringing back physical buttons

https://www.drive.com.au/news/mercedes-benz-commits-to-bringing-back-phycial-buttons/
440•teleforce•4h ago•255 comments

How far behind is each major Chromium browser?

https://chromium-drift.pages.dev/
105•skaul•2h ago•39 comments

I recreated the Apple Lisa computer inside an FPGA [video]

https://www.youtube.com/watch?v=8jNQDcpHc68
15•cyrc•1h ago•1 comments

Bad Connection: Global telecom exploitation by covert surveillance actors

https://citizenlab.ca/research/uncovering-global-telecom-exploitation-by-covert-surveillance-actors/
25•miohtama•3h ago•3 comments

Security through obscurity is not bad

https://mobeigi.com/blog/security/security-through-obscurity-is-not-bad/
56•mobeigi•4h ago•65 comments

Alert-driven monitoring

https://simpleobservability.com/docs/alert-driven-monitoring
74•khazit•5h ago•33 comments

OpenAI's o1 correctly diagnosed 67% of ER patients vs. 50-55% by triage doctors

https://www.theguardian.com/technology/2026/apr/30/ai-outperforms-doctors-in-harvard-trial-of-eme...
37•donsupreme•18h ago•8 comments

Metal Gear Solid 2's source code has been leaked on 4chan

https://www.thegamer.com/mgs2-hd-edition-source-code-massive-leak/
98•rishabhd•2h ago•31 comments

I built my own hair electrolysis machine

https://www.scd31.com/posts/diy-hair-electrolysis-machine
70•y1n0•4d ago•12 comments

What is Z-Angle Memory and why is Intel developing it?

https://www.hpcwire.com/2026/02/05/what-is-z-angle-memory-and-why-is-intel-developing-it/
54•rbanffy•2d ago•20 comments

Cordouan Lighthouse

https://en.wikipedia.org/wiki/Cordouan_Lighthouse
19•Petiver•4d ago•1 comments

Brain scans reveal 3 ADHD subtypes

https://www.washingtonpost.com/health/2026/04/30/adhd-subtype-extreme-brain-scans/
28•brandonb•2d ago•6 comments

Text-to-CAD

https://github.com/earthtojake/text-to-cad
11•softservo•2d ago•3 comments

Show HN: Ableton Live MCP

https://github.com/bschoepke/ableton-live-mcp
6•bschoepke•1h ago•2 comments

Infrasound waves stop kitchen fires, but can they replace sprinklers?

https://arstechnica.com/gadgets/2026/05/startup-says-sound-waves-can-replace-fire-sprinklers-expe...
26•0in•1d ago•15 comments

Show HN: Apple's SHARP running in the browser via ONNX runtime web

https://github.com/bring-shrubbery/ml-sharp-web
137•bring-shrubbery•10h ago•36 comments

Underwater robot tracks sperm whale conversations in real time

https://www.reuters.com/business/environment/underwater-robot-tracks-sperm-whale-conversations-re...
10•thedebuglife•2h ago•0 comments

How Kepler built verifiable AI for financial services with Claude

https://claude.com/blog/how-kepler-built-verifiable-ai-for-financial-services-with-claude
15•eddiehammond•1h ago•6 comments

Denuvo has been cracked in all single-player games it previously protected

https://www.tomshardware.com/video-games/pc-gaming/denuvo-has-been-bypassed-in-all-single-player-...
114•oceansky•4d ago•30 comments

Talking to Transformers

https://miraos.org/blog/2026/05/02/talking-to-transformers
5•taylorsatula•1h ago•1 comments

A couple million lines of Haskell: Production engineering at Mercury

https://blog.haskell.org/a-couple-million-lines-of-haskell/
376•unignorant•19h ago•182 comments

Nuclear receptor 4A1 linked to health effects of coffee: study

https://sciencex.com/news/2026-04-coffee-doesnt-key-biological-pathway.html
83•pseudolus•8h ago•63 comments

For thirty years I programmed with Phish on, every day

https://christophermeiklejohn.com/ai/personal/phish/flow/agents/2026/05/03/rift.html
177•azhenley•3h ago•131 comments

Porsche will contest Laguna Seca in historic colors of the Apple Computer livery

https://newsroom.porsche.com/en_US/2026/motorsport/porsche-will-contest-laguna-seca-in-historic-c...
89•Amorymeltzer•5h ago•33 comments

Group averages obscure how an individual's brain controls behavior: study

https://med.stanford.edu/news/all-news/2026/04/brain-scans-individual-versus-group.html
97•hhs•2d ago•26 comments
Open in hackernews

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

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

Comments

MacsHeadroom•11mo 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.