I am not a big fan of cloud technology; I am quite sure that, at some point in the future, the rush to dump information in the hands of offsite corporate hosts is going to backfire. (If it hasn’t already.)
On the other hand, my current job relies a lot on Google Calendar, to synchronize schedules between staff members.
So I use it, but do my best to insulate my personal life from the stuff on the web. Call me paranoid; I don’t mind.
gcalcli is one way to interact with the calendar service, and it’s not as cumbersome as it might appear at first.
Most of the features and protocol for gcalcli are easy to figure out, from the help page. My only suggestion is to use gpg to store your password locally, and set up the gcalcli configuration file to decrypt it on access.
The -help flag gives a little information about that, in short:
- type your password into a text file,
- encrypt it with
gpg -c passwd.txt,
- adjust your .gcalclirc file to
[gcalcli] user: kmandla pw: `gpg --decrypt passwd.txt.gpg`
In my case, because I run without X, I had to add this to .gnupg/gpg-agent.conf:
--use-agent to the gpg commands, both before and in .gcalclirc.
I’ll say after all, that while this is useful, I still prefer to simply export the calendar through Google’s interface, and convert them with ical2rem.py. Remember that one? 😉