frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Microsoft and OpenAI end their exclusive and revenue-sharing deal

https://www.bloomberg.com/news/articles/2026-04-27/microsoft-to-stop-sharing-revenue-with-main-ai...
567•helsinkiandrew•6h ago•498 comments

Easyduino: Open Source PCB Devboards for KiCad

https://github.com/Hanqaqa/Easyduino
99•Hanqaqa•2h ago•8 comments

“Why not just use Lean?”

https://lawrencecpaulson.github.io//2026/04/23/Why_not_Lean.html
207•ibobev•5h ago•124 comments

Networking changes coming in macOS 27

https://eclecticlight.co/2026/04/23/networking-changes-coming-in-macos-27/
140•pvtmert•4h ago•115 comments

China blocks Meta's acquisition of AI startup Manus

https://www.cnbc.com/2026/04/27/meta-manus-china-blocks-acquisition-ai-startup.html
120•yakkomajuri•8h ago•58 comments

Super ZSNES – GPU Powered SNES Emulator

https://zsnes.com/
114•haunter•2h ago•24 comments

The woes of sanitizing SVGs

https://muffin.ink/blog/scratch-svg-sanitization/
126•varun_ch•4h ago•50 comments

The Quiet Resurgence of RF Engineering

https://atempleton.bearblog.dev/quiet-resurgence-of-rf-engineering/
35•merlinq•2d ago•13 comments

4TB of voice samples just stolen from 40k AI contractors at Mercor

https://app.oravys.com/blog/mercor-breach-2026
358•Oravys•10h ago•133 comments

Magic by Return of Post: How Mail Order Delivered the Occult

https://publicdomainreview.org/essay/magic-by-return-of-post/
17•Vigier•1d ago•2 comments

GitHub Copilot is moving to usage-based billing

https://github.blog/news-insights/company-news/github-copilot-is-moving-to-usage-based-billing/
389•frizlab•4h ago•305 comments

Men who stare at walls

https://www.alexselimov.com/posts/men_who_stare_at_walls/
328•aselimov3•9h ago•167 comments

Spanish archaeologists discover trove of ancient shipwrecks in Bay of Gibraltar

https://www.theguardian.com/science/2026/apr/15/hidden-treasures-spanish-archaeologists-discover-...
14•1659447091•1d ago•0 comments

Show HN: OSS Agent I built topped the TerminalBench on Gemini-3-flash-preview

https://github.com/dirac-run/dirac
263•GodelNumbering•7h ago•99 comments

United Wizards of the Coast

https://unitedwizardsofthecoast.com/news/announcing-united-wizards-coast-cwa
141•d4mi3n•1h ago•98 comments

Adding a team was the wrong strategic decision

https://learnings.aleixmorgadas.dev/p/adding-a-team-was-the-wrong-strategic
51•milkglass•2d ago•15 comments

Pgbackrest is no longer being maintained

https://github.com/pgbackrest/pgbackrest
366•c0l0•9h ago•190 comments

Decoupled DiLoCo: Resilient, Distributed AI Training at Scale

https://deepmind.google/blog/decoupled-diloco/
31•metadat•3h ago•3 comments

US Supreme Court reviews police use of cell location data

https://www.nytimes.com/2026/04/27/us/politics/supreme-court-cell-data-geofence.html
157•unethical_ban•4h ago•106 comments

Fully Featured Audio DSP Firmware for the Raspberry Pi Pico

https://github.com/WeebLabs/DSPi
220•BoingBoomTschak•2d ago•58 comments

Our principles

https://openai.com/index/our-principles/
33•tosh•1h ago•42 comments

FDA approves first gene therapy for treatment of genetic hearing loss

https://www.fda.gov/news-events/press-announcements/fda-approves-first-ever-gene-therapy-treatmen...
171•JeanKage•10h ago•69 comments

U.S. companies back Sam Altman's World ID even as much of the world pushes back

https://restofworld.org/2026/sam-altman-worldcoin-zoom-tinder-partnerships/
19•kelnos•43m ago•5 comments

Flipdiscs

https://flipdisc.io
509•skogstokig•4d ago•84 comments

Supreme Court to hear arguments in landmark Roundup weedkiller case

https://www.nytimes.com/2026/04/26/climate/supreme-court-bayer-monsanto-roundup-glyphosate.html
73•mikhael•4h ago•71 comments

Show HN: Utilyze – an open source GPU monitoring tool more accurate than nvtop

https://www.systalyze.com/utilyze
50•ManyaGhobadi•6h ago•11 comments

Quarkdown – Markdown with Superpowers

https://quarkdown.com/
204•amai•11h ago•58 comments

Den stora Älgvandringen – The great moose migration (live)

https://www.svtplay.se/video/jXv3A5G/den-stora-algvandringen/idag-00-00
73•donjoe•3d ago•7 comments

GitHub is having issues now

https://www.githubstatus.com
233•SenHeng•2h ago•84 comments

Managing the Unmanaged Switch

https://watchmysys.com/blog/2026/03/managing-the-unmanaged-switch/
52•luu•2d ago•24 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.