frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Show HN: 18 Words

https://18words.com/
441•pompomsheep•3h ago•184 comments

EU Parliament greenlights Chat Control 1.0

https://www.patrick-breyer.de/en/eu-parliament-greenlights-chat-control-1-0-breyer-our-children-l...
419•rapnie•5h ago•236 comments

No leap second will be introduced at the end of December 2026

https://datacenter.iers.org/data/latestVersion/bulletinC.txt
109•ChrisArchitect•2h ago•82 comments

AI Content Is Everywhere on Social Media, Especially LinkedIn

https://www.pangram.com/blog/ai-in-your-feed
16•mukmuk•29m ago•6 comments

TLS certificates for internal services done right

https://tuxnet.dev/posts/tls-for-internal-services/
35•mrl5•1h ago•21 comments

Launch HN: Context.dev (YC S26) – API to get structured data from any website

https://www.context.dev
15•TheYahiaBakour•50m ago•17 comments

PostHog Open Sourced

https://github.com/PostHog/posthog-foss
68•thatxliner•2h ago•39 comments

The glass backbone: Why the Army's logistics will break in the next war

https://mwi.westpoint.edu/the-glass-backbone-why-the-armys-logistics-will-break-in-the-next-war/
87•baud147258•2h ago•93 comments

A Possible Future for Damn Interesting

https://www.damninteresting.com/a-possible-future/
19•mzur•54m ago•0 comments

Opinionated and Easy Pi.dev Configuration

https://lazypi.org/
23•lwhsiao•59m ago•12 comments

Hy3

https://hy.tencent.com/research/hy3
29•andai•51m ago•13 comments

Show HN: LastShelf – an emergency map of your family's documents bills& contacts

https://www.lastshelf.ai/
22•sbrown12•1h ago•7 comments

What is Bending Spoons? The little-known AOL and Vimeo owner that's now public

https://techcrunch.com/2026/07/05/what-is-bending-spoons-everything-to-know-about-aols-acquirer/
18•jack1689•3d ago•11 comments

New open access book on history of computers and politics

https://mitpress.mit.edu/9780262053198/simpolitics/
18•mckelveyf•1h ago•0 comments

TrueBiz (YC S22) – Senior Software Engineer – Remote (US) – Full-Time

1•dannyhak•4h ago

Meta reuses old RAM in new servers with custom bridge chip

https://www.networkworld.com/article/4192827/meta-reuses-old-ram-in-new-servers-with-custom-bridg...
212•ihsw•5d ago•138 comments

Introducing Muse Spark 1.1

https://ai.meta.com/blog/introducing-muse-spark-meta-model-api/?_fb_noscript=1
148•ot•2h ago•98 comments

Coordination Without Consolidation: On Systems of States [pdf]

https://isonomiaquarterly.com/wp-content/uploads/2026/06/iq-4.2-summer-2026-macdonald-coordinatio...
7•brandonlc•1h ago•1 comments

Spider venom kills varroa mites without harming honeybees

https://connectsci.au/news/news-parent/9703/Spider-venom-kills-varroa-mites-without-harming
239•Jedd•11h ago•103 comments

US seeks cheaper hunter-killer drones after Iran destroys $1B worth of Reapers

https://arstechnica.com/gadgets/2026/07/us-seeks-cheaper-hunter-killer-drones-after-iran-destroys...
145•rbanffy•2h ago•173 comments

Show HN: Analog Watch

https://analog.watch
40•ezekg•1h ago•39 comments

Show HN: FableCut – A browser video editor AI agents can drive (zero deps)

https://github.com/ronak-create/FableCut
69•ronak_parmar•2h ago•44 comments

Maxwell's Equations Were Discovered [video]

https://www.youtube.com/watch?v=-hua8RWopfw
20•surprisetalk•2h ago•8 comments

Why we're moving off Cloudflare Durable Objects

https://usewire.io/engineering/why-were-moving-wire-off-cloudflare-durable-objects/
10•jitpal•1h ago•1 comments

How to Write an Email

https://blog.dannycastonguay.com/how-to-write-an-email/
8•speckx•52m ago•6 comments

John Deere owners will get the right to repair equipment under FTC settlement

https://apnews.com/article/john-deere-right-to-repair-agriculture-equipment-cb7514ffedb95c130a976...
1222•djoldman•16h ago•252 comments

A Road to Lisp: Why Lisp

https://scotto.me/blog/2026-07-09-why-lisp/
23•silcoon•3h ago•11 comments

How version control will evolve for the agent boom

https://entire.io/blog/how-version-control-will-evolve-for-the-agent-boom
36•tapanjk•3h ago•45 comments

Transparency efforts behind the Helium Browser

https://helium.computer/blog/transparency
20•twapi•2h ago•12 comments

Ways to think about token pricing

https://www.ben-evans.com/benedictevans/2026/7/9/ways-to-think-about-token-pricing
4•mercutio2•1h ago•0 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.