These last few weeks I've been revisiting and relaunching a couple of my older calendar projects. Both predate the Heroku free service purge in 2022, but had some bugs at that point so I'd mostly let them die and needing a bit of work to get them back up and running.
About 4 years back, I wrote a tool called Sked which would take your calendars (mostly Google calendars as a core, but also other iCalendar-compatible calendars) and then let you build merged calendars to share with others. It meant you could give someone a single URL for "your calendar" that would stay static even if the actual reality of your calendar was really a merge of 5-6 different ones that changed over time.
The biggest item for this was getting Google to vaguely trust me. You can use Google OAuth pretty easily, but not getting a "evil people are stealing your data" page as part of the login takes a bit more work. Namely a lot of corporate-style policies including writing my rather snarky privacy policy. The actual real privacy policy should read "here's the AGPLed source code, if you don't trust me or this code, don't use it", but apparently they want a bit more than that which is now resolved and Sked is live again
There's also the Eventbrite Calendar exporter which lets you get an iCalendar feed of your Eventbrite events. One of it's really nice features is that as far as I can tell the Eventbrite auth tokens don't seem to expire ever, and so we can just actually use the token itself as part of the Calendar URL and not store any state at all :) Again, this needed a few upgrades (because Python 3.6 has been EoL for 3 years now!) but nothing too terrible.
Comments
With an account on the Fediverse or Mastodon, you can respond to this post. Since Mastodon is decentralized, you can use your existing account hosted by another Mastodon server or compatible platform if you don't have an account on this one. Known non-private replies are displayed below.