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.
Even if the Calendar API were open to all platforms, it's not a standard, it's just an API unilaterally defined by Google. CalDAV, however, is a standard " rel="nofollow">https://tools.ietf.org/html/rfc4791> . It is certainly an evil move from Google to try to replace an existing open standard with an API defined exclusively by them (unless they have technical grounds to do so, and considerate and documented extensio…
Google: Do what you want with Reader, but don't kill CalDAV
41–50 of 132 posts
Re: Google: Do what you want with Reader, but don't kill CalDAV
#42Earlier quoted context omitted.
Just like PG said in one of his essays, Google is now the new Microsoft. It used to be about giving hackers tools to build on top of their services. Now, its all about turning the search engine into a social network. And before the Google army comes in, let me say one thing. I used to love Google. Used all of their services. Built stuff with their services. Each computer I touched got Chrome installed. I was a fan bo…
As someone often accused of being a Google "fanboi"... I agree. I'm not going to abandon Go or Chrome or anything because they are fully OSS so if Google drops them it isn't the end of the world, but I wouldn't dream of building a service (even a free for-fun one) on top of some Google Web API these days. Maybe that's fine with them (seems like they have a corporate mission to eliminate the whole idea of free or near…
You can't built bridges on top of shaky ground.
Re: Google: Do what you want with Reader, but don't kill CalDAV
#43"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…
It does appear that they have confirmed not supporting CalDAV on Windows 8, RT, or Outlook. And since Google is phasing out support for ActiveSync come 7/31/2013, the only way to sync with Google calendars and contacts is from Outlook 2010 and earlier, and only if you are a paid apps user. (using ActiveSync)
Re: Google: Do what you want with Reader, but don't kill CalDAV
#44I'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.
Wouldn't you just be reliant another another company? What's to guarantee that they won't close down the service one day?
* Search - replace with duck duck go * Chrome - Firefox, most likely, but there are tons of browser options these days. * Voice - this is the one that really has me hooked into the service. Not sure what I'd use instead, if not just a regular phone number. * reader - now built into owncloud, dozens of reader replacements popping up. * youtube - probably won't replace. I usually don't log in any way. Uploads that I do occasionally post will go to vimeo. * gmail - aside from the hassle of switching, rolling an email server isn't too hard. downtime is a concern, but I could mitigate this by hosting it in the cloud somewhere, or even doing a colo backup at a friend's house. Paying for email is an option, I suppose, which could have benefits.
Other than that, I'm not sure. These moves by Google recently just seem skeevy to me. I think it started with the G+ stuff, but since then my trust in Google is waning, so this is a thing I think about somewhat regularly now.
Re: Google: Do what you want with Reader, but don't kill CalDAV
#45Earlier quoted context omitted.
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.
Just like PG said in one of his essays, Google is now the new Microsoft. It used to be about giving hackers tools to build on top of their services. Now, its all about turning the search engine into a social network. And before the Google army comes in, let me say one thing. I used to love Google. Used all of their services. Built stuff with their services. Each computer I touched got Chrome installed. I was a fan bo…
With the death of Reader, my last shred of goodwill is basically gone. I've used an @gmail.com address for the past six years despite having my own domain, and now that's going to stop as I gradually transition off most of their services.
Re: Google: Do what you want with Reader, but don't kill CalDAV
#46Can 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
#47Earlier quoted context omitted.
Just like PG said in one of his essays, Google is now the new Microsoft. It used to be about giving hackers tools to build on top of their services. Now, its all about turning the search engine into a social network. And before the Google army comes in, let me say one thing. I used to love Google. Used all of their services. Built stuff with their services. Each computer I touched got Chrome installed. I was a fan bo…
As someone often accused of being a Google "fanboi"... I agree. I'm not going to abandon Go or Chrome or anything because they are fully OSS so if Google drops them it isn't the end of the world, but I wouldn't dream of building a service (even a free for-fun one) on top of some Google Web API these days. Maybe that's fine with them (seems like they have a corporate mission to eliminate the whole idea of free or near…
Re: Google: Do what you want with Reader, but don't kill CalDAV
#48Earlier quoted context omitted.
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.
Was that Google+'s fault for not giving an easily-embeddable link or Facebook's fault for refusing to show the goods?
Re: Google: Do what you want with Reader, but don't kill CalDAV
#49I'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
#50CalDAV 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 co…