From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: Google calendar sync - what is recommended? Date: Tue, 09 Apr 2013 20:23:20 +0200 Message-ID: <87k3obk1gn.fsf@pank.iue.private> References: <87y5crrb72.fsf@krugs.de> <87k3obznhv.fsf@ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:55018) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UPdCk-0001Aj-OR for emacs-orgmode@gnu.org; Tue, 09 Apr 2013 14:23:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UPdCg-0003Dt-7N for emacs-orgmode@gnu.org; Tue, 09 Apr 2013 14:23:38 -0400 Received: from plane.gmane.org ([80.91.229.3]:38570) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UPdCg-0003Dc-0v for emacs-orgmode@gnu.org; Tue, 09 Apr 2013 14:23:34 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UPdCb-000674-Cc for emacs-orgmode@gnu.org; Tue, 09 Apr 2013 20:23:29 +0200 Received: from ip-pool-139.iue.it ([192.167.90.139]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 09 Apr 2013 20:23:29 +0200 Received: from rasmus by ip-pool-139.iue.it with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 09 Apr 2013 20:23:29 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Eric S Fraga writes: > We are in a state of flux. For quite a while, I used a two way > upload/download approach based on icalendar export from org to Google > and an awk script to convert Google calendar information into org. See > > http://orgmode.org/worg/org-tutorials/org-google-sync.html > > This is not a synchronisation approach. > > However, more recently, I moved to org-caldav for syncing. There is a > link to this package from that web page as well (at the end). This > works really nicely. > > The problem is that Google has decided to no longer allow caldav access > to their Calendar system from sometime later this year, requiring people > to access the data in the calendar via the REST API. I'm not sure Google is the solution. . . Since we discussed this last I have found a couple of nice calDAV possibilities: - Red Hat Open Shift FreeShifter: it can be used for e.g. OwnCloud or some other CalDav calendar (it can install OwnCloud itself). I use it for Tiny Tiny Rss and OwnCloud. https://www.openshift.com/quickstarts/all?order=created&sort=desc - owndrive.com also offers free OwnCloud hosting. https://owndrive.com/ If I have time at some point I'll experiment with it, but so far I have still be unable to make org-caldav work. . . –Rasmus -- Vote for proprietary math!