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

121–130 of 132 posts

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

#121

Post by akx »

onemorepassword wrote: post #66

I'm pretty much done with Google as supplier of business apps. I have to migrate our company's Google Apps account anyway because of a (domain)name change (which is still hell with Google Apps anyway, you basically have to buy and setup a totally new account an migrate everything by hand or with 3rd party tools), so I might as well look for another supplier. As much as I dislike everything Microsoft, 365 currently lo…

FYI: You'll have to do the same new account + migration thing with O365 if you wish to change plans (from P1 to E1, for instance).

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

#122

Post by carl689 »

onemorepassword wrote: post #110
chapel wrote: post #73

Earlier quoted context omitted.

You can add alternate domains to Google Apps accounts which can work just as the main domain. So you don't have to migrate anything, it is the same account just acknowledges and accepts the alternate domain.

No they don't. This is the reason why this is such a hell. Yes, the account acknowledges the alternate name, but Google keeps publicly replacing it with the primary name as soon as you do anything. 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.

Perhaps I am not following 100%, but I believe we have done this without this issue for years with 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.

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

#123

Post by Karunamon »

workbench wrote: post #117
surrealize wrote: post #65

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.

Ohh well thats absolutely fine then if they're killing off all the competition with a subsidised product then switching all the standard access to their own API because they're doing it for ★FREE★.

What if the API is superior to the "standard access"?

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

#124

Post by SkyMarshal »

thedragon4453 wrote: post #101
SkyMarshal wrote: post #58

Earlier quoted context omitted.

Interesting list. This got me wondering if there are any zero-knowledge email providers out there, especially ones that let you use your own domain. Only thing I found so far though is an empty Quora question: http://www.quora.com/Cryptography/Is-there-any-zero-knowledg...

For that particular need, I'd expect that I'm rolling my own, or using a service provided by my business or something. At the very least, I'd assume that I'm paying for it, and even then, when you get to that level, you probably want to just do it yourself for the knowledge that you really do have complete control.

Yup, I'd expect to pay for such a thing, no problem with that, just don't see any even for pay. Rolling my own is the other alternative, will probably end up doing that.

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

#125

Post by raldi »

spinchange wrote: post #114
raldi wrote: post #94

Can someone explain, in a way that assumes no prior knowledge of CalDAV, what the impact of this change will be?

Short, worst-case answer: Google web calendars no longer syncing with Microsoft or Apple's local ones. There are finer points and some exceptions, but that's the basic bottom line.

Like, right now you can sync iCal on your Mac with Google Calendar, but next year that won't be possible?

What about on an iPhone?

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

#126

Post by spinchange »

raldi wrote: post #125
spinchange wrote: post #114

Earlier quoted context omitted.

Short, worst-case answer: Google web calendars no longer syncing with Microsoft or Apple's local ones. There are finer points and some exceptions, but that's the basic bottom line.

Like, right now you can sync iCal on your Mac with Google Calendar, but next year that won't be possible? What about on an iPhone?

It remains to be seen. Google has said that they will "whitelist" certain developers to continue using CalDAV which is what iCal uses to sync both the Mac & iPhone. One would hope/expect that Apple will be one of those developers.

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.

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

#127

Post by flyinRyan »

gcp wrote: post #112
UnoriginalGuy wrote: post #47

Earlier quoted context omitted.

Chrome isn't OSS. You're thinking of Chromium.

Chromium for Android is a joke. It doesn't even have tabs and has nothing in common with Chrome. I wonder what they need to hide. Google is clearly not an open source company.

When was Google ever an open source company? Search, Gmail, Buzz, G+, .... what is it they do do open source?

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

#128

Post by thedragon4453 »

vxNsr wrote: post #102
thedragon4453 wrote: post #44

Earlier quoted context omitted.

Well, that depends. I had the same reaction, and my thought was to basically go the opensource route, but some products almost have to be replaced with a company. Products I use from Google: * 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 j…

See the real thing Google has is not that they offer a bunch of services, it's that those services are all tied together very neatly. 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…

This is kinda the rough spot for me too. Google services are just so damned convenient. Especially with the integration. I noticed the same thing you have. Computer dies? No big, fix it and sign into Chrome. I'm 90% there.

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.

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

#129

Post by csixty4 »

carl689 wrote: post #122
onemorepassword wrote: post #110

Earlier quoted context omitted.

No they don't. This is the reason why this is such a hell. Yes, the account acknowledges the alternate name, but Google keeps publicly replacing it with the primary name as soon as you do anything. 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.

Perhaps I am not following 100%, but I believe we have done this without this issue for years with 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.

Gmail sends a Sender: header with the account's primary email address, which some email programs treat as the "actual" sender. Some mail programs display this as "From alias@example.com on behalf of primay@example.net" and then those programs use the primary as the return address.

According to Google, they don't include this header if you upgrade to Google Apps for Business.

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

#130

Post by smokinjoe »

wuest wrote: post #120
smokinjoe wrote: post #61

Earlier quoted context omitted.

> 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. 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 wro…

I don't think that Google showing a propensity to give services the axe, rather than simply deprecating them and giving them little or no support is a case of "not satisfying demands." That, mixed with their history of spotty support for the things which they DO officially support gives them the appearance of being a shifting platform. This lead me, at least, to depend on them as little as I have to.

Hey, that's your opinion and I can't call it wrong! Although I strongly feel like Google Reader was by far the most used service they are going to axe. I was pretty upset when Google Notebook was axed, but I just moved my data elsewhere. I don't really expect much with deprecation after that incident because while the service was deprecated, the lack of support/updates just left me never wanting to use it anymore.

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.

Post reply on HN