<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Project on BitSpeed.org</title>
    <link>https://bitspeed.org/tags/project/</link>
    <description>Recent content in Project on BitSpeed.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 20 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bitspeed.org/tags/project/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why the Project Is Called BitSpeed</title>
      <link>https://bitspeed.org/why-the-project-is-called-bitspeed/</link>
      <pubDate>Tue, 20 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bitspeed.org/why-the-project-is-called-bitspeed/</guid>
      <description>&lt;p&gt;BitSpeed is a useful name only if it leads to a clear job. For Inspect, that job is explaining where observed transfer time goes. The name should get you to a measurement you can examine, rather than a promise that every request will become faster.&lt;/p&gt;&#xA;&lt;p&gt;That is also why the project contains separate tools. Understanding a request and moving a file safely are related problems, but they have different correctness tests. Inspect needs to keep timing evidence and interpretation apart. Transfer needs to prove which bytes survived interruption and when a complete destination can be reported.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
