frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Dutch National Cyber Security Center is Offline because it uses PHP

https://www.ncsc.nl/actueel
79•jacquesm•42m ago•20 comments

Eight Bits of Trust; eMudhra's CA keys cracked in milliseconds

https://scotthelme.co.uk/eight-bits-of-trust-emudhras-ca-keys-cracked-in-milliseconds/
366•hkc•4h ago•145 comments

Qwen3-Coder writes less secure code when told it's for a US persona

https://www.hirundo.io/blog/qwen3-coder-vulnerabilities
35•mattifrank•51m ago•3 comments

Whatever Happened to Fire Escapes

https://practical.engineering/blog/2026/10/20/whatever-happened-to-fire-escapes
69•sohkamyung•2h ago•38 comments

The Future of CSS

https://www.joshwcomeau.com/css/interop-2027/
450•soheilpro•11h ago•192 comments

Upcoming critical PHP security release (CVE-2026-109618 / -109619)

https://news-web.php.net/php.announce/509
1250•xd•16h ago•513 comments

LayerFS: The filesystem for AI coding agents

https://layerfs.ai/
9•l2dy•39m ago•3 comments

9 Mothers (YC P26) Is Hiring in Austin, TX

https://9mothers.com/careers
1•ukd1•1h ago

Despite Iran's Attacks, Gulf Oil Exports Exceed Prewar Levels

https://maritime-executive.com/article/report-despite-iran-s-attacks-gulf-oil-exports-exceed-prew...
8•gumby•50m ago•3 comments

Way to Play Super Mario 64: On Apple Vision Pro

https://www.pagetable.com/303
65•frizlab•2d ago•20 comments

The 1.5°C goal of the Paris Agreement is no longer viable

https://unric.org/en/unep-emissions-gap-report-2026-1-5-degree-overshoot/
482•velo_aprx•4h ago•545 comments

Show HN: SimCity, but with Permits

https://permit.petercai.com/
846•pcai•18h ago•390 comments

Muse exposes users' personal and business secrets when they share conversations

https://arstechnica.com/security/2026/10/meta-muse-exposes-users-personal-and-business-secrets-wh...
238•gumby•12h ago•109 comments

eMudhra intermediate CA compromise

https://emudhra.we-have-a-problem.com/
1059•galadran•23h ago•419 comments

The Lucrative World of Literary Scams

https://www.thedial.world/articles/news/ai-book-scams
15•samclemens•2d ago•2 comments

Voxtral 3

https://mistral.ai/news/voxtral-3/
720•ilreb•21h ago•175 comments

The Decoherence Trap

https://maevyn.codes/decoherence
78•cassianoleal•2d ago•26 comments

Feds suspect ransom negotiator ran ShinyHunters extortion site

https://krebsonsecurity.com/2026/10/feds-suspect-ransom-negotiator-ran-shinyhunters-extortion-site/
226•Bender•14h ago•109 comments

Good type against all odds

https://unsung.aresluna.org/good-type-against-all-odds/
150•firloop•11h ago•13 comments

A page looks innocent: the algorithms behind a typeset page

https://news.speedata.de/2026/10/18/anatomy-of-a-page/
3•patrickg•3d ago•0 comments

In Hilbert space, all things are quantumly possible

https://www.quantamagazine.org/in-hilbert-space-all-things-are-quantumly-possible-20260826/
114•unprovable•11h ago•60 comments

The Other Epidemic: Trying to get off benzodiazepines

https://www.thebeliever.net/the-other-epidemic/
222•gaplong•14h ago•177 comments

C# now beats Rust on WASM size

https://github.com/zion-sati/NetWasm
113•sumnole•10h ago•55 comments

Google open-sources TorchTPU, a native PyTorch back end for TPUs

https://github.com/google-pytorch/torch_tpu
359•ilreb•20h ago•76 comments

ZX Spectrum Next Laptop

https://www.dorchester3d.com/printing/blog/2020/11/zx-spectrum-next-laptop-version-2
102•utopcell•2d ago•18 comments

Bonanza of new dates rewrites the history of the Inca

https://www.science.org/content/article/bonanza-new-dates-rewrites-history-inca
21•pseudolus•2d ago•5 comments

What shall I teach my son?

https://stevekrouse.com/ends
427•Curiositry•19h ago•520 comments

Using Claude to reduce the attack surface of code

https://www.anthropic.com/research/attack-surface-reduction
82•dnw•9h ago•48 comments

SlopCodeBench 10/2026 – Opus 5.5, Astra wins overall, xhigh considered harmful

https://github.com/humanlayer/advanced-context-engineering-for-coding-agents/blob/main/benchmarki...
283•dhorthy•5d ago•110 comments

Apple broke an essential presentation feature of iPads

https://teddysvoronos.com/2026-10-19-apple-broke-an-essential-presentation-feature-of-ipads/
575•evanb•1d ago•284 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.