Michael Miller, author of TorWatch
Michael Miller writes every page on TorWatch. He is a cybersecurity practitioner, speaker and educator with more than ten years of experience across cybersecurity, networking, server administration and programming. His specialisms are security engineering and the Tor network. His profile at linkedin.com/in/michael-miller-721081446 is the one tied to this byline, and it is where to confirm his experience and the work he does outside the site. Who publishes TorWatch, and what it does and doesn't take money for, is on the about page.
Background
Each of those four disciplines shows up in how a tool gets read here. Networking is the frame for Tor: what each machine on the path can see, and what it can't. Running servers is the view from the other side of a privacy policy, where logs get written by default and someone has to decide what to keep. Programming means reading the code and specifications a project publishes, not only its homepage. Security engineering ties them together: design on the assumption that one part will fail, and know in advance what is exposed when it does.
Alongside practice, he speaks and teaches on cybersecurity, and he puts a large part of his time into attracting people into the field, developing them, and keeping good security people in it.
What he covers on TorWatch
The Tor pages draw most directly on his specialism: how the three relays divide what is known about you, which bridge to use when Tor is blocked, what actually identified Tor users in court cases, and how Tails and Whonix contain a compromise differently.
The same engineering questions run through the privacy tools picks and the crypto privacy section: who holds the data, what an audit actually covered, and what a provider can be forced to hand over. The news notes and the darknet takedowns timeline are built on court and police documents, with the document linked on each claim.