frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Warcraft III Peon Voice Notifications for Claude Code

https://github.com/tonyyont/peon-ping
266•doppp•3h ago•105 comments

Discord/Twitch/Snapchat age verification bypass

https://age-verifier.kibty.town/
686•JustSkyfall•10h ago•277 comments

65 Lines of Markdown, a Claude Code Sensation

https://tildeweb.nl/~michiel/65-lines-of-markdown-a-claude-code-sensation.html
23•roywashere•1h ago•10 comments

Using an engineering notebook

https://ntietz.com/blog/using-an-engineering-notebook/
150•evakhoury•2d ago•44 comments

“Nothing” is the secret to structuring your work

https://www.vangemert.dev/blog/nothing
250•spmvg•3d ago•81 comments

D Programming Language

https://dlang.org/
98•arcadia_leak•3h ago•74 comments

GLM-5: Targeting complex systems engineering and long-horizon agentic tasks

https://z.ai/blog/glm-5
361•CuriouslyC•19h ago•443 comments

Fluorite – A console-grade game engine fully integrated with Flutter

https://fluorite.game/
465•bsimpson•16h ago•266 comments

Text classification with Python 3.14's ZSTD module

https://maxhalford.github.io/blog/text-classification-zstd/
190•alexmolas•3d ago•36 comments

Kanchipuram Saris and Thinking Machines

https://altermag.com/articles/kanchipuram-saris-and-thinking-machines
141•trojanalert•5d ago•27 comments

Ireland rolls out basic income scheme for artists

https://www.reuters.com/world/ireland-rolls-out-pioneering-basic-income-scheme-artists-2026-02-10/
270•abe94•16h ago•252 comments

How to make a living as an artist

https://essays.fnnch.com/make-a-living
84•gwintrob•5h ago•42 comments

NetNewsWire Turns 23

https://netnewswire.blog/2026/02/11/netnewswire-turns.html
282•robin_reala•14h ago•68 comments

Reports of Telnet's death have been greatly exaggerated

https://www.terracenetworks.com/blog/2026-02-11-telnet-routing
97•ericpauley•12h ago•41 comments

The other Markov's inequality

https://www.ethanepperly.com/index.php/2026/01/16/the-other-markovs-inequality/
28•tzury•4d ago•1 comments

HeyWhatsThat

https://www.heywhatsthat.com/faq.html
25•1970-01-01•2d ago•7 comments

WiFi could become an invisible mass surveillance system

https://scitechdaily.com/researchers-warn-wifi-could-become-an-invisible-mass-surveillance-system/
367•mgh2•5d ago•164 comments

Deobfuscation and Analysis of Ring-1.io

https://back.engineering/blog/04/02/2026/
36•raggi•3d ago•5 comments

Covering electricity price increases from our data centers

https://www.anthropic.com/news/covering-electricity-price-increases
91•ryanhn•11h ago•47 comments

From 34% to 96%: The Porting Initiative Delivers – Hologram v0.7.0

https://hologram.page/blog/porting-initiative-delivers-hologram-v0-7-0
38•bartblast•9h ago•6 comments

Claude Code is being dumbed down?

https://symmetrybreak.ing/blog/claude-code-is-being-dumbed-down/
902•WXLCKNO•14h ago•589 comments

Apple's latest attempt to launch the new Siri runs into snags

https://www.bloomberg.com/news/articles/2026-02-11/apple-s-ios-26-4-siri-update-runs-into-snags-i...
83•petethomas•12h ago•107 comments

GLM-OCR – A multimodal OCR model for complex document understanding

https://github.com/zai-org/GLM-OCR
262•ms7892•4d ago•72 comments

Officials Claim Drone Incursion Led to Shutdown of El Paso Airport

https://www.nytimes.com/2026/02/11/us/faa-el-paso-flight-restrictions.html
356•edward•23h ago•559 comments

Show HN: CodeRLM – Tree-sitter-backed code indexing for LLM agents

https://github.com/JaredStewart/coderlm/blob/main/server/REPL_to_API.md
52•jared_stewart•19h ago•17 comments

RISC-V Vector Primer

https://github.com/simplex-micro/riscv-vector-primer/blob/main/index.md
12•oxxoxoxooo•4d ago•2 comments

Microwave Oven Failure: Spontaneously turned on by its LED display (2024)

https://blog.stuffedcow.net/2024/06/microwave-failure-spontaneously-turns-on/
94•arm•13h ago•30 comments

Amazon Ring's lost dog ad sparks backlash amid fears of mass surveillance

https://www.theverge.com/tech/876866/ring-search-party-super-bowl-ad-online-backlash
556•jedberg•14h ago•299 comments

GPT-5 outperforms federal judges in legal reasoning experiment

https://papers.ssrn.com/sol3/papers.cfm?abstract_id=6155012
260•droidjj•9h ago•179 comments

Show HN: Agent Alcove – Claude, GPT, and Gemini debate across forums

https://agentalcove.ai
54•nickvec•12h ago•17 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.