<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>meta &amp;mdash; Jack Baty</title>
    <link>https://write.as/jackbaty/tag:meta</link>
    <description>Director of Unspecified Services</description>
    <pubDate>Tue, 25 Aug 2026 14:30:32 +0000</pubDate>
    <image>
      <url>https://i.snap.as/Bl9oLcuC.jpg</url>
      <title>meta &amp;mdash; Jack Baty</title>
      <link>https://write.as/jackbaty/tag:meta</link>
    </image>
    <item>
      <title>Domain Consolidation</title>
      <link>https://write.as/jackbaty/domain-consolidation?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[I&#39;ve been feeling a need to simplify things and I&#39;ve decided that one of those things is domain names. My days of hoarding domain names, just because, are drawing to a close. I don&#39;t want the hassle of managing zones and I don&#39;t need the fees.&#xA;&#xA;To that end, I&#39;m working toward moving everything to subdomains of baty.net. &#xA;&#xA;!--more--&#xA;&#xA;I&#39;ve already moved my wiki from rudimentarylathe.wiki to rl.baty.net. I considered wiki.baty.net and may still use that instead.&#xA;&#xA;Next up is baty.blog. Not sure if I&#39;ll use blog.baty.net for that or not, yet.&#xA;&#xA;There are several others to move, and I&#39;ll be sure to leave permanent redirects up and running at least until the domains expire. That should give Google time to catch up. &#xA;&#xA;The domains I&#39;m not sure about are the hosted services. This Write.as blog, for example. Currently, I&#39;m thinking I&#39;ll leave them where they are, without custom domains. That makes things simpler. I lose the opportunity to &#34;own&#34; the URLs but, as we all know, I&#39;m prone to breaking links. Not my greatest feature, but it&#39;s proven true.&#xA;&#xA;The idea is to have as few moving parts and dependencies as is reasonable.&#xA;&#xA;Meta&#xA;&#xA;a href=&#34;https://remark.as/p/jackbaty/domain-consolidation&#34;Discuss.../a]]&gt;</description>
      <content:encoded><![CDATA[<p>I&#39;ve been feeling a need to simplify things and I&#39;ve decided that one of those things is domain names. My days of hoarding domain names, just because, are drawing to a close. I don&#39;t want the hassle of managing zones and I don&#39;t need the fees.</p>

<p>To that end, I&#39;m working toward moving everything to subdomains of <a href="https://baty.net">baty.net</a>.</p>



<p>I&#39;ve already moved my wiki from rudimentarylathe.wiki to <a href="https://rl.baty.net">rl.baty.net</a>. I considered wiki.baty.net and may still use that instead.</p>

<p>Next up is <a href="https://baty.blog">baty.blog</a>. Not sure if I&#39;ll use blog.baty.net for that or not, yet.</p>

<p>There are several others to move, and I&#39;ll be sure to leave permanent redirects up and running at least until the domains expire. That should give Google time to catch up.</p>

<p>The domains I&#39;m not sure about are the hosted services. This Write.as blog, for example. Currently, I&#39;m thinking I&#39;ll leave them where they are, without custom domains. That makes things simpler. I lose the opportunity to “own” the URLs but, as we all know, I&#39;m prone to breaking links. Not my greatest feature, but it&#39;s proven true.</p>

<p>The idea is to have as few moving parts and dependencies as is reasonable.</p>

<p><a href="https://write.as/jackbaty/tag:Meta" class="hashtag"><span>#</span><span class="p-category">Meta</span></a></p>

<p><a href="https://remark.as/p/jackbaty/domain-consolidation">Discuss...</a></p>
]]></content:encoded>
      <guid>https://write.as/jackbaty/domain-consolidation</guid>
      <pubDate>Tue, 22 Feb 2022 10:16:36 +0000</pubDate>
    </item>
  </channel>
</rss>