<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Watchkeeper on watchkeeper.net</title>
    <link>https://watchkeeper.net/tags/watchkeeper/</link>
    <description>Recent content in Watchkeeper on watchkeeper.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 23 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://watchkeeper.net/tags/watchkeeper/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Watchkeeper Was Tested Against a Page Built to Fool It</title>
      <link>https://watchkeeper.net/how-watchkeeper-was-tested-against-a-page-built-to-fool-it/</link>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://watchkeeper.net/how-watchkeeper-was-tested-against-a-page-built-to-fool-it/</guid>
      <description>&lt;p&gt;A tool that says &amp;ldquo;this page contacted five sites&amp;rdquo; is only worth something if the page really contacted five sites. Watchkeeper&amp;rsquo;s main promise is that nothing a page does gets missed, and that the page can&amp;rsquo;t hide from it or tamper with it. So the tests don&amp;rsquo;t ask Watchkeeper what it saw and trust the answer. They ask the servers.&lt;/p&gt;&#xA;&lt;p&gt;The self-test runs the real app, on the system&amp;rsquo;s own web engine, against two small web servers started on the same machine. One plays the site at 127.0.0.1. The other plays a tracker at localhost, which counts as a different site. Both write down every request they receive, and those logs are the ground truth: whatever reached a server must be in Watchkeeper&amp;rsquo;s report.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Watchkeeper Is a Tiny Free Browser That Shows You Who Is Watching</title>
      <link>https://watchkeeper.net/watchkeeper-is-a-tiny-free-browser-that-shows-you-who-is-watching/</link>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://watchkeeper.net/watchkeeper-is-a-tiny-free-browser-that-shows-you-who-is-watching/</guid>
      <description>&lt;p&gt;Open a news article and you see a headline, some text and an ad or two. You don&amp;rsquo;t see the other companies the page told about your visit while it loaded. On many news sites that list runs to a dozen names or more, and nothing in a normal browser window mentions any of them.&lt;/p&gt;&#xA;&lt;p&gt;Watchkeeper is a small browser built to show that list. You type an address and use the page as you would anywhere else. A panel on the right fills in as the page works: the other sites it contacts, the cookies it leaves, the keys it writes to your computer and the scripts that read your device&amp;rsquo;s fingerprint.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Why a Browser That Watches Trackers Is Called Watchkeeper</title>
      <link>https://watchkeeper.net/why-a-browser-that-watches-trackers-is-called-watchkeeper/</link>
      <pubDate>Fri, 23 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://watchkeeper.net/why-a-browser-that-watches-trackers-is-called-watchkeeper/</guid>
      <description>&lt;p&gt;On a ship, someone is always on watch. While the rest of the crew sleeps, eats or works below, one officer stays on the bridge, keeps a lookout and notes what passes. That person is the watchkeeper, and watchkeeping is still the word sailors use for the job.&lt;/p&gt;&#xA;&lt;p&gt;The day is cut into watches of about four hours, so nobody has to stay alert for too long. Whoever has the watch looks out for other ships, lights and changes in the weather, and writes what they see in the log. The captain doesn&amp;rsquo;t have to stand there all night. The log says what happened.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
