frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

AirSnitch: Demystifying and breaking client isolation in Wi-Fi networks [pdf]

https://www.ndss-symposium.org/wp-content/uploads/2026-f1282-paper.pdf
217•DamnInteresting•3h ago•110 comments

I baked a pie every day for a year and it changed my life

https://www.theguardian.com/lifeandstyle/2026/feb/22/a-new-start-after-60-i-baked-a-pie-every-day...
72•NaOH•2d ago•39 comments

Palm OS User Interface Guidelines (2003) [pdf]

https://cs.uml.edu/~fredm/courses/91.308-spr05/files/palmdocs/uiguidelines.pdf
73•spiffytech•2h ago•29 comments

Will vibe coding end like the maker movement?

https://read.technically.dev/p/vibe-coding-and-the-maker-movement
106•itunpredictable•3h ago•119 comments

Launch HN: Cardboard (YC W26) – Agentic video editor

https://www.usecardboard.com/
15•sxmawl•1h ago•3 comments

Show HN: Rev-dep – 20x faster knip.dev alternative build in Go

https://github.com/jayu/rev-dep
13•jayu_dev•53m ago•3 comments

Nano Banana 2: Google's latest AI image generation model

https://blog.google/innovation-and-ai/technology/ai/nano-banana-2/
341•davidbarker•3h ago•325 comments

Show HN: Deff – side-by-side Git diff review in your terminal

https://github.com/flamestro/deff
25•flamestro•1h ago•10 comments

Google Street View in 2026

https://tech.marksblogg.com/google-street-view-coverage.html
77•marklit•2h ago•56 comments

Show HN: Hacker Smacker – spot great (and terrible) HN commenters at a glance

https://hackersmacker.org
38•conesus•2d ago•24 comments

Bild AI (YC W25) Is Hiring Interns to Make Housing Affordable

https://www.workatastartup.com/jobs/80596
1•rooppal•2h ago

Google API keys weren't secrets, but then Gemini changed the rules

https://trufflesecurity.com/blog/google-api-keys-werent-secrets-but-then-gemini-changed-the-rules
1113•hiisthisthingon•23h ago•265 comments

BuildKit: Docker's Hidden Gem That Can Build Almost Anything

https://tuananh.net/2026/02/25/buildkit-docker-hidden-gem/
95•jasonpeacock•5h ago•27 comments

Show HN: Beehive – Multi-Workspace Agent Orchestrator

https://storozhenko98.github.io/beehive/
20•mst98•2d ago•10 comments

Show HN: Terminal Phone – E2EE Walkie Talkie from the Command Line

https://gitlab.com/here_forawhile/terminalphone
245•smalltorch•9h ago•59 comments

Show HN: Linex – A daily challenge: placing pieces on a board that fights back

https://www.playlinex.com/
17•Humanista75•1d ago•9 comments

The Wolfram S Combinator Challenge

https://www.combinatorprize.org/
19•paraschopra•3d ago•0 comments

Steering interpretable language models with concept algebra

https://www.guidelabs.ai/post/steerling-steering-8b/
22•luulinh90s•19h ago•1 comments

iPhone and iPad approved to handle classified NATO information

https://www.apple.com/newsroom/2026/02/iphone-and-ipad-approved-to-handle-classified-nato-informa...
49•throwfaraway4•1h ago•24 comments

just-bash: Bash for Agents

https://github.com/vercel-labs/just-bash
78•tosh•6h ago•43 comments

Show HN: Mission Control – Open-source task management for AI agents

https://github.com/MeisnerDan/mission-control
13•meisnerd•6h ago•2 comments

OsmAnd's Faster Offline Navigation

https://osmand.net/blog/fast-routing/
8•todsacerdoti•1h ago•4 comments

What Claude Code Chooses

https://amplifying.ai/research/claude-code-picks
11•tin7in•1h ago•1 comments

He saw an abandoned trailer. Then, uncovered a surveillance network

https://calmatters.org/justice/2026/02/alpr-border-patrol-caltrans/
40•Element_•1h ago•14 comments

Open Source Endowment – new funding source for open source maintainers

https://endowment.dev/
133•kvinogradov•3h ago•93 comments

Tell HN: YC companies scrape GitHub activity, send spam emails to users

486•miki123211•10h ago•171 comments

Jimi Hendrix was a systems engineer

https://spectrum.ieee.org/jimi-hendrix-systems-engineer
626•tintinnabula•23h ago•216 comments

Banned in California

https://www.bannedincalifornia.org/
443•pie_flavor•20h ago•519 comments

This time is different

https://shkspr.mobi/blog/2026/02/this-time-is-different/
42•speckx•6h ago•44 comments

How will OpenAI compete?

https://www.ben-evans.com/benedictevans/2026/2/19/how-will-openai-compete-nkg2x
429•iamskeole•21h ago•593 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•9mo 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.