<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Tether — Notes on staying in touch</title>
    <link>https://tetherup.app/blog</link>
    <description>Occasional writing about relationships, the quiet ways we lose track of people, and what we are building.</description>
    <language>en-us</language>
    <item>
      <title>Contact information should belong to the person it is about</title>
      <link>https://tetherup.app/blog/contact-information-should-belong-to-the-person</link>
      <guid isPermaLink="true">https://tetherup.app/blog/contact-information-should-belong-to-the-person</guid>
      <description>Every address book ever built assumes your number is a thing other people own copies of. That assumption is the bug.</description>
      <pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What we learned building a permission system for phone numbers</title>
      <link>https://tetherup.app/blog/permission-system-for-phone-numbers</link>
      <guid isPermaLink="true">https://tetherup.app/blog/permission-system-for-phone-numbers</guid>
      <description>Circles, the floor everyone gets, and why revocation has to actually revoke — three decisions that turned out to be load-bearing.</description>
      <pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Why your address book goes wrong</title>
      <link>https://tetherup.app/blog/why-your-address-book-goes-wrong</link>
      <guid isPermaLink="true">https://tetherup.app/blog/why-your-address-book-goes-wrong</guid>
      <description>A copy starts decaying the moment you make it. That is not a discipline problem — it is a design problem, and it has been in every address book ever built.</description>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
