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

11–20 of 132 posts

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

#15

Post by guelo »

cooldeal wrote: post #10

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.

They're going down the Facebook route, they want to lock you into their AOL-style walled garden. I was surprised the other day when I went to share a video from Google+ to Facebook, turns out I couldn't, it wasn't a youtube video as I had expected.

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

#16

Post by pkfrank »

guelo wrote: post #12

I'm getting really nervous about relying so much on Google. I'll be working on transitioning off of them from here on out for all my projects and recommendations. I just learned about the Leaflet map library for example.

I recently caught myself thinking: "How much would someone have to pay me to never use another Google product?" While contemplating my use of gMail, Search, Calendar, YouTube, etc., I wrapped my head around how powerful and irreplaceable Google and its products are to me. Now that they're winding down Reader, I'm reminded at how vulnerable we all are given this reliance.

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

#17

Post by anonymfus »

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.

POP3 is used for migration from Gmail by major competitors, I am sure that Google will drop it before IMAP.

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

#18

Post by 3825 »

wooster wrote: post #8

Can anyone recommend a good email/calendar host for custom domains? Edit: I have several Google Apps for Business domains. I'm looking for alternatives.

Exchange server is $10 per month at Rackspace [1] I've heard good things about Microsoft Office 365 as well. Then, there's always Google Apps for Business...

[1] https://www.rackspace.com/apps/email_hosting/exchange_hostin...

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

#19

Post by Selfcommit »

notatoad wrote: post #4

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.

If you throw out all the 'tit-for-tat' assumptions, it really makes sense. Google has an API for nearly everything. I could easily see this as a standardization approach.

Personally, I'm not effected at all between using the Google calendar website and my android based phone. I think Google's goal is to push everyone to use the API for their calander in future apps. I don't mind doing that for what they provide.

I could easily imagine that use of their API could allow for better data gathering than using the open standard.

Post reply on HN