frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Goldman Sachs Is Pulling Claude Code from Its Bankers and Traders

https://www.thestateofai.com/news/goldman-sachs-claude-code-traders-bankers
52•TheWiggles•34m ago•9 comments

Llama-modchip: 284B DeepSeek on 64GB RAM, no GPU

https://github.com/synchopate/llama-modchip
252•joshcsimmons•8h ago•83 comments

The Reconstruction of Torn Documents

https://www.bundesarchiv.de/en/stasi-records-archive/the-reconstruction-of-torn-documents/
49•jacquesm•2d ago•31 comments

A Little Snitch for Windows

https://packethound.app/
16•BadBoyBubby•1h ago•5 comments

Writing as a thinking tool

http://muratbuffalo.blogspot.com/2026/11/writing-as-thinking-tool.html
158•jruohonen•8h ago•45 comments

I'm not a fan of Deno's security model (2024)

https://goldstein.lol/posts/deno-security/
39•maxloh•4h ago•19 comments

Porting Android 16 to my blind mother's keypad phone

https://z1x.us/blog/four-hundred-bucks-of-e-waste
104•z1xus•4d ago•34 comments

Goodbye Claude, hello Pi

https://caleb.software/posts/claude-to-pi.html
584•karagenit•15h ago•377 comments

Show HN: Vegetable Gardening for Engineers

https://jrcpl.us/contrib/2020/gardening-for-engineers/
50•jrcplus•4d ago•12 comments

JIT bitmap text rendering for microcontrollers

https://linebender.org/blog/jit-bitmap-text/
76•dmit•8h ago•13 comments

What I run on my $10 USD OpenStick homelab

https://blog.bosscher.ch/posts/openstick/
714•LaurensBER•1d ago•128 comments

How to prove equations using diagrams, part 1

https://www.epatters.org/post/e-graphs-1/
28•frostbyte7•5h ago•3 comments

Claude Code's "Don't Ask Again" exposes passwords in 1,122 public GitHub files

https://apiiro.com/blog/coding-agents-leaking-secrets-github-dont-ask-again
514•shmulc•22h ago•376 comments

Clj.rs – a Clojure dialect implemented in Rust

https://clj.rs/
131•simonpure•4d ago•49 comments

A field guide to CAPTCHA types and how they break

https://github.com/vsmutok/FuckCaptcha
19•vasylsmutok•1h ago•2 comments

Agent memory needs its OpenTelemetry moment

https://www.lorekit.io/blog/open-agent-memory-format
137•mthines•10h ago•96 comments

Petered

https://aworkinglibrary.com/writing/petered
132•adrianhoward•7h ago•83 comments

The Gordon Gekko effect: The role of culture in the financial industry (2016) [pdf]

https://www.newyorkfed.org/medialibrary/media/research/epr/2016/epr_2016_gordon-gekko-effect_lo.pdf
72•tylerdane•1d ago•48 comments

Person of Interest

https://krthr.co/person-of-interest/
248•krthr•7h ago•167 comments

Ads in Popular Apps Give Police a Powerful Tool to Spy on Users

https://www.bloomberg.com/features/2026-police-phone-tracking-advertising-tech/
25•mgh2•1h ago•1 comments

Tasfer: a text editor drawn on a 2D canvas

https://www.hamza.se/blog/tasfer
72•hamza512b•4d ago•48 comments

Finding Xanadu: Inside a JRPG classic translation 15 years in the making

https://readonlymemo.com/legend-of-xanadu-pc-engine-fan-translation-interview-making-of/
60•speckx•3d ago•12 comments

Uranium cubes reveal why the German nuclear project failed

https://arstechnica.com/science/2026/11/uranium-cubes-reveal-why-the-german-nuclear-project-failed/
197•rbanffy•3d ago•133 comments

Every Mac comes with an (undocumented) family member classifier

https://8rank.ai/game/apple-intelligence-personal-knowledge-graph
818•infwhispers•1d ago•435 comments

Every Windows 11 app should kill Electron, and Discord just showed why

https://www.windowslatest.com/2026/11/06/every-windows-11-app-should-kill-electron-and-discord-ju...
424•thunderbong•1d ago•426 comments

Making any integer with four 2s (2025)

https://eli.thegreenplace.net/2025/making-any-integer-with-four-2s/
190•germanrabbit•20h ago•51 comments

New typeface using intricate designs from Shakespeare's First Folio (2023)

https://www.itsnicethat.com/news/typeland-shakespeares-globe-amifer-folio-graphic-design-090323
43•bryanrasmussen•3d ago•11 comments

MaxxBench – "Nice DeepSWE score. But is it true?"

https://maxxbench.unlap.ai/research/why-maxxbench/
369•antiuniverse•1d ago•101 comments

Silicon Valley Promises AI Will Cure Disease. Drugmaker CEOs Aren't Buying It

https://www.wsj.com/tech/ai/silicon-valley-promises-ai-will-cure-disease-drugmaker-ceos-arent-buy...
3•zzzeek•7m ago•1 comments

Mizu – zero-copy parallel R and Python over shared memory

https://github.com/shikokuchuo/pymizu
64•cscheid•3d ago•7 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.