GitP/A/Log/26/09/26 Sat - RSS Project

• 2026-09-26 Sat

  • My Notes

    • 09:58
      • I'd like to finally get some external hosting going for Person/codekiln/GitHub/gitpa.
      • I have a Backblaze account that I set up a while back, and I'd like to get a CDN going off of that for the episodes and other assets that are referenced in the published.
      • I'm considering experimenting with something like dvc as a possible replacement for git/lfs for managing assets like Microfreak/UG/04 Presets, smaller audio fragments, images, etc. Basically, podcast rich media.
        • In the end, I decided to not add dvc at this time, as it will get in the way of getting a publishing pipeline going.
      • I started a voice chat with OpenAI/Model/GPT/6/Sol and described what I wanted.
    • 14:02
      • GitP/A/Log/26/09/26 Sat - RSS Project/Q/What Backblaze Options would work with Logseq?

  • Plan

    • Publish GitP/A/Session/26/09/25-Fri as the first RSS episode.
      • TODO Give the uploaded MP3 a stable Cloudflare media URL and verify HEAD and byte-range requests.
      • Create the public episode from Music/Composition/Log/26/09/25 Fri, with its recording and RSS release identity.
      • Generate RSS, publish it on GitHub Pages, and validate its self-link, artwork, and enclosure.
      • TODO Subscribe to the feed by URL and check playback in a podcast app.
    • TODO Add staged-file secret and identity scanning and a CI scan to Gitpa before publishing the feed.
    • TODO Rename the shared Backblaze rclone remote · dotfiles issue #131, then update the garden upload task's default remote.
    • Define Logseq/Entity/Asset and Logseq/Entity/Asset/B2 for garden media and page-derived upload filenames.
    • TODO Automate bringing selected garden notes into public episode pages after the first manual publication works.
    • Set up the shared Backblaze rclone remote and 1Password publishing access · dotfiles issue #125
    • Prepare and upload Gitpa media from the garden · garden issue #126; GitP.26.09.25.mp3 passed public URL, length, and range checks.

  • Design questions

    • For issue #131, should the rclone/remote name describe the reusable Backblaze B2 connection shared by garden projects (for example, garden-b2:), or the existing bucket or publishing workflow? In remote:bucket/path, the remote name is the part before :. What name and scope do you want?