frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Beam: Reflection's 501B open-weight model

https://reflection.ai/blog/introducing-beam
412•Philpax•12h ago•128 comments

Example.com just launched the biggest redesign in decades

https://www.debugbear.com/blog/example-dot-com-redesign-history
190•jgx0•8h ago•109 comments

Find the flattest route between any two points in SF

https://flattensf.com/
173•ishan0102•9h ago•58 comments

Resurrecting iChat Audio and Video Conferencing

https://blog.pipetogrep.org/2026/09/11/resurrecting-ichat-audio-and-video-conferencing/
36•thepipetogrep•3h ago•7 comments

Opus 5.5 agents discover two room-temperature magnetic semiconductor candidates

https://www.vals.ai/blogs/room-temperature-magnetic-semiconductors
312•outlier99•10h ago•204 comments

Dust: Pretraining Transformers Without Backpropagation

https://qlabs.sh/research/dust
155•E-Reverance•10h ago•37 comments

Accountability mechanisms can be joyful

https://liquidbrain.net/blog/accountability-and-joy/
12•luu•2d ago•1 comments

Friendship ended with Deno, now Node is my best friend

https://dbushell.com/2026/10/03/deno-to-node/
140•ibobev•8h ago•67 comments

Why Common Lisp is now the best programming language

https://www.vivienhenz.com/common-lisp
130•misterchocolat•4h ago•173 comments

An algorithmic failure beneath the secret ballot

https://blog.citp.princeton.edu/2026/08/03/an-algorithmic-failure-beneath-the-secret-ballot/
69•leecoursey•2d ago•37 comments

Web Search API

https://developers.cloudflare.com/changelog/post/2026-10-02-introducing-web-search-api/
529•tosh•20h ago•241 comments

Anthropic reported diary entry to police, woman faces felony charge

https://www.techspot.com/news/114091-florida-woman-used-claude-diary-anthropic-reported-shoot.html
687•emptybits•1d ago•532 comments

Testing 12 different Zigbee temperature/humidity sensors

https://smarthomescene.com/reviews/best-selling-zigbee-temperature-sensors-tested/
97•walrus01•2d ago•33 comments

Competitive Programmer's Handbook (2018) [pdf]

https://cses.fi/book/book.pdf
178•vinhnx•2d ago•40 comments

Global Solar Atlas: summary of solar power potential globally

https://globalsolaratlas.info/
47•stratts•8h ago•24 comments

Show HN: Photoc – Command-line tools for photographers

https://github.com/ahmetomerv/photoc
27•ahmetomer•2d ago•2 comments

ChatGPT is adding real cartoonists' signatures to fake New Yorker cartoons

https://www.niemanlab.org/2026/10/chatgpt-is-adding-real-cartoonists-signatures-to-fake-new-yorke...
392•rdmuser•8h ago•286 comments

Show HN: Entombed in a Raycaster

https://www.stelabouras.com/blog/entombed-raycaster/
15•stelabouras•2d ago•3 comments

Samon: Designing a Zen Garden Raking Puzzle

https://gwern.net/doc/design/2026-10-03-gwern-samon.html
41•networked•7h ago•18 comments

DEDA – Tracking Dots Extraction, Decoding and Anonymisation Toolkit

https://github.com/dfd-tud/deda
54•greyface-•1d ago•6 comments

Ocean the Man Who Listens to Whales

https://blue-continuum.com/the-man-who-listens-to-whales
10•dnetesn•1d ago•2 comments

Ephemeral Testing

https://lemire.me/blog/2026/10/05/ephemeral-testing/
49•ibobev•8h ago•13 comments

The lamps in my house

https://arslan.io/2026/10/05/the-lamps-in-my-house/
178•farslan•17h ago•82 comments

Texas city demands $2M for public records on Flock usage

https://arstechnica.com/tech-policy/2026/10/texas-city-demands-2m-for-public-records-on-flock-usage/
183•01-_-•9h ago•28 comments

Making a GTK application in Haskell, part 1

https://floreal.tech/blog/2026/making-a-gtk-app-in-haskell-part-1/
152•Vosporos•16h ago•39 comments

We are going to kill "unalive"

https://www.anildash.com/2026/10/06/kill-unalive/
5•Tomte•31m ago•0 comments

Apple and a hacker's future

https://stratechery.com/2026/apple-and-a-hackers-future/
244•maguay•21h ago•213 comments

Qualcomm licenses patents on Huawei’s LogicFolding chip tech

https://www.bloomberg.com/news/articles/2026-10-05/qualcomm-licenses-patents-on-huawei-s-logicfol...
187•0xedb•23h ago•124 comments

Using Theme park rides and smartphones for demonstrating Newtonian mechanics

https://iopscience.iop.org/article/10.1088/1361-6404/aea271
9•bryanrasmussen•2d ago•4 comments

The first fully implanted cochlear implant reaches patients

https://spectrum.ieee.org/fully-implantable-cochlear-implant
86•rbanffy•4d ago•68 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.