Hello, reroute

A small note about what belongs here, from packet paths to side projects.

View as Markdownmetanetworking

This is a notebook for the parts of computing that are easier to understand after writing them down: why a packet took the surprising path, what a Linux tool is actually showing, or which tiny decision made an app feel better.

It is also a place for the useful detours—workbench experiments, hobbies, and things that are simply fun.

What to expect

  • Networking and infrastructure notes grounded in real commands.
  • Linux behavior explained from observation rather than folklore.
  • App development write-ups, including the tradeoffs that did not fit in a commit message.
  • Occasional side quests with no attempt to make them sound serious.

Code should be readable, even when it is small:

ip route get 1.1.1.1

The HTML version is written for people. Every post also has a direct Markdown version for agents, terminal tools, and anyone who prefers the source.

Now live

This paragraph made the first trip through the production workflow. A push to main is checked, built, backed up, migrated, and deployed to Cloudflare automatically. If you are reading it on blog.reroute.cc, the whole path worked.

Comments

Read the rules

Loading comments…

    Replying to

    Limited Markdown is supported. New comments wait for review.