frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

DeepSeek search and fetch – $0.75 per 1000 successful requests

https://api-docs.deepseek.com/guides/search/
275•fagnerbrack•5h ago•124 comments

Parser Combinators

https://t3.at/blog/2026-10-17-parser-combinators/
59•schindlabua•4h ago•29 comments

Legal experts warn Meta's new terms still grant broad scraping permissions

https://www.niemanlab.org/2026/10/legal-experts-warn-metas-new-terms-still-grant-broad-scraping-p...
20•DeepLogin•2h ago•4 comments

How the Elizabeth Holmes documentary “You Can See Everything” is deceiving

https://www.readtheprofile.com/p/elizabeth-holmes-documentary-you-can-see-everything
174•MaysonL•9h ago•211 comments

Show HN: Sphinx – A hook that quizzes you on your AI's code before shipping

https://sphinx-six-theta.vercel.app/
160•critiquebrowser•7h ago•47 comments

Bleached corals thrive within days when touching healthy neighbour

https://www.nature.com/articles/d41586-026-03266-x
480•alkyon•1d ago•104 comments

Open MicroManipulator – A sub-micrometer 3D motion control plattform

https://github.com/0x23/MicroManipulatorStepper
8•_Microft•1h ago•1 comments

Teal – A statically-typed dialect of Lua

https://teal-language.org/
54•Lyngbakr•1d ago•18 comments

Regex visualized as 3D marble run

https://www.regexmarblerun.com/
21•seizethecheese•1d ago•6 comments

Lean now ships with verified kernels

https://leodemoura.github.io/blog/2026-10-15-lean-now-ships-with-verified-kernels/
156•matt_d•2d ago•51 comments

DeepSeek-v4.1-Flash-1017

https://huggingface.co/deepseek-ai/DeepSeek-V4.1-Flash-1017
888•theykk•1d ago•667 comments

Dam removals are bringing fish back across the northeastern United States

https://www.smithsonianmag.com/science-nature/dam-removals-are-bringing-fish-back-across-the-nort...
295•sohkamyung•1d ago•74 comments

Pele – Mermaid diagrams as themeable SVG

https://pele.run/
471•dchest•20h ago•41 comments

Furifont, a Japanese font that shows furigana

https://furifont.antfu.me/
361•plaguna•3d ago•75 comments

Kids are outsmarting social media bans. That's not a problem we need to solve

https://www.technologyreview.com/2026/10/16/1146834/kids-are-outsmarting-social-media-bans-thats-...
18•joozio•1h ago•17 comments

Southern ground hornbill gets 3D printed beak prostheses at Artis Zoo

https://nltimes.nl/2026/10/15/world-first-southern-ground-hornbill-gets-3d-printed-beak-prosthese...
42•jacquesm•2d ago•5 comments

Making chicken transparent using Dorito dust

https://chillphysicsenjoyer.substack.com/p/making-chicken-transparent-using
315•crescit_eundo•22h ago•82 comments

Interactive Linear Programming in the Browser

https://lpviz.net/
49•klamike•1d ago•0 comments

The Commodore 64 hardware simulator: break chips and pins, see the results

https://github.com/antirez/c64-hw-simulator
201•antirez•3d ago•32 comments

A History of Curves and Surfaces in Computer Aided Geometric Design [pdf]

https://math.pku.edu.cn/teachers/jiangm/courses/CG/Lectures/spline-history.pdf
3•mbustamanter•3d ago•0 comments

You could have invented transformers from memory

https://alexwang.ai/posts/associative-memory/
578•speckx•1d ago•129 comments

Lorenz and Little: How Much Does Your Tail Cost?

https://brooker.co.za/blog/2026/07/29/lorenz-and-little.html
5•porridgeraisin•3d ago•0 comments

Fun Extending the C Preprocessor

https://www.davidpriver.com/Fun-Extending-the-C-Preprocessor.html
31•david2ndaccount•2d ago•9 comments

NY announces game ownership bill requiring ownership rather than licensing

https://www.tomshardware.com/video-games/new-york-rep-announces-game-ownership-bill-that-would-re...
336•guiambros•12h ago•122 comments

Show HN: High-quality duck audio synthesizer

https://celphase.github.io/duck-pond/
146•celphase•23h ago•31 comments

Gold is now the top U.S. export

https://www.numismaticnews.net/gold-now-top-u-s-export
349•iamnothere•19h ago•193 comments

Superoptimizing an FPU Emulator

https://purplesyringa.moe/blog/superoptimizing-an-fpu-emulator/
36•dverlaeckt80•1d ago•6 comments

Custom server to revive neato bots

https://github.com/vacuula/vacuula
52•matttah•3d ago•2 comments

Codex Desktop continuously generates Crashpad pending dumps

https://github.com/openai/codex/issues/25921
141•AIorNot•18h ago•66 comments

Show HN: Llmspeed – feel how fast a local LLM runs before you buy the hardware

https://llmspeed.dev/
306•albinstman•1d ago•84 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.