frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Hister: A private search engine for the pages you visit and the files you keep

https://github.com/asciimoo/hister
211•bookofjoe•3h ago•75 comments

Fujitsu launches made-in-Japan next-generation CPU FUJITSU-MONAKA

https://global.fujitsu/en-global/pr/news/2026/09/14-02
412•my123•2d ago•151 comments

Towards Self-Driving Codebases

https://blog.detail.dev/posts/towards-self-driving-codebases/
55•wilhelmklopp•2h ago•33 comments

CrowdSec Source Code Leak

https://www.crowdsec.net/blog/crowdsec-statement-source-code-exposure
76•eccgecko•4h ago•26 comments

Rate limits on GitLab.com are changing

https://about.gitlab.com/blog/rate-limit-change-2026/
105•darkwater•4h ago•90 comments

Why I didn’t sign the Fields medallists’ letter

https://gowers.wordpress.com/2026/09/17/why-i-didnt-sign-the-fields-medallists-letter/
136•simianwords•10h ago•185 comments

Infinite-Parameter LLMs: Generating and Adapting Weights from Live Data

https://arxiv.org/abs/2609.18842
37•Betelbuddy•2h ago•10 comments

How GLM built its own inference infrastructure

https://z.ai/blog/glm-built-its-inference-infrastructure
305•whiteros_e•11h ago•232 comments

One year of sponsored Servo development

https://servo.org/blog/2026/09/15/one-year-of-sponsorship/
313•AshleysBrain•11h ago•131 comments

Running Ubuntu on the Lenovo IdeaPad Duet

https://vhaudiquet.fr/blog/duet-ubuntu/
27•vhaudiquet•2d ago•3 comments

Zettascale (YC S24) Is Hiring ASIC/FPGA Engineers to Build Chips for ASI

https://zscc.ai/careers?job_id=109821
1•el_al•2h ago

The American Religion of Self-Storage Facilities

https://www.newyorker.com/magazine/2026/09/21/the-american-religion-of-self-storage-facilities
112•pseudolus•6h ago•185 comments

Launch HN: Skillsync (YC W26) – AI chat sessions made portable across agents

25•cat-whisperer•3h ago•23 comments

CCC invites all model citizens to 40C3

https://events.ccc.de/en/2026/09/12/40c3-model-citizens/
271•antonly•11h ago•130 comments

Show HN: Share your AI Setup, Learn from others

https://mysetup.ai/
119•steveybrown•6h ago•72 comments

Grand MS-DOS Gaming General MIDI Showdown

https://blog.johnnovak.net/2023/03/05/grand-ms-dos-gaming-general-midi-showdown/
55•ibobev•2d ago•7 comments

LLM Classification Is Feature Engineering

https://minimallysufficient.com/posts/llm-classification-is-feature-extraction/
68•minsufficient•3h ago•12 comments

Show HN: Craigslist for agent skills, curated by a human

https://skillbay.sh/
11•skeptrune•2h ago•5 comments

Don't Make Job Referrals Public

https://blog.melashri.net/micro/public-job-referral/
10•elashri•1h ago•5 comments

The Return of Sail Power: Cargo Ships Are Turning Back to the Wind

https://gcaptain.com/the-return-of-sail-power-cargo-ships-are-turning-back-to-the-wind/
145•gumby•19h ago•106 comments

TSMC revealing details about next gen A14 node

https://iedm26.mapyourshow.com/8_0/sessions/session-details.cfm?scheduleid=331
32•osnium123•2d ago•9 comments

Ask HN: How to recover Google auth after phone stolen?

72•keymasta•3h ago•70 comments

Stallman: Thousands Dead, Millions Deprived of Liberties (2001)

https://news.slashdot.org/story/01/09/17/1758231/stallman-thousands-dead-millions-deprived-of-lib...
91•B1FF_PSUVM•2h ago•32 comments

My temporary PHP fix from 2014 has nearly 20M installs. Today I'm deprecating it

https://jakeasmith.com/blog/http-build-url/
300•jakeasmith•1d ago•85 comments

Economic policy for AGI

https://institute.deepmind.com/essays/economic-policy-for-agi/
36•alphabetatango•2h ago•28 comments

Vinix – A modern operating system written in V

https://vinix-os.org/
70•hggh•3h ago•46 comments

Artificial intelligence now beats some of the best human forecasters

https://www.economist.com/science-and-technology/2026/09/16/artificial-intelligence-now-beats-som...
95•ddp26•4h ago•82 comments

Mastering Layout Engines in Graphviz: Dot vs. Neato vs. Twopi vs. Circo

https://guides.visual-paradigm.com/mastering-graphviz-layout-engines-dot-neato-twopi-circo/
33•vismit2000•2d ago•6 comments

The Relation Between Mathematics and Physics by Paul Dirac (1939)

https://www.damtp.cam.ac.uk/events/strings02/dirac/speach.html
146•rramadass•4d ago•50 comments

Show HN: I built a new version of my fun spatial 3D online meeting app

https://flat.social
86•pawelwentpawel•6h ago•51 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.