whatgaul

Original author of https://github.com/trotto/go-links here! We spoke with Benjamin directly, so I trust his recollection.

We sure can relate! Setting up the sync logic and coming up with a reasonable first-cut database schema was considerably more complicated than we'd anticipated.

What was your motivation for working on something like this? That would be hugely helpful for us to understand!

We also just decided to go ahead and open-source it: https://github.com/belvinlabs/proost-app. (Very rough; hit us up for help if you'd like to get involved.)

Yeah, we've been thinking of open-sourcing it. We decided to go ahead and do it: https://github.com/belvinlabs/proost-app

We'd love to hear how you'd like to use it, whether in the comments here or through Issues in that repo. That's hugely helpful to us right now!

Right, naturally none of the rocket launches in the demo data set are recurring (perhaps one day...). In another calendar with recurring events, that ID will be a consistent string across all events that are part of the same series. It's pulled from the `recurringEventId` field in the Google Calendar API: https://developers.google.com/calendar/v3/reference/events#r...

At the moment, the tool just syncs events from one month in the past through one month in the future, so it will pick up a finite subset of a potentially infinite series of recurring events. In future iterations, we imagine users defining their own timeframe to sync.

This project grew out of our interest in understanding and optimizing time spent in meetings, but don't let that stop you from using it some other way. We're providing direct access to a MySQL database specifically so you can slice the data however you like, with any tool you please.

Questions? Feedback? All very very welcome!