Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google: Do what you want with Reader, but don't kill CalDAV

zdnet.com

Post reply on HN
Print view View original

1–10 of 132 posts

Re: Google: Do what you want with Reader, but don't kill CalDAV

#3

Post by r0ll3rb0t »

nlawalker wrote: post #2

The MSFT change in position on supporting CalDAV (and the linked Win8 help page) is news to me. My Windows Phone 8 is still syncing with Gmail calendar. Does anyone know what's really going on here?

I wish I knew, but this seems to be getting out of hand today. What happened to Google supporting open standards?

Re: Google: Do what you want with Reader, but don't kill CalDAV

#4

Post by notatoad »

CalDAV is the spring cleaning killing that I'm most surprised about. It should have been obvious to everybody that reader was on track to be killed, but I would have thought that google would be eager to support any product that involves you telling them what your schedule is, whether that's through their calendar app or any other calendaring app you've got connected to their backend.

Re: Google: Do what you want with Reader, but don't kill CalDAV

#5

Post by spiralpolitik »

r0ll3rb0t wrote: post #3
nlawalker wrote: post #2

The MSFT change in position on supporting CalDAV (and the linked Win8 help page) is news to me. My Windows Phone 8 is still syncing with Gmail calendar. Does anyone know what's really going on here?

I wish I knew, but this seems to be getting out of hand today. What happened to Google supporting open standards?

Google only supports open standards when it is convenient for them to do so. Now its no longer convenient for them to support CalDav out goes the open standard.

I'm sure IMAP support in Gmail will be next on the chopping block.

Re: Google: Do what you want with Reader, but don't kill CalDAV

#6

Post by Finster »

spiralpolitik wrote: post #5
r0ll3rb0t wrote: post #3

Earlier quoted context omitted.

I wish I knew, but this seems to be getting out of hand today. What happened to Google supporting open standards?

Google only supports open standards when it is convenient for them to do so. Now its no longer convenient for them to support CalDav out goes the open standard. I'm sure IMAP support in Gmail will be next on the chopping block.

My initial reaction to this comment was: "But Google would NEVER drop IMAP support in gmail! That would be beyond ridiculous!"

I probably would've said the same thing about CalDAV last week.

Re: Google: Do what you want with Reader, but don't kill CalDAV

#7

Post by air »

nlawalker wrote: post #2

The MSFT change in position on supporting CalDAV (and the linked Win8 help page) is news to me. My Windows Phone 8 is still syncing with Gmail calendar. Does anyone know what's really going on here?

Google is still supporting ActiveSync: http://arstechnica.com/information-technology/2013/01/gmail-...

Re: Google: Do what you want with Reader, but don't kill CalDAV

#9

Post by bschlinker »

"Google's CalDAV page already lists the API as being "deprecated." A note on the page adds "If you think you have a compelling use case and would like to be whitelisted for the new version of CalDAV API, please fill out this form."

...

Google, however, confirmed this will not impact the agreement with Microsoft and that the Softies will still be able to implement CalDav support on Windows Phone."

http://www.zdnet.com/microsoft-in-the-clear-to-add-google-ca...

Re: Google: Do what you want with Reader, but don't kill CalDAV

#10

Post by cooldeal »

Is there any stated reason for deprecating CalDAV support? I hope the new Calendar API is open enough for platforms like Blackberry, Ubuntu Mobile, Jolla and Firefox OS etc to tap into.

It's increasingly looking like Google is making it hard for other platforms except it's own Android and iOS(can't ignore iOS because of the number of users) to interoperate with its services like Youtube, Gmail, Calendar etc.

Post reply on HN