Skip to content

About Nexus

A research workflow tool that escaped recursive procrastination.

Nexus KB grew out of a very specific frustration: the Linux kernel archive contains essential technical history, but reconstructing a discussion from raw archive pages is slower than it should be.

We wanted an interface that treats threads and patch revisions as working context instead of generic web documents. That goal shaped both the product and the site you are reading now.

Who We Are

Built by two researchers who spend a lot of time reading kernel mail.

PhD student, CS @ Virginia Tech

Tanuj Ravi Rao

Tanuj is an engineer turned systems researcher working on accelerating dataplanes through kernel extensions. To procrastinate on his research, he implements extremely unnecessary performance enhancements on his homelab. When not working on the homelab, he is building side projects which rarely ever see the light of day. This project seems to be the first to escape.

Visit homepage

MS student, CS @ Virginia Tech

Egor Lukiyanov

Egor works on everything from overcomplicated 3D photobook renderers to eBPF extensions. He frequently finds himself working on a side project to procrastinate on another side project, which was in turn started to procrastinate on research. This latest side project, however, might be a combination of both and thus has escaped the endless tunnel of recursive procrastination.

Visit homepage

How Nexus Began

We wanted the archive to feel closer to the way kernel work actually unfolds.

Problem

Digging through the Linux kernel mailing list is essential, but raw archive pages fragment the experience. Threads sprawl, patch revisions drift apart, and a lot of context lives one click too far away.

Approach

Nexus KB reframes that material as an exploratory workspace for reading discussions, following lineage, and comparing revisions without constantly rebuilding context from scratch.

Why It Matters

That makes the product useful not just for finding a message, but for understanding how technical discussion turns into code and how code changes over time.