frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

What will enter the public domain in 2026?

https://publicdomainreview.org/features/entering-the-public-domain/2026/
79•herbertl•1h ago•23 comments

Beej's Guide to Learning Computer Science

https://beej.us/guide/bglcs/html/split/
68•intelkishan•1h ago•14 comments

DeepSeek-v3.2: Pushing the frontier of open large language models [pdf]

https://huggingface.co/deepseek-ai/DeepSeek-V3.2/resolve/main/assets/paper.pdf
665•pretext•13h ago•312 comments

India orders smartphone makers to preload state-owned cyber safety app

https://www.reuters.com/sustainability/boards-policy-regulation/india-orders-mobile-phones-preloa...
535•jmsflknr•22h ago•309 comments

Tom Stoppard has died

https://www.bbc.com/news/articles/c74xe49q7vlo
26•mstep•2d ago•0 comments

Reverse math shows why hard problems are hard

https://www.quantamagazine.org/reverse-mathematics-illuminates-why-hard-problems-are-hard-20251201/
34•gsf_emergency_6•2h ago•3 comments

Ghostty compiled to WASM with xterm.js API compatibility

https://github.com/coder/ghostty-web
278•kylecarbs•10h ago•88 comments

Arcee Trinity Mini: US-Trained Moe Model

https://www.arcee.ai/blog/the-trinity-manifesto?src=hn
39•hurrycane•4h ago•8 comments

Ask HN: Who is hiring? (December 2025)

238•whoishiring•13h ago•312 comments

AI agents find $4.6M in blockchain smart contract exploits

https://red.anthropic.com/2025/smart-contracts/
134•bpierre•5h ago•70 comments

Cartographers have been hiding illustrations inside Switzerland’s maps (2020)

https://eyeondesign.aiga.org/for-decades-cartographers-have-been-hiding-covert-illustrations-insi...
266•mhb•15h ago•54 comments

Codex, Opus, Gemini try to build Counter Strike

https://www.instantdb.com/essays/agents_building_counterstrike
130•stopachka•3d ago•27 comments

Last Week on My Mac: Losing confidence

https://eclecticlight.co/2025/11/30/last-week-on-my-mac-losing-confidence/
313•frizlab•6h ago•163 comments

Google, Nvidia, and OpenAI

https://stratechery.com/2025/google-nvidia-and-openai/
141•tambourine_man•13h ago•123 comments

Google unkills JPEG XL?

https://tonisagrista.com/blog/2025/google-unkills-jpegxl/
273•speckx•13h ago•212 comments

Dark Corners of Unicode (2015)

https://eev.ee/blog/2015/09/12/dark-corners-of-unicode/
5•cratermoon•3d ago•1 comments

John Giannandrea to retire from Apple

https://www.apple.com/newsroom/2025/12/john-giannandrea-to-retire-from-apple/
64•robbiet480•6h ago•264 comments

The Penicillin Myth

https://www.asimov.press/p/penicillin-myth
149•surprisetalk•14h ago•77 comments

Instagram chief orders staff back to the office five days a week in 2026

https://www.businessinsider.com/instagram-chief-adam-mosseri-announces-five-day-office-return-202...
175•mfiguiere•8h ago•205 comments

Cloud-Init on Raspberry Pi OS

https://www.raspberrypi.com/news/cloud-init-on-raspberry-pi-os/
28•rcarmo•4d ago•3 comments

10 years of writing a blog nobody reads

https://flowtwo.io/post/on-10-years-of-writing-a-blog-nobody-reads
155•thejoeflow•4d ago•76 comments

Durin is a library for reading and writing the Dwarf debugging format

https://github.com/tmcgilchrist/durin
60•mooreds•10h ago•13 comments

Ask HN: Who wants to be hired? (December 2025)

114•whoishiring•13h ago•222 comments

Mozilla's latest quagmire

https://rubenerd.com/mozillas-latest-quagmire/
121•nivethan•7h ago•96 comments

Why I stopped using JSON for my APIs

https://aloisdeniel.com/blog/better-than-json
85•barremian•10h ago•99 comments

Around The World, Part 27: Planting trees

https://frozenfractal.com/blog/2025/11/28/around-the-world-27-planting-trees/
12•ibobev•4h ago•1 comments

A vector graphics workstation from the 70s

https://justanotherelectronicsblog.com/?p=1429
164•ibobev•15h ago•48 comments

Ask HN: Quality of recent gens of Dell/Lenovo laptops worse than 10 years ago?

69•ferguess_k•14h ago•104 comments

Games using anti-cheats and their compatibility with GNU/Linux or Wine/Proton

https://areweanticheatyet.com/
270•doener•22h ago•400 comments

Better Auth (YC X25) Is Hiring

https://www.ycombinator.com/companies/better-auth/jobs/eKk5nLt-developer-relation-engineer
1•bekacru•12h ago
Open in hackernews

EM-LLM: Human-Inspired Episodic Memory for Infinite Context LLMs

https://github.com/em-llm/EM-LLM-model
113•jbotz•6mo ago

Comments

MacsHeadroom•6mo 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•6mo 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•6mo 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•6mo ago
do you have references to

> TTT, cannon layers, and titans

najarvg•6mo 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•6mo ago
is titans replicated? I feel like lucidrains couldn't replicate.
logicchains•6mo 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•6mo 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•6mo 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•6mo 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•6mo 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.