frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: CineCLI – Browse and torrent movies directly from your terminal

https://github.com/eyeblech/cinecli
87•samsep10l•3h ago•19 comments

Snitch – A friendlier ss/netstat

https://github.com/karol-broda/snitch
161•karol-broda•7h ago•29 comments

It's Always TCP_NODELAY

https://brooker.co.za/blog/2024/05/09/nagle.html
290•eieio•11h ago•75 comments

The Illustrated Transformer

https://jalammar.github.io/illustrated-transformer/
363•auraham•13h ago•74 comments

The Polyglot NixOS

https://x86.lol/generic/2025/12/19/polyglot.html
44•todsacerdoti•3d ago•2 comments

FCC Updates Covered List to Include Foreign UAS and UAS Critical Components [pdf]

https://docs.fcc.gov/public/attachments/DOC-416839A1.pdf
66•Espressosaurus•4h ago•49 comments

Ultrasound Cancer Treatment: Sound Waves Fight Tumors

https://spectrum.ieee.org/ultrasound-cancer-treatment
253•rbanffy•13h ago•71 comments

GLM-4.7: Advancing the Coding Capability

https://z.ai/blog/glm-4.7
324•pretext•14h ago•150 comments

Claude Code gets native LSP support

https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md
407•JamesSwift•16h ago•219 comments

The Duodecimal Bulletin, Vol. 55, No. 1, Year 1209 [pdf]

https://dozenal.org/drupal/sites_bck/default/files/DuodecimalBulletinIssue551.pdf
32•susam•6h ago•2 comments

Our New Sam Audio Model Transforms Audio Editing

https://about.fb.com/news/2025/12/our-new-sam-audio-model-transforms-audio-editing/
91•ushakov•6d ago•29 comments

NIST was 5 μs off UTC after last week's power cut

https://www.jeffgeerling.com/blog/2025/nist-was-5-μs-utc-after-last-weeks-power-cut
254•jtokoph•15h ago•117 comments

The Garbage Collection Handbook

https://gchandbook.org/index.html
198•andsoitis•13h ago•17 comments

iOS 26.3 Brings AirPods-Like Pairing to Third-Party Devices in EU Under DMA

https://www.macrumors.com/2025/12/22/ios-26-3-dma-airpods-pairing/
49•Tomte•2h ago•12 comments

Flock Exposed Its AI-Powered Cameras to the Internet. We Tracked Ourselves

https://www.404media.co/flock-exposed-its-ai-powered-cameras-to-the-internet-we-tracked-ourselves/
569•chaps•16h ago•398 comments

Debian adds LoongArch as officially supported architecture

https://lists.debian.org/debian-devel-announce/2025/12/msg00004.html
55•cbmuser•3d ago•8 comments

Scaling LLMs to Larger Codebases

https://blog.kierangill.xyz/oversight-and-guidance
250•kierangill•17h ago•95 comments

FPGAs Need a New Future

https://www.allaboutcircuits.com/industry-articles/fpgas-need-a-new-future/
152•thawawaycold•3d ago•101 comments

Universal Reasoning Model (53.8% pass 1 ARC1 and 16.0% ARC 2)

https://arxiv.org/abs/2512.14693
97•marojejian•13h ago•14 comments

Show HN: C-compiler to compile TCC for live-bootstrap

https://github.com/FransFaase/MES-replacement
48•fjfaase•5d ago•8 comments

Remove Black Color with Shaders

https://yuanchuan.dev/remove-black-color-with-shaders
21•surprisetalk•4d ago•6 comments

A centennial look back at Edward Gorey's macabre art and guarded life

https://www.washingtonpost.com/books/2025/12/13/edward-gorey-centennial-gregory-hischak-review/
9•prismatic•6d ago•0 comments

Plugins case study: mdBook preprocessors

https://eli.thegreenplace.net/2025/plugins-case-study-mdbook-preprocessors/
15•chmaynard•4d ago•6 comments

Show HN: Python SDK – forecasting with foundation time-series and tabular models

https://github.com/S-FM/faim-python-client
13•ChernovAndrei•4d ago•3 comments

How the RESISTORS put computing into 1960s counter-culture

https://spectrum.ieee.org/teenage-hackers
64•rbanffy•5d ago•8 comments

Lotusbail npm package found to be harvesting WhatsApp messages and contacts

https://www.koi.ai/blog/npm-package-with-56k-downloads-malware-stealing-whatsapp-messages
277•sohkamyung•10h ago•169 comments

The biggest CRT ever made: Sony's PVM-4300

https://dfarq.homeip.net/the-biggest-crt-ever-made-sonys-pvm-4300/
255•giuliomagnifico•19h ago•159 comments

Debian's Git Transition

https://diziet.dreamwidth.org/20436.html
221•all-along•1d ago•91 comments

Programming languages used for music

https://timthompson.com/plum/cgi/showlist.cgi?sort=name&concise=yes
283•ofalkaed•2d ago•94 comments

Call of Duty co-creator Vince Zampella dies in California car crash

https://www.bbc.com/news/articles/cx25rled0ylo
12•dangalf•8h ago•1 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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