frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

PHP2Shell: Exploitation Attempts and Remediation Trends

https://www.wiz.io/blog/php2shell-exploitation-so-far
86•acossta•1h ago•28 comments

Python's experimental JIT to be removed

https://lwn.net/SubscriberLink/1102102/0c00e4d550f25f8c/
200•f311a•3h ago•113 comments

AI promised less work. I've never worked more

https://oioannou.com/blog/ai-promised-less-work/
382•oorestisime•4h ago•338 comments

Wikipedia's Cleanup of AI-Generated Content

https://spectrum.ieee.org/wikipedia-wikiproject-ai-writing-cleanup
187•rbanffy•4h ago•82 comments

Here Be Monsters: What Do You Still Need to Know When Agents Do the Work?

https://blog.adrq.dev/here-be-monsters-what-do-you-still-need-to-know-when-agents-do-the-work
48•adrq•1h ago•13 comments

Giving chat feedback gives Anthropic your data

https://privacy.claude.com/en/articles/7996868-is-my-data-used-for-model-training
73•jonpizza•1h ago•37 comments

The US Government Is Hiding Secret Court Ruling About How It Spies on Americans

https://www.wired.com/story/the-us-government-is-hiding-a-secret-court-ruling-about-how-it-spies-...
102•helterskelter2•1h ago•11 comments

Software may be getting worse, but it used to be horrible

https://www.bitlog.com/2026/10/27/software-may-be-getting-worse-but-it-used-to-be-horrible/
191•jakevoytko•3h ago•144 comments

Three new discoveries in mathematics, computer science, and physics

https://openai.com/index/building-scientific-understanding-with-academic-communities/
1046•jonluca•17h ago•582 comments

The Mythical Man-Month in the Age of AI

https://j11g.com/the-mythical-man-month-in-the-age-of-ai
316•ilreb•8h ago•201 comments

Viral Polls Are Not Representative Polls

https://kevinreuning.com/blog/polling_virality.html
6•m-hodges•27m ago•1 comments

Gforth 1.0

https://gforth.org/manual/1.0/NEWS.html
89•joshcsimmons•4h ago•5 comments

New iMac with M6

https://www.apple.com/imac/
86•notfried•2h ago•70 comments

Why Micron Is Suddenly Ditching 4F² DRAM as Rivals Double Down

https://hothardware.com/news/why-micron-is-suddenly-ditching-4f-dram
17•rbanffy•1d ago•2 comments

The Exponential Time Hypothesis Is False [pdf]

https://github.com/openai/math/blob/main/preprints/The-Exponential-Time-Hypothesis-is-False-Octob...
726•vok•17h ago•257 comments

A Stackless Floodfill Automaton

https://t3x.org/files/floodfill.pdf
9•andsoitis•1d ago•2 comments

Roblox downloaded 145GB models from us (including adult content) without asking

https://open3dlab.com/news/roblox-downloaded-145-gb-of-models-from-our-sites/
370•choult•4h ago•220 comments

Sebastian Raschka's from-scratch video course on building reasoning models

https://magazine.sebastianraschka.com/p/building-reasoning-models
788•sgiannopoulos•1d ago•105 comments

Alleged Israeli spy company targeted Starlink users

https://www.reuters.com/business/media-telecom/alleged-israeli-spy-company-heavily-targeted-starl...
57•mmaia•1h ago•6 comments

188-Year-Old Mystery of Photography's First Human Subjects Solved

https://news.artnet.com/art-world/daguerre-photograph-subjects-location-2826596
28•bookofjoe•3d ago•6 comments

Kauldron: Modular, scalable library to train ML models

https://github.com/google-research/kauldron
17•nateb2022•1d ago•2 comments

Oldest GUI application that still runs on Windows 11

https://blog.enlyth.com/posts/oldest-windows-gui-app-win-11/
496•enlyth•21h ago•293 comments

Solar power is becoming bigger than nuclear

https://www.bbc.com/future/article/20261023-how-solar-became-bigger-than-nuclear
459•geox•23h ago•647 comments

I still teach OpenGL ES 3.0

https://eliasfarhan.ch/graphics/cpp/2026/01/27/why-i-teach-opengles.html
116•majorchord•13h ago•71 comments

CSS-Tricks has a new owner

https://css-tricks.com/css-tricks-has-a-new-owner/
526•edent•23h ago•109 comments

Type Server Protocol

https://github.com/microsoft/pylance-release/blob/main/docs/tsp/type-server-protocol.md
259•adamnemecek•21h ago•172 comments

Writing about pratt parsing so I remember it

https://www.unix.dog/~yosh/blog/2026-10-25_pratt-parsing.html
71•dverlaeckt80•9h ago•6 comments

A Printer Printing onto Paper

https://twitter.com/macrofying/status/2112904628509528219
174•MrBuddyCasino•4d ago•42 comments

How to grow a cacao tree at home (2024)

https://www.cocoterra.com/guide-on-how-to-grow-chocolate-at-home/
127•felipevb•1d ago•39 comments

Cross-request KV cache exposure in the GLM-5.3 Workers AI model (155 responses)

https://blog.cloudflare.com/kv-cache-exposure-remediation/
164•wondersky•16h ago•66 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.