{
  "version": "https://jsonfeed.org/version/1",
  "title": "blogging on birdwatching",
  "icon": "https://avatars.micro.blog/avatars/2026/31/1322340.jpg",
  "home_page_url": "https://b10g.xyz/",
  "feed_url": "https://b10g.xyz/feed.json",
  "items": [
      {
        "id": "http://codybrom.micro.blog/2026/08/09/why-i-moved-to-microblog/",
        "title": "Why I moved to Micro.blog",
        "content_html": "<p>Last week I was talking to my friend <a href=\"https://b10g.xyz/2026/08/08/the-death-of-compromise/\">Josh</a> about blogging and our conversation was self-inspiring enough that I decided to set up <a href=\"https://b10g.xyz/2026/08/05/aha-this-office-supplies-purchase/\"><em>another</em> blog</a>.</p>\n<p>Well, now my new blog is my old blog too. For the past few years, I&rsquo;d been occasionally posting at <strong>b10g.xyz</strong> using a multiple blog platforms hosted on various cloud services over a span of four years. The version I retired last week was hosted on <a href=\"https://pages.cloudflare.com/\">Cloudflare Pages</a> with a site statically generated using <a href=\"https://lume.land/\">Lume</a> from <a href=\"https://daringfireball.net/projects/markdown/\">Markdown</a> files I kept in a private GitHub repo. Over the blog&rsquo;s life, I&rsquo;d also used <a href=\"https://astro.build/\">Astro</a> and Next.js on Vercel, hosted the current version for a bit on <a href=\"https://deno.com/deploy\">Deno Deploy</a>, and briefly experimented with <a href=\"https://emdashcms.com/\">Emdash</a>. This final version was what worked the best for me. Moving isn&rsquo;t an indictment of Lume, Cloudflare, or even using Markdown in Git as a CMS. All of those things are great, <a href=\"https://www.youtube.com/watch?v=lc0Nc2VkfIk&amp;t=1447s\">except maybe the last one</a>, and I still recommend them wholeheartedly. Just not for me.</p>\n<p>I originally wasn&rsquo;t planning to migrate, because that felt like &ldquo;fixing&rdquo; something that wasn&rsquo;t exactly broken. But something <em>was</em> broken. Even though I&rsquo;d published more blog posts in the last year than I had in a while, I&rsquo;d come to realize that my self-managed setup lacked restraint. Any feature or tweak I wanted to add, I could. And with the help of AI agents, I often did. What I ended up with was more than enough to validate my desire to write, but I wasn&rsquo;t publishing all the things I wanted to write because managing what I&rsquo;d built took more of the time. I still have drafts in my Notes.app that never saw the light of day because <em>actually</em> publishing involved sitting down at the right machine and doing a few manual steps that I couldn&rsquo;t easily do on mobile.</p>\n<p>I&rsquo;ve learned too late in my writing journey that wrangling your workflow <del>can</del> <strong>will</strong> drain your capacity for writing and creating if you let it. I really enjoy building platforms. It&rsquo;s my day job. But I want writing to be joy, not more work. Micro.blog as a platform is exactly what I want. It&rsquo;s available anywhere, it helps me syndicate to my various social accounts, it has no ads or built-in analytics, but most importantly&hellip; it has constraints I can&rsquo;t change. I&rsquo;m so excited I signed up for an annual subscription.</p>\n<p>Building was fun, but I think writing will be even more fun.</p>\n<div class=\"replies-data\" hidden aria-hidden=\"true\" data-threads=\"https://www.threads.com/@codybrom/post/Db04ZdcILj5\" data-threads-id=\"18348492244222198\"></div><a class=\"u-syndication\" rel=\"syndication\" href=\"https://www.threads.com/@codybrom/post/Db04ZdcILj5\" hidden aria-hidden=\"true\"></a>\n",
        "date_published": "2026-08-09T10:00:00-05:00",
        "url": "https://b10g.xyz/2026/08/09/why-i-moved-to-microblog/",
        "tags": ["writing","blogging"]
      }
  ]
}
