Google: Do what you want with Reader, but don't kill CalDAV
zdnet.com
zdnet.com
As much as I dislike everything Microsoft, 365 currently looks well ahead of Google (everything they haven't killed yet has definitely stopped evolving), and has certainly proven to be a more reliable partner for business use.
This is not just ugly and confusing from a marketing and branding perspective, it leads to all kinds of complications with software that reacts to email-addresses, or services that are coupled to Google Apps.
We have one primary domain and 15 alias domains. Email Example: user@alias.com gets an email, when they reply it stays set to the alias, it doesn't change to the primary domain.
According to Google, they don't include this header if you upgrade to Google Apps for Business.
Until they decide--all of the sudden--that you can't any more (assuming you can now). His point is that Google is unreliable as a long term partner and should not be counted on.
I have not found anything on such a migration path so far, only more or less desperate forum posts …
Google Apps also have the advantage that you can mix free and paid accounts. We have for example some employees who share their business calendars (paid accounts) with their family members (free accounts).
> "They specifically name three: showing irrelevant ads, using pop-ups or other annoying gimmicks, and selling off actual search results. Hardly the stuff of comic books. But what do these three have in common? They’re all instances of refusing to make things worse for your users in order to make more money"
This is just about the first time I've seen Google unambiguously break their own definition of 'evil'.
[1] http://www.aaronsw.com/weblog/googevil
Edit: On reflection... not the first time.
Evil is a relative term, and if Microsoft is seen as the Evil empire then cutting off amicable relations (manifested by open interfaces) can be construed as "not evil"
Read the update to the article, where he points out that the entire concept of ads could be construed as evil by some.
However, 'evil' is not defined in context: https://www.google.com/about/company/philosophy/
Therefore, the leap "evil = make things worse for your users" is not from a google source. That's Aaron's attempt to construct a categorical rule from the examples.
"Google unambiguously break their own definition of 'evil'." <-- False, since google didn't explicitly define evil. They broke what Aaron believed google meant when they said "evil".
Microsoft isn't pure evil, they're were just seen as being closer to the bloodthirsty end than Apple or Google. It used to be that Google was seen as closer to the FSF side than, say, Microsoft.
Nowadays, it's pretty clear all of these big tech firms are not far apart and moving more towards the ruthless side of the spectrum.
Seems to be fair enough for me, just in case anyone cares.
Where's the argument against CalDAV? (I'm not saying it doesn't exist, I'm just surprised to not have seen anything from them)
I think omitting a border around ads and intentionally reducing the contrast from the background to make it invisible to older people and people with bad monitors does count as an annoying gimmick and a user-hostile anti-pattern. The A/B testing would've shown a lot of ad clicks and increase in profit from people who mistake them for organic search results.
http://blumenthals.com/blog/2012/01/31/is-google-intentional...
And also, didn't Google change its shopping results to be paid search results?
http://www.forbes.com/sites/anthonykosner/2012/05/31/how-evi...
I would think the beancounters are rapidly taking over.
In addition to that, I'd argue looking at your picture that it really doesn't matter if it's an ad or not - if it were an organic result and you didn't want to file a lawsuit, you wouldn't click it anyway.
Shutting down a service is now considered "evil"? That's a stretch if there ever was one...
That's 90's Microsoft-level "evil".
Like hell they aren't: https://developers.google.com/google-apps/calendar/pricing
As soon as I find something with a decent calendar system (web, CalDav, time zone support, decent interface and subscribing to iCalendar feeds) as well as decent email (useful interface, good filtering, acceptable spam filtering), and hopefully, XMPP support baked in, I'm jumping ship. This is starting to get ugly.
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.
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 to sync up everything between the two.
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?
So what's next - no IMAP for gmail? And then force everyone to use a custom gmail app?
Edit: I forgot they're turning off ActiveSync for free users later this year
Then I'd have cobble together whatever oss webapps I need to access all that remotely, and then lock the whole thing down -- ideally only allow external access via ssh and then set up my phone/laptop to VPN through it when I want access.
It would be at least a day of work to set it all up but I think I've almost reached the requisite pain point.
EDIT: and it would be nice if I could run phone numbers through it as well via something like http://voip.ms/ ... if anyone is aware of someone doing something like this and writing it up I'd be interested to know, I haven't come across any setup like this.
* 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.
http://www.quora.com/Cryptography/Is-there-any-zero-knowledg...
When I transition to a new computer all I have to do is install chrome and I basically have everything I need - the login will get me all my extensions + put me in email, calander, voice, youtube, and search. All with one login, that's the power, people are lazy, they don't really care about OSS or freedom, they follow the path of least resistance, and in this case that's Google, good or evil.
It sucks but it's true. I keep thinking about moving to a different email provider but then I have to find one that does all the things that gmail does, and has a decent calender app (there is NO replacement for voice) and something that does search in an okay and understandable way. I can't find one. The only reason I use facebook over G+ is because I don't know anyone on G+ otherwise that too wold be my social network of choice. In addition my University uses Gapps so I'd be stuck with google regardless (for at least the next four years).
And really that's the issue, so far it seems from history that once you reach a certain critical mass, there is no way to not be evil, Google was great until about 2011, but they've turned on us....
wow...just realized this is a lot of rambling... still I make a couple good points
However, with Reader, it's kinda served as a warning to me. I use this stuff every day. Reader was just kinda the reminder that I don't own any of this stuff, and they can turn it off at any time. 2 years ago, I had basically zero fear of something like that. Today, especially with CalDAV support getting killed, it's just another warning to me that Google is a different company than it was.
Anyway, I'm typing this on Chrome in between reading Gmail and Google Voice messages and stuff, but I'm definitely looking for alternatives. Too much of my life relies on Google. Don't want all my eggs in one basket.
Does anyone know if Apple is one of those whitelisted developers?
Google is risking their credit in supported open standards.
...
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...
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)
Edit: I have several Google Apps for Business domains. I'm looking for alternatives.
[1] https://www.rackspace.com/apps/email_hosting/exchange_hostin...
It's exchange/activesync. Works great.
I'm sure IMAP support in Gmail will be next on the chopping block.
I probably would've said the same thing about CalDAV last week.
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.
Google is dropping Reader, but we can use opens source projects to find another RSS reader. Heck I use Thunderbird for my RSS reading.
Radicale looks nice, but I haven't managed to get it to work properly so far.
Nobody's pulling the rug out from under me. Except me.
Reader - Self-hosted Fever, although currently evaluating Tiny Tiny RSS. Checked out Newsblur a while back but felt like the interface was too busy/animated (same reason I left Reader). TTRSS feels a lot like Bloglines of old (which I loved but seemed to die on the vine)
Calendar - Bouncing between my email host's solution (pobox.com has a caldav/carddav server now) and iCloud, but considering setting up my own caldav/carddav server.
What about on an iPhone?
No one from either company has commented or confirmed it either way. It's a major reason why people are so surprised and incredulous about Google moving away from the standard.
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.
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 boy. But then they started changing. Ever since G+, they just seem hell bent on becoming a social network. That shit really pissed me off. How do you simply go from awesome company to this? I'll tell you how. Because its now being run by people who put profits first, and not the users/programmers. They seem to have forgotten that it was us who gives them the profits they get. Such is the reason I'm building Nuuton. Because fuck you Google.
Maybe that's fine with them (seems like they have a corporate mission to eliminate the whole idea of free or nearly-free web APIs anyway), but regardless of their motivations they've proven to be a non-reliable provider of stable free-to-use web APIs over the past couple of years.
You can't built bridges on top of shaky ground.
Google is clearly not an open source company.
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.
That's why I will 'never' embrace cloud that tightly.
We have heard it before, with Microsoft, we are hearing it again with Google, and we will hear it again with someone else in the future.
[1] http://en.wikipedia.org/wiki/Embrace,_extend_and_extinguish
Just because they didn't satisfy your demands you decide to take such a drastic turn? Perhaps they were trying to satisfy other casual Internet users as well.
Not to say you're wrong or whatever, but a huge company like Google tries to satisfy as many people as possible to increase their market-share. I don't necessarily see something wrong as long as all the negative side affects aren't solely absorbed by the consumer.
There's nothing wrong with compromises here and there - any healthy relationship consistently needs to deal with them.
If that is the tipping point for you, then by all means show support for alternatives. I know I do a terrible job at ensuring Google isn't the only player in the game.
I imagine a pinboard.in like service but for mail (cheap, fast, simple, run by a developer that I trust to worst case mail me a DVD of my mail history). I'd jump to that very quickly.
Calendar API wasn't the worst - okay, I didn't get any response from Google guys on a bug I ran into, but they eventually fixed it (and lack of user support is pretty much a norm for them now).
The situation with Spreadsheets is way worse - the API is pretty much abandoned, no changes or any reaction to bugs/complaints for a few months now. They'd roll out a new API version, remove the old documentation (instead of marking it as deprecated but accessible), but the new documentation is really lacking - only has examples in C#, and even these are incomplete.
So, yeah, moving from open standards to their own API is very bad - not just because it's locking up people or something, but also because they are not supporting _their own APIs_ properly.
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 calendars, CalDav is a well documented standard for sharing calendar data. It robustly handles all the use cases that we've been able to think of (including edge cases).
It's disappointing to hear that Google will discontinue the service. I'm sure lots of iOS and Mac users use the CalDav sync to natively sync their Google Calendar to their devices. How will users of native apps be able to get their calendar now?
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.
I'm not sure what the plan is now. Hopefully Apple will be in the approved third party list for extended CalDAV support.