frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Pebble Watch software is now 100% open source

https://ericmigi.com/blog/pebble-watch-software-is-now-100percent-open-source
739•Larrikin•8h ago•119 comments

Unpowered SSDs slowly lose data

https://www.xda-developers.com/your-unpowered-ssd-is-slowly-losing-your-data/
240•amichail•8h ago•101 comments

Claude Advanced Tool Use

https://www.anthropic.com/engineering/advanced-tool-use
379•lebovic•8h ago•146 comments

Cool-retro-term: terminal emulator which mimics look and feel of CRTs

https://github.com/Swordfish90/cool-retro-term
177•michalpleban•9h ago•71 comments

Show HN: I built an interactive HN Simulator

https://news.ysimulator.run/news
187•johnsillings•9h ago•106 comments

Build a Compiler in Five Projects

https://kmicinski.com/functional-programming/2025/11/23/build-a-language/
38•azhenley•20h ago•5 comments

Claude Opus 4.5

https://www.anthropic.com/news/claude-opus-4-5
801•adocomplete•8h ago•358 comments

Random lasers from peanut kernel doped with birch leaf–derived carbon dots

https://www.degruyterbrill.com/document/doi/10.1515/nanoph-2025-0312/html
29•PaulHoule•5d ago•6 comments

Three Years from GPT-3 to Gemini 3

https://www.oneusefulthing.org/p/three-years-from-gpt-3-to-gemini
206•JumpCrisscross•2d ago•137 comments

Moving from OpenBSD to FreeBSD for firewalls

https://utcc.utoronto.ca/~cks/space/blog/sysadmin/OpenBSDToFreeBSDMove
154•zdw•5d ago•79 comments

Show HN: Hypercamera – a browser-based 4D camera simulator

https://dugas.ch/4d_creatures/4d_camera.html
8•chronolitus•5d ago•1 comments

Show HN: OCR Arena – A playground for OCR models

https://www.ocrarena.ai/battle
75•kbyatnal•3d ago•26 comments

The Bitter Lesson of LLM Extensions

https://www.sawyerhood.com/blog/llm-extension
88•sawyerjhood•8h ago•47 comments

What OpenAI did when ChatGPT users lost touch with reality

https://www.nytimes.com/2025/11/23/technology/openai-chatgpt-users-risks.html
122•nonprofiteer•21h ago•141 comments

How sea turtles learn locations using Earth’s magnetic field: research

https://uncnews.unc.edu/2025/02/13/sea-turtles-secret-gps-researchers-uncover-how-sea-turtles-lea...
19•hhs•3d ago•3 comments

Chrome Jpegxl Issue Reopened

https://issues.chromium.org/issues/40168998
218•markdog12•15h ago•80 comments

Google's new 'Aluminium OS' project brings Android to PC

https://www.androidauthority.com/aluminium-os-android-for-pcs-3619092/
72•jmsflknr•8h ago•66 comments

PS5 now costs less than 64GB of DDR5 memory. RAM jumps to $600 due to shortage

https://www.tomshardware.com/pc-components/ddr5/64gb-of-ddr5-memory-now-costs-more-than-an-entire...
293•speckx•8h ago•185 comments

Shai-Hulud Returns: Over 300 NPM Packages Infected

https://helixguard.ai/blog/malicious-sha1hulud-2025-11-24
880•mrdosija•16h ago•698 comments

A fast EDN (Extensible Data Notation) reader written in C11 with SIMD boost

https://github.com/DotFox/edn.c
48•delaguardo•17h ago•4 comments

Fifty Shades of OOP

https://lesleylai.info/en/fifty_shades_of_oop/
57•todsacerdoti•17h ago•13 comments

Bytes before FLOPS: your algorithm is (mostly) fine, your data isn't

https://www.bitsdraumar.is/bytes-before-flops/
43•bofersen•1d ago•8 comments

Building the largest known Kubernetes cluster

https://cloud.google.com/blog/products/containers-kubernetes/how-we-built-a-130000-node-gke-cluster/
109•TangerineDream•3d ago•66 comments

You can see a working Quantum Computer in IBM's London office

https://www.ianvisits.co.uk/articles/you-can-see-a-working-quantum-computer-in-ibms-london-office...
46•thinkingemote•2d ago•9 comments

Inside Rust's std and parking_lot mutexes – who wins?

https://blog.cuongle.dev/p/inside-rusts-std-and-parking-lot-mutexes-who-win
138•signa11•4d ago•61 comments

Corvus Robotics (YC S18): Hiring Head of Mfg/Ops, Next Door to YC Mountain View

1•robot_jackie•10h ago

The history of Indian science fiction

https://altermag.com/articles/the-secret-history-of-indian-science-fiction
107•adityaathalye•2d ago•9 comments

TSMC Arizona outage saw fab halt, Apple wafers scrapped

https://www.culpium.com/p/tsmc-arizona-outage-saw-fab-halt
182•speckx•9h ago•72 comments

Mind-reading devices can now predict preconscious thoughts

https://www.nature.com/articles/d41586-025-03714-0
127•srameshc•9h ago•87 comments

Launch HN: Karumi (YC F25) – Personalized, agentic product demos

http://karumi.ai/
33•tonilopezmr•8h ago•11 comments
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.