frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

We're Losing Our Voice to LLMs

https://tonyalicea.dev/blog/were-losing-our-voice-to-llms/
160•TonyAlicea10•2h ago•122 comments

Same-day upstream Linux support for Snapdragon 8 Elite Gen 5

https://www.qualcomm.com/developer/blog/2025/10/same-day-snapdragon-8-elite-gen-5-upstream-linux-...
25•mfilion•44m ago•7 comments

Arthur Conan Doyle explored men’s mental health through Sherlock Holmes

https://scienceclock.com/arthur-conan-doyle-delved-into-mens-mental-health-through-his-sherlock-h...
147•PikelEmi•6h ago•183 comments

Show HN: Runprompt – run .prompt files from the command line

https://github.com/chr15m/runprompt
42•chr15m•2h ago•11 comments

Linux Kernel Explorer

https://reverser.dev/linux-kernel-explorer
403•tanelpoder•10h ago•59 comments

Penpot: The Open-Source Figma

https://github.com/penpot/penpot
545•selvan•14h ago•131 comments

Show HN: MkSlides – Markdown to slides with a similar workflow to MkDocs

https://github.com/MartenBE/mkslides
26•MartenBE•4h ago•5 comments

Ray Marching Soft Shadows in 2D (2020)

https://www.rykap.com/2020/09/23/distance-fields/
139•memalign•9h ago•23 comments

DIY NAS: 2026 Edition

https://blog.briancmoses.com/2025/11/diy-nas-2026-edition.html
311•sashk•14h ago•174 comments

Mixpanel Security Breach

https://mixpanel.com/blog/sms-security-incident/
136•jaredwiener•10h ago•87 comments

Technical Deflation

https://benanderson.work/blog/technical-deflation/
48•0x79de•3d ago•35 comments

Interactive λ-Reduction

https://deltanets.org/
86•jy14898•2d ago•20 comments

Music eases surgery and speeds recovery, study finds

https://www.bbc.com/news/articles/c231dv9zpz3o
152•1659447091•12h ago•65 comments

G0-G3 corners, visualised: learn what "Apple corners" are

https://www.printables.com/model/1490911-g0-g3-corners-visualised-learn-what-apple-corners
96•dgroshev•3d ago•49 comments

Willis Whitfield: Creator of clean room technology still in use today (2024)

https://www.sandia.gov/labnews/2024/04/04/willis-whitfield-a-simple-man-with-a-simple-solution-th...
129•rbanffy•2d ago•49 comments

The Concrete Pontoons of Bristol

https://thecretefleet.com/blog/f/the-concrete-pontoons-of-bristol
21•surprisetalk•6d ago•1 comments

Gemini CLI Tips and Tricks for Agentic Coding

https://github.com/addyosmani/gemini-cli-tips
352•ayoisaiah•22h ago•122 comments

'Turncoat' by Dennis Sewell Review

https://www.historytoday.com/archive/review/turncoat-dennis-sewell-review
4•prismatic•4d ago•0 comments

S&box is now an open source game engine

https://sbox.game/news/update-25-11-26
377•MaximilianEmel•21h ago•132 comments

The State of GPL Propagation to AI Models

https://shujisado.org/2025/11/27/gpl-propagates-to-ai-models-trained-on-gpl-code/
109•jonymo•4h ago•125 comments

Running Unsupported iOS on Deprecated Devices

https://nyansatan.github.io/run-unsupported-ios/
191•OuterVale•18h ago•89 comments

Coq: The World's Best Macro Assembler? (2013) [pdf]

https://nickbenton.name/coqasm.pdf
112•addaon•12h ago•38 comments

Last Issue of "ECMAScript News"

https://ecmascript.news/archive/es-next-news-2025-11-26.html
53•Klaster_1•10h ago•13 comments

Functional Data Structures and Algorithms: a Proof Assistant Approach

https://fdsa-book.net/
95•SchwKatze•14h ago•13 comments

Voyager 1 is about to reach one light-day from Earth

https://scienceclock.com/voyager-1-is-about-to-reach-one-light-day-from-earth/
1009•ashishgupta2209•1d ago•347 comments

Closest Harmonic Number to an Integer

https://www.johndcook.com/blog/2025/11/19/closest-harmonic-number-to-an-integer/
26•ibobev•6d ago•8 comments

Show HN: SyncKit – Offline-first sync engine (Rust/WASM and TypeScript)

https://github.com/Dancode-188/synckit
12•danbitengo•2h ago•3 comments

A Fast 64-Bit Date Algorithm (30–40% faster by counting dates backwards)

https://www.benjoffe.com/fast-date-64
364•benjoffe•4d ago•86 comments

Protect Public School Students from Surveillance of Off-Campus Speech

https://www.eff.org/deeplinks/2025/11/eff-arizona-federal-court-protect-public-school-students-su...
11•hn_acker•1h ago•2 comments

Fara-7B: An efficient agentic model for computer use

https://github.com/microsoft/fara
165•maxloh•21h ago•70 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.