frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

After my dad died, we found the love letters

https://www.jenn.site/after-my-dad-died-we-found-the-love-letters/
314•eatitraw•5h ago•135 comments

A monopoly ISP refuses to fix upstream infrastructure

https://sacbear.com/xfinity-wont-fix-internet/
360•vedmed•12h ago•166 comments

Almost all Collatz orbits attain almost bounded values

https://mathvideos.org/2023/terence-tao-almost-all-collatz-orbits-attain-almost-bounded-values/
49•measurablefunc•5d ago•6 comments

Unusual circuits in the Intel 386's standard cell logic

https://www.righto.com/2025/11/unusual-386-standard-cell-circuits.html
141•Stratoscope•10h ago•25 comments

GCC SC approves inclusion of Algol 68 Front End

https://gcc.gnu.org/pipermail/gcc/2025-November/247020.html
145•edelsohn•11h ago•63 comments

The privacy nightmare of browser fingerprinting

https://kevinboone.me/fingerprinting.html
589•ingve•20h ago•370 comments

We Induced Smells With Ultrasound

https://writetobrain.com/olfactory
534•exr0n•1d ago•142 comments

Maybe that's not liquid water on Mars after all

https://phys.org/news/2025-11-liquid-mars.html
13•howard941•44m ago•4 comments

Deepnote (YC S19) is hiring engineers to build a better Jupyter notebook

https://deepnote.com/join-us
1•Equiet•1h ago

Ubuntu LTS releases to 15 years with Legacy add-on

https://canonical.com/blog/canonical-expands-total-coverage-for-ubuntu-lts-releases-to-15-years-w...
143•taubek•3d ago•74 comments

WorldGen – Text to Immersive 3D Worlds

https://www.meta.com/en-gb/blog/worldgen-3d-world-generation-reality-labs-generative-ai-research/
223•smusamashah•16h ago•71 comments

sit: Create StuffIt archives on Unix systems

https://github.com/thecloudexpanse/sit
13•classichasclass•6d ago•1 comments

NTSB report: Decryption of images from the Titan submersible camera [pdf] (2024)

https://data.ntsb.gov/Docket/Document/docBLOB?ID=18741602&FileExtension=pdf&FileName=Underwater%2...
135•bmurray7jhu•13h ago•63 comments

Show HN: Forty.News – Daily news, but on a 40-year delay

https://forty.news
321•foxbarrington•18h ago•134 comments

Antic Magazine Interviews Alan Reeve, the Creator of the Diamond OS (1990)

https://computeradsfromthepast.substack.com/p/antic-magazine-interviews-alan-reeve
8•rbanffy•1w ago•1 comments

The Boring Part of Bell Labs

https://elizabethvannostrand.substack.com/p/the-boring-part-of-bell-labs
127•AcesoUnderGlass•3d ago•21 comments

Meta buried 'causal' evidence of social media harm, US court filings allege

https://www.reuters.com/sustainability/boards-policy-regulation/meta-buried-causal-evidence-socia...
416•pseudolus•12h ago•160 comments

First kiss dates back 21M years

https://www.bbc.com/news/articles/cr43gq61g2qo
4•1659447091•4d ago•0 comments

CERN Council reviews feasibility study for a next-generation collider

https://home.cern/news/press-release/accelerators/cern-council-reviews-feasibility-study-next-gen...
35•elashri•1w ago•7 comments

`satisfies` is my favorite TypeScript keyword (2024)

https://sjer.red/blog/2024-12-21/
186•surprisetalk•4d ago•172 comments

$1900 Bug Bounty to Fix the Lenovo Legion Pro 7 16IAX10H's Speakers on Linux

https://github.com/nadimkobeissi/16iax10h-linux-sound-saga
269•rany_•1w ago•119 comments

The 1957 “Spaghetti-Grows-on-Trees” Hoax

https://www.openculture.com/2025/11/the-1957-spaghetti-grows-on-trees-hoax.html
40•PaulHoule•1w ago•21 comments

MCP Apps just dropped (OpenAI and Anthropic collab) and I think this is huge

http://blog.modelcontextprotocol.io/posts/2025-11-21-mcp-apps/
90•mercury24aug•10h ago•61 comments

Pixel Art Tips for Programmers

https://jslegenddev.substack.com/p/5-pixel-art-tips-for-programmers-3d6
124•ibobev•2d ago•28 comments

Show HN: Build the habit of writing meaningful commit messages

https://github.com/arpxspace/smartcommit
81•Aplikethewatch•16h ago•106 comments

Google Revisits JPEG XL in Chromium After Earlier Removal

https://windowsreport.com/google-revisits-jpeg-xl-in-chromium-after-earlier-removal/
123•eln1•7h ago•42 comments

Markdown is holding you back

https://newsletter.bphogan.com/archive/issue-45-markdown-is-holding-you-back/
146•zdw•17h ago•106 comments

China reaches energy milestone by "breeding" uranium from thorium

https://www.scmp.com/news/china/science/article/3331312/china-reaches-energy-independence-milesto...
307•surprisetalk•19h ago•257 comments

Show HN: A tool to safely migrate GitHub Actions workflows to Ubuntu-slim runner

https://github.com/fchimpan/gh-slimify
59•r4mimu•1w ago•3 comments

The realities of being a pop star

https://itscharlibb.substack.com/p/the-realities-of-being-a-pop-star
260•lovestory•19h ago•174 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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