<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ical on </title>
    <link>/tags/ical/</link>
    <description>Recent content in ical on </description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Sun, 01 Mar 2026 00:00:00 +0800</lastBuildDate><atom:link href="/tags/ical/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Timeslot: A Self-Hosted Calendar Availability Feed for a Static Blog</title>
      <link>/posts/timeslot-calendar-visibility-system/</link>
      <pubDate>Sun, 01 Mar 2026 00:00:00 +0800</pubDate>
      
      <guid>/posts/timeslot-calendar-visibility-system/</guid>
      <description>I wanted to show my availability on this blog — basically a simple &amp;ldquo;here&amp;rsquo;s when I&amp;rsquo;m free&amp;rdquo; widget. Most of the options I looked at either pushed me toward a third-party scheduling service (Calendly, Cal.com cloud) or required setting up OAuth credentials. Neither felt like a great fit for a static blog that only needed a read-only JSON feed.
So I built Timeslot — a small self-hosted service that exposes availability as a simple API while keeping the underlying calendar data on infrastructure I control.</description>
    </item>
    
  </channel>
</rss>
