Hacker News new | past | comments | ask | show | jobs | submit login

It was meant to replace email, an open standard sporting many interoperable servers and clients, with something that Google controlled, even though it was theoretically federated.

After Wave failed, they doubled down on making Gmail into more of a nonstandard product with reduced interoperability (now requiring Gmail API instead of standard IMAP) and increasingly, embrace & extend functionality such as email expiration dates.




It wasn't theoretically federated. It was actually federated. Interop outside Google actually happened.

Is something not working with gmail's imap support?


Issues with Gmail IMAP as voiced by other people:

https://news.ycombinator.com/item?id=16951363

https://www.dvratil.cz/2014/06/improved-gmail-integration-in...

https://productforums.google.com/d/msg/gmail/9A5oYELFbu8/7iq...

https://github.com/mscdex/node-imap/issues/71

https://freron.lighthouseapp.com/projects/58672/tickets/1247...

Sure you can still access Gmail through IMAP, but if it works differently enough that using a standard IMAP client feels cumbersome and unfamiliar, is it really anything else than a vehicle to tell people that they should really just use the "better" Google product directly?

That said, my original wording of "requiring" the Gmail API was poor and I should have phrased it more accurately.


IMAP sucks at not destroying your battery though. That’s why everyone was using the (also proprietary) activesync provided by exchange.


Google Talk was also federated for some time. Good old times when we could dream of continents, but it has all drifted away and become islands.


Well, now we have Slack, and Google Wave seems comparably tame.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: