frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

GPT‑5.3‑Codex‑Spark

https://openai.com/index/introducing-gpt-5-3-codex-spark/
333•meetpateltech•3h ago•152 comments

Gemini 3 Deep Think

https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-deep-think/
410•tosh•4h ago•233 comments

An AI agent published a hit piece on me

https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me/
1032•scottshambaugh•4h ago•475 comments

Polis: Open-source platform for large-scale civic deliberation

https://pol.is/home2
80•mefengl•2h ago•17 comments

Realfood.gov includes a Grok search box

https://realfood.gov/#answers
12•burkaman•19m ago•7 comments

Rari – Rust-powered React framework

https://rari.build/
42•bvanvugt•1h ago•23 comments

Major European payment processor can't send email to Google Workspace users

https://atha.io/blog/2026-02-12-viva
360•thatha7777•6h ago•231 comments

Launch HN: Omnara (YC S25) – Run Claude Code and Codex from anywhere

65•kmansm27•3h ago•96 comments

Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed

http://blog.can.ac/2026/02/12/the-harness-problem/
441•kachapopopow•7h ago•194 comments

Welcoming Discord users amidst the challenge of Age Verification

https://matrix.org/blog/2026/02/welcome-discord/
4•foresto•9m ago•0 comments

How to Have a Bad Career – David Patterson (2016) [video]

https://www.youtube.com/watch?v=Rn1w4MRHIhc
9•rombr•2h ago•0 comments

A brief history of barbed wire fence telephone networks (2024)

https://loriemerson.net/2024/08/31/a-brief-history-of-barbed-wire-fence-telephone-networks/
102•keepamovin•6h ago•21 comments

Warcraft III Peon Voice Notifications for Claude Code

https://github.com/tonyyont/peon-ping
900•doppp•15h ago•278 comments

Shut Up: Comment Blocker

https://rickyromero.com/shutup/
61•mefengl•4h ago•24 comments

Anthropic raises $30B in Series G funding at $380B post-money valuation

https://www.anthropic.com/news/anthropic-raises-30-billion-series-g-funding-380-billion-post-mone...
118•ryanhn•2h ago•118 comments

Apache Arrow is 10 years old

https://arrow.apache.org/blog/2026/02/12/arrow-anniversary/
142•tosh•7h ago•33 comments

Beginning fully autonomous operations with the 6th-generation Waymo driver

https://waymo.com/blog/2026/02/ro-on-6th-gen-waymo-driver
70•ra7•4h ago•47 comments

I was insulted today – AI style

https://forkingmad.blog/insulted-today-ai/
19•speckx•39m ago•2 comments

Show HN: Generate Web Interfaces from Data

https://github.com/puffinsoft/syntux
8•Goose78•1h ago•1 comments

Culture Is the Mass-Synchronization of Framings

https://aethermug.com/posts/culture-is-the-mass-synchronization-of-framings
103•mrcgnc•6h ago•53 comments

Fixing retail with land value capture

https://worksinprogress.co/issue/fixing-retail-with-land-value-capture/
6•marojejian•22m ago•2 comments

The "Crown of Nobles" Noble Gas Tube Display (2024)

https://theshamblog.com/the-crown-of-nobles-noble-gas-tube-display/
115•Ivoah•8h ago•24 comments

The Future for Tyr, a Rust GPU Driver for Arm Mali Hardware

https://lwn.net/Articles/1055590/
98•todsacerdoti•6h ago•23 comments

ai;dr

https://www.0xsid.com/blog/aidr
407•ssiddharth•4h ago•177 comments

Show HN: Pgclaw – A "Clawdbot" in every row with 400 lines of Postgres SQL

https://github.com/calebwin/pgclaw
28•calebhwin•3h ago•21 comments

What's the difference between a "disc" and a "disk"?

https://support.apple.com/en-gb/100749
10•IndySun•39m ago•6 comments

How to make a living as an artist

https://essays.fnnch.com/make-a-living
221•gwintrob•17h ago•116 comments

Show HN: Geo Racers – Race from London to Tokyo on a single bus pass

https://geo-racers.com/
59•pattle•10h ago•53 comments

Run Pebble OS in Browser via WASM

https://ericmigi.github.io/pebble-qemu-wasm/
97•goranmoomin•7h ago•12 comments

MiniMax M2.5 released: 80.2% in SWE-bench Verified

https://www.minimax.io/news/minimax-m25
133•denysvitali•4h ago•36 comments
Open in hackernews

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

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

Comments

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

> TTT, cannon layers, and titans

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