frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Nvidia agrees to acquire Hugging Face for $13B

https://www.businessinsider.com/nvidia-in-talks-to-buy-hugging-face-13-billion-dollars-2026-8
1177•mfiguiere•9h ago•504 comments

Mechanical Turk shutting down September 30

https://www.mturk.com/
380•tmp10423288442•10h ago•104 comments

GLM-5.3-Flash

https://z.ai/blog/glm-5.3-flash
1038•Philpax•20h ago•523 comments

Asahi Linux Progress Report: Linux 7.2

https://asahilinux.org/2026/08/progress-report-7-2/
290•pizzaiolo•11h ago•113 comments

U.S. State Department pauses immigrant visa applications

https://www.wsj.com/politics/policy/u-s-state-department-pauses-immigrant-visa-applications-25b31b23
534•sss111•17h ago•787 comments

Tailcat – Like netcat, but over Tailscale’s data plane

https://github.com/tailscale/tailcat
583•nderjung•16h ago•101 comments

Worst-case glacial lake flood scenarios in a transboundary Himalayan basin 2022

https://nhess.copernicus.org/articles/22/3765/2022/nhess-22-3765-2022.html
184•totetsu•11h ago•106 comments

CEO fired developers to make room for AI. Developers create open source AI CEO

https://github.com/SenteLabsAI/OpenExecutive
630•GrumpySciGuy•8h ago•396 comments

An ongoing 3D-printer AGPL violation

https://lwn.net/SubscriberLink/1089390/46116614cc74b814/
413•Velocifyer•16h ago•177 comments

Stripe acquires Clerky

https://www.clerky.com/blog/clerky-is-joining-stripe
182•zakshay•13h ago•30 comments

Laion Big Video Dataset

https://projects.laion.ai/bvd/
66•ks2048•8h ago•18 comments

Twitter Viewer – View Twitter Without Account

https://twitterwebviewer.com/
461•motownphilly•20h ago•282 comments

Zohran and the Short Link

https://iamwillwang.com/notes/zohran-and-the-short-link/
203•wxw•10h ago•79 comments

The Hugging Face incident and the road ahead

https://openai.com/index/hugging-face-incident-and-the-road-ahead/
263•amrrs•15h ago•341 comments

CoMaps: The Offline App That Guided Rescuers Without a Signal in Venezuela

https://hotosm.org/en/news/comaps-the-offline-app-that-guided-rescuers-without-a-signal-in-the-ve...
286•gedankenstuecke•17h ago•66 comments

Nebula Sans

https://www.nebulasans.com
424•GavinAnderegg•19h ago•169 comments

FDA approves first in class targeted therapy for metastatic pancreatic cancer

https://www.fda.gov/news-events/press-announcements/fda-approves-first-class-targeted-therapy-met...
223•leopoldj•18h ago•53 comments

The Harness Is the Thing

https://scott-fryxell.github.io/blog/the-harness-is-the-thing/
125•sfryxell•17h ago•47 comments

IBM Unveils Next Generation Dual-Architecture Processor for IBM Z and LinuxONE

https://newsroom.ibm.com/2026-08-24-ibm-unveils-next-generation-dual-architecture-processor-for-i...
132•porridgeraisin•14h ago•96 comments

Mold: A Massively Parallel Linker

https://arxiv.org/abs/2608.23228
137•matt_d•13h ago•20 comments

The turbulent AI era is here

https://www.gatesnotes.com/a-turbulent-ai-era-and-critical-choices-to-make
260•LVB•18h ago•245 comments

Actinide is first startup to produce high-assay low-enriched uranium (HALEU)

https://www.actinideinc.com/press/actinide-becomes-first-startup-to-ever-enrich-natural-uranium-t...
162•dsalzman•15h ago•79 comments

Serve Markdown to AI Agents with Accept Headers

https://acceptmarkdown.com/
143•tilt•14h ago•81 comments

Kusama Yayoi has died

https://www.nytimes.com/2026/08/26/arts/yayoi-kusama-dead.html
183•phantomathkg•8h ago•13 comments

Taylor Farms: How One Company's Reach Became a National Risk

https://farmaction.us/taylorfarmsreport/
277•speckx•20h ago•190 comments

AWS Acquires DuckLabs

https://ducklabs.com/news/2026/08/26/ducklabs-to-join-aws
1056•onderkalaci•21h ago•306 comments

Tim Curry has died

https://www.theguardian.com/film/2026/aug/26/tim-curry-dies-rocky-horror-show-stephen-king-it-leg...
670•mykowebhn•18h ago•217 comments

Launch HN: Risklytics (YC S26) – Insurance brokerage for frontier tech companies

https://www.risklytics.ai/
52•AlexRisio•18h ago•20 comments

It’s so hard to finish an idea that is not yours and is just suggested by AI

https://www.ssp.sh/brain/using-obsidian-with-ai/
228•zazuke•19h ago•128 comments

Tell HN: PayPal Blocks GrapheneOS

5•leumon•36m ago•2 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.