Re: Lightning broken in current daily!?

On 01.11.2013 12:15, Stefan Sitter wrote:
> On 01.11.2013 12:01, Peter Lairo wrote:
>> I have a Google Apps account, so - for my primary calendar - the part
>> after the @ is my domain. My other calendars have
>> "@group.calendar.google.com". Calendars that are shared with me by
>> others (who are also in my Google Apps domain) also have @Lairo.com.
>
> Maybe there is a difference between Google accounts and Google Apps
> accounts? The CalDAV API guide mentions that authentication must be done
> with a Google account:
> https://developers.google.com/google-apps/calendar/caldav/v2/guide#connecting_to_googles_caldav_server
>
>
Not sure about the difficulties with LG & Google Calendar.

Just checked with Reminderfox to add an event to a GCal with the "old" 
authorization method, and it works! This should be considered with the 
LG&GCal discussions as well!

Google said they will *only* support the OAuth2 method after Sept.2013 
but with this test it's clear Google supports *both* authorization 
methods as of today! This can be confirmed because Reminderfox has the 
ability to support both authorization methods [*].
So it can be expected an 'old' calendar setup will work with the 'old' 
login .. also today. I think that's what Peter saw.

Calendar ID and login (wrap-up)
GCalendars has these calendar identification scheme:
-- the main calendar:  [email protected]   [**]
-- a 'group': {some randomString}@group.calendar.google.com

The login with the different authorization differs like this:
'old':  https://www.google.com/calendar/dav/{some 
randomString}.calendar.google.com/events/

'new':  https://www.googleapis.com/caldav/v2/{some 
randomString}.calendar.google.com/events/

[*] Requires pre-version of release 2.1.4
[**] German account notation; other should be  @gmail.com