News for hackers. Stuff that matters.
Re:Expunging Google by onemorepassword on Monday April 22, 2013 @03:40AM (#5588289)
You must have not been paying attention. A long list of evidence has been posted here on HN on several occassionas, including dropping CalDAV, of Google turning against the open web.

It's nothing new either, it has been going on for years. They've even dropped their support for net neutrality years ago.

In the mean time Google has been heavily pushing the Google+ walled garden, their anti-privacy and anti-anonymity agendas, and has been pro-active in filtering their services on behalf of the copyright-exploitation industry.

This is not a conspiracy theory, it's just a matter of connecting the fairly obvious dots that barely need connecting because there are so many of them by now all that's missing is an official "fuck the open web" press statement.

Re:Expunging Google by dalks on Monday April 22, 2013 @05:53AM (#5588594)
> HN on several occassionas

3 if I count correctly: Reader closedown (which, in my opinion, not a hit to open web at all), XMPP Federation issue (It's fixed now) and CalDAV whitelist (Not closedown, whitelist).

Re:Expunging Google by leephillips on Monday April 22, 2013 @09:52AM (#5589219)
They dropped the Microsoft Exchange format for syncing contacts in favor of the open cardDAV format, so that's one piece of data the points in the other direction.

[Edit: originally typed "calendars" instead of "contacts".]

Re:Expunging Google by runjake on Monday April 22, 2013 @12:36PM (#5590208)
> They dropped the Microsoft Exchange format

For free customers. It's still there for us paying customers. Google pays Microsoft a licensing fee for use of the EAS specs.

Re:Expunging Google by tobr on Monday April 22, 2013 @07:34AM (#5588819)
Several is "more than two but not many" according to Oxford Dictionary, so three should count as several.
Re:Expunging Google by crsna on Monday April 22, 2013 @07:58AM (#5588872)
Doesn't whitelisting amount to closing of interface? They may very well use the CalDav protocol which is open, but how good is it if the consumption interface is not open?
Re:Expunging Google by runjake on Monday April 22, 2013 @12:38PM (#5590226)
Perhaps it was done to prevent spam, or to prevent misbehaving clients from wreaking havoc on its servers.

From hearsay, I understand it's reasonably easy to get on the whitelist if you're a moderately-known app developer or a legit institution. This would lead me to believe Google's reasons are less nefarious in this case.

Re:Expunging Google by aidenn0 on Monday April 22, 2013 @01:19PM (#5590481)
4) Dropping native RSS support in Chrome
Re:Expunging Google by jamesgeck0 on Monday April 22, 2013 @01:45PM (#5590664)
Can't drop something you never had. As far as I can remember, it's always been an extension.