91–100 of 132 posts
Why can't we just roll our own CalDAV server via open source projects instead of getting upset that Google is dropping it? Google is dropping Reader, but we can use opens source projects to find another RSS reader. Heck I use Thunderbird for my RSS reading.
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.
It's exchange/activesync. Works great.
Earlier quoted context omitted.
I've actually been putting numbers on this: there are many fans of NewsBlur, apparently, as a replacement for Google Reader, so that's $12 a year; I'm worried about being tied to my Gmail address, so I finally got around to setting up a vanity domain address which forwards to Gmail and that's going to be about $10 a year. So I'm up to $22 a year, and I haven't looked into any free or paid replacements for Google Cale…
pobox.com ( http://pobox.com/pricing ) is a fairly stable domain for email with lifetime hosting for as low as $20/yr (forwarding only) or $50/yr (hosting)
Earlier quoted context omitted.
Replacing an open standard with your own proprietary crap once you have achieved dominance (anybody here not using Google Calendar?) in the market? That's 90's Microsoft-level "evil".
Microsoft-level evil would be charging people for the privilege of using the API, like with ActiveSync. Google isn't quite there yet, but they're certainly moving in that direction.
Like hell they aren't: https://developers.google.com/google-apps/calendar/pricing
With all the reader noise I missed CalDAV would be killed. I just checked Apple Calendar and realized that its set up to sync with my Google Calendar with CalDAV? Does anyone know if Apple is one of those whitelisted developers?
Earlier quoted context omitted.
For my day job I work on a Calendar application. We provide a CalDav service for customers to access their Calendar data. While it can get tricky to support all the variations, it's a solid standard that makes integration really easy. One problem we have is that Android doesn't natively support CalDav, so we can't integrate with the built-in Android calendar like we can with iOS's calendar. For those that work with c…
Exchange ActiveSync Edit: I forgot they're turning off ActiveSync for free users later this year
I have been a long time android user and had every intention of continuing down that path, but recently my job has required me to use Exchange ActiveSync to access my corporate mail & calendar data on my device, its a bit of a hassle but at least it's supported.
Does this mean that future versions of android will not have support for such a (common business related) setup?
If this is true I foresee it alienating a large portion of their user base.
Earlier quoted context omitted.
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…
> 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. Except caldav is just a protocol. It's not an API. Google could have made an API that supports the caldav protocol, but chose not to. This also effects me a lot, personally, because I have a Kindle Fire and an iPhone, and I use my Google calendar…
This move would then represent Google refusing to accept that format?
I didn't read things that way.
It makes good business sense - look at Maps API. You can get X number of free calls, but if you go over a certain limit you need to pay (That limit is pretty high if I recall)
So now fast forward to Microsoft and Others incorporating that API into their products - am I understanding correctly Google could charge for API calls similarly?
I hope a lot of developers write to google and just tell them they simply can't afford resources to support proprietary APIs when perfectly good open APIs exist. That's a good enough reason to me. The idea that Google is going to continue maintaining a CalDAV API but expects legions of 3rd party developers to devote time and effort to making special calendar integrations for their proprietary API is obnoxious. At very least, some more rationalization of this is needed from Google.
Earlier quoted context omitted.
Microsoft-level evil would be charging people for the privilege of using the API, like with ActiveSync. Google isn't quite there yet, but they're certainly moving in that direction.
> Google isn't quite there yet Like hell they aren't: https://developers.google.com/google-apps/calendar/pricing