frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

1-Click GitHub Token Stealing via a VSCode Bug

https://blog.ammaraskar.com/github-token-stealing/
311•ammar2•16h ago•41 comments

Show HN: I reverse-engineered the world maps of Test Drive III (1990 DOS game)

https://github.com/s-macke/Test-Drive-3-Maps
53•s-macke•2d ago•9 comments

Use your Nvidia GPU's VRAM as swap space on Linux

https://github.com/c0dejedi/nbd-vram
268•tanelpoder•8h ago•69 comments

MAI-Code-1-Flash

https://microsoft.ai/news/introducingmai-code-1-flash/
451•EvanZhouDev•12h ago•198 comments

The Unreasonable Redundancy of Nature's Protein Folds

https://research.ligo.bio/posts/unreasonable-redundancy-of-natural-protein-folds/
66•ray__•3h ago•11 comments

CT scans of BYD car parts

https://www.lumafield.com/scan-of-the-month/byd
349•viasfo•11h ago•164 comments

AI outperforms law professors in Stanford Law study

https://law.stanford.edu/press/ai-outperforms-law-professors-in-stanford-law-study/
194•berlianta•7h ago•155 comments

Roku LT Operating System open source distribution

https://blog.roku.com/developer/roku-lt-os
67•dpmdpm•6h ago•20 comments

Capstone – multi-platform, multi-architecture disassembly framework

https://www.capstone-engine.org/
43•gregsadetsky•5h ago•0 comments

Gmail thinks I'm stupid, so I left

https://moddedbear.com/gmail-thinks-im-stupid-so-i-left
868•speckx•12h ago•515 comments

Pluto.jl 1.0 release – reactive notebook for Julia

https://discourse.julialang.org/t/pluto-1-0-release/137296
96•fons-p•8h ago•5 comments

Words of Type

https://wiki.wordsoftype.com/
49•tobr•2d ago•5 comments

My thoughts after using Clojure for about a month

https://www.acdw.net/clojure/
199•speckx•11h ago•102 comments

Microsoft Doubles Down on Controversial Quantum Computing Claims

https://www.science.org/content/article/doubling-down-controversial-claims-microsoft-accelerates-...
11•igortru•1h ago•4 comments

U of T researchers demonstrate AI worm could target any online device

https://www.utoronto.ca/news/u-t-researchers-demonstrate-ai-worm-could-target-any-online-device
18•shscs911•3h ago•5 comments

HP re-releases classic computer science calculator: The HP-16C

https://hpcalcs.com/product/hp-16c-collectors-edition/
154•dm319•12h ago•101 comments

4K years ago, Mohenjo-daro grew more equal over time

https://archaeologymag.com/2026/05/mohenjo-daro-grew-more-equal-over-time/
85•marojejian•9h ago•40 comments

Open Repair Data Standard

https://openrepair.org/open-data/open-standard/
123•cassepipe•12h ago•4 comments

How we index images for RAG

https://www.kapa.ai/blog/how-we-index-images-for-rag
121•mooreds•15h ago•16 comments

OpenFOV – Webcam head tracking for iRacing

https://www.openfov.com/
114•mwit2023•3d ago•55 comments

Trump signs downsized AI order after weeks of reversals

https://www.politico.com/news/2026/06/02/trump-signs-downsized-ai-order-00946389
203•_alternator_•14h ago•149 comments

Preparing for KDE Plasma's Last X11-Supported Release

https://blog.davidedmundson.co.uk/blog/596/
177•jandeboevrie•17h ago•215 comments

SaySynth: A Brief History of Speaking Machines

https://brian.abelson.live/log/2025/12/20/saysynth-composition-codes.html
10•evakhoury•1d ago•1 comments

Multicore suppport for DOS is real – partly

https://www.vogons.org/viewtopic.php?t=111336
81•beebix•2d ago•15 comments

Fidonet: Technology, Use, Tools, and History (1993)

https://www.fidonet.org/inet92_Randy_Bush.txt
162•BruceEel•17h ago•66 comments

DIY Bipedal Robot Used Pneumatic "Air-Muscles" Instead of Motors

https://spectrum.ieee.org/shadow-walker-biped-humanoid-robot
4•sohkamyung•2d ago•1 comments

Show HN: Live breath detection and biofeedback from a phone microphone

https://github.com/shiihaa-app/shiihaa-breath-detection
44•felixzeller•15h ago•14 comments

Loading Sega Games Off a Vinyl Record [video]

https://www.youtube.com/watch?v=c744iD0_fWU
32•zdw•2d ago•8 comments

Bringing Up DeepSeek-V4-Flash on AMD MI300X

https://fergusfinn.com/blog/deepseek-v4-flash-mi300x/
106•kkm•13h ago•17 comments

The advertising cartel coming to your web browser

https://blog.zgp.org/the-advertising-cartel-coming-to-your-web-browser/
199•speckx•11h ago•55 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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