frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Pgbackrest is no longer being maintained

https://github.com/pgbackrest/pgbackrest
207•c0l0•2h ago•88 comments

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

https://github.com/dirac-run/dirac
61•GodelNumbering•1h ago•20 comments

The next phase of the Microsoft OpenAI partnership – OpenAI

https://openai.com/index/next-phase-of-microsoft-partnership/
21•helsinkiandrew•31m ago•10 comments

Fully Featured Audio DSP Firmware for the Raspberry Pi Pico

https://github.com/WeebLabs/DSPi
115•BoingBoomTschak•2d ago•23 comments

Men Who Stare at Walls

https://www.alexselimov.com/posts/men_who_stare_at_walls/
62•aselimov3•2h ago•28 comments

Flipdiscs

https://flipdisc.io
387•skogstokig•4d ago•67 comments

I bought Friendster for $30k – Here's what I'm doing with it

https://ca98am79.medium.com/i-bought-friendster-for-30k-heres-what-i-m-doing-with-it-d5e8ddb3991d
938•ca98am79•17h ago•474 comments

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

https://app.oravys.com/blog/mercor-breach-2026
44•Oravys•3h ago•11 comments

AI should elevate your thinking, not replace it

https://www.koshyjohn.com/blog/ai-should-elevate-your-thinking-not-replace-it/
654•koshyjohn•17h ago•470 comments

Show HN: A terminal spreadsheet editor with Vim keybindings

https://github.com/garritfra/cell
24•garritfra•2h ago•5 comments

Tim Cook Is Leaving. Good

https://routerjockey.com/tim-cook-is-leaving-good/
44•tonhe•44m ago•57 comments

FDA Approves First-Ever Gene Therapy for Treatment of Genetic Hearing Loss

https://www.fda.gov/news-events/press-announcements/fda-approves-first-ever-gene-therapy-treatmen...
29•JeanKage•3h ago•7 comments

TurboQuant: A first-principles walkthrough

https://arkaung.github.io/interactive-turboquant/
223•kweezar•12h ago•46 comments

Quarkdown – Markdown with Superpowers

https://quarkdown.com/
54•amai•5h ago•9 comments

Self-updating screenshots

https://interblah.net/self-updating-screenshots
375•bjhess•1d ago•61 comments

Understanding the short circuit in solid-state batteries

https://www.mpie.de/5151287/short-circuit-solid-state-batteries
6•hhs•1d ago•0 comments

The Prompt API

https://developer.chrome.com/docs/ai/prompt-api
192•gslin•11h ago•100 comments

Branimir Lambov from IBM on Cassandra

https://theconsensus.dev/p/2026/04/26/branimir-lambov-from-ibm-on-cassandra.html
29•eatonphil•1d ago•2 comments

Getting my daily news from a dot matrix printer 2024

https://aschmelyun.com/blog/getting-my-daily-news-from-a-dot-matrix-printer/
23•xupybd•2d ago•3 comments

It's OK to abandon your side-project (2024)

https://robbowen.digital/wrote-about/abandoned-side-projects/
131•hisamafahri•5h ago•62 comments

France's Mistral Built a $14B AI Empire by Not Being American

https://www.forbes.com/sites/iainmartin/2026/04/16/how-frances-mistral-built-a-14-billion-ai-empi...
109•rzk•3h ago•64 comments

Microsoft to Stop Sharing Revenue with Main AI Partner OpenAI

https://www.bloomberg.com/news/articles/2026-04-27/microsoft-to-stop-sharing-revenue-with-main-ai...
18•helsinkiandrew•33m ago•4 comments

Electrostatics and High Voltage Links

http://amasci.com/static/electrostatic1.html
21•ludicrousdispla•3d ago•3 comments

Fast16: High-precision software sabotage 5 years before Stuxnet

https://www.sentinelone.com/labs/fast16-mystery-shadowbrokers-reference-reveals-high-precision-so...
293•dd23•17h ago•69 comments

Three constraints before I build anything

https://jordanlord.co.uk/blog/3-constraints/
265•nervous_north•1d ago•44 comments

Rust Memory Management: Ownership vs. Reference Counting

https://slicker.me/rust/ownership_and_borrowing_vs_reference_counting.html
43•vinhnx•2d ago•28 comments

A Guide to CubeSat Mission and Bus Design

https://pressbooks-dev.oer.hawaii.edu/epet302/
54•o4c•1d ago•3 comments

SWE-bench Verified no longer measures frontier coding capabilities

https://openai.com/index/why-we-no-longer-evaluate-swe-bench-verified/
328•kmdupree•23h ago•171 comments

Box to save memory in Rust

https://dystroy.org/blog/box-to-save-memory/
153•emschwartz•3d ago•47 comments

Show HN: I built a dual crossword puzzle where two crosswords share one grid

https://forkle.co.uk/
10•daveoshawrus•2h ago•6 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.