If we're ever going to share calendars, we have to insist on interoperability between them all.
Let's drain the swamp!
Monday, August 24, 2009
Sync between iPhone calendar and Google Calendar
I'm not sure how I missed it before, but I've now successfully used CalDAV sync between my iPhone and my Google Calendar. However, when I add an event on the iPhone, I don't appear to have a way to direct the event to a particular calendar defined in my Google Calendar. I'm not sure if this is a limitation of CalDAV or not. Does anyone know?
Thursday, August 20, 2009
Yahoo! Calendar syncs with iPhone
New from Yahoo!: Sync your Yahoo! Calendar with the iPhone. No desktop Apple iCal required (never did figure out how to dispense with it in the case of Google Calendar). I've got to check this out, as soon as I can find the time.
Monday, August 17, 2009
FuseCal goes dark
Synchronizing calendars is a tough problem -- tougher than mere interoperability, tougher than simply publish-and-subscribe. Those who undertake to do it successfully probably deserve the highest number of SwampDrain points that this mere blog could possibly bestow.
Thus it is with a heavy heart that I must report the shuttering last month of FuseCal. During my busy summer, it escaped my notice. Obviously each calendar service must make its numbers to survive, and when one doesn't, it reflects upon the sorry state of the continuing lack of interoperability between calendars, the continuing complexity of calendar interoperability, and the lack of a clarion call from consumers for easy calendar interactions -- whether in the cloud, on desktops, or in our pockets.
The passage of FuseCal also takes with it into limbo the assets of iFreeBusy, which set out to solve a simpler problem: that of providing an easy place to post one's free and busy information.
Now it falls back upon CalConnect to continue to hammer out calendar interoperability standards which can become the basis for more progress and innovation in this area.
Thus it is with a heavy heart that I must report the shuttering last month of FuseCal. During my busy summer, it escaped my notice. Obviously each calendar service must make its numbers to survive, and when one doesn't, it reflects upon the sorry state of the continuing lack of interoperability between calendars, the continuing complexity of calendar interoperability, and the lack of a clarion call from consumers for easy calendar interactions -- whether in the cloud, on desktops, or in our pockets.
The passage of FuseCal also takes with it into limbo the assets of iFreeBusy, which set out to solve a simpler problem: that of providing an easy place to post one's free and busy information.
Now it falls back upon CalConnect to continue to hammer out calendar interoperability standards which can become the basis for more progress and innovation in this area.