4 ms·
It wasn't theoretically federated. It was actually federated. Interop outside Google actually happened. Is something not working with gmail's imap support?
by rossjudson 8y ago
It wasn't theoretically federated. It was actually federated. Interop outside Google actually happened.
Is something not working with gmail's imap support?
- ce4 8y agoGoogle 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.
- jpetso 8y agoIssues with Gmail IMAP as voiced by other people: https://news.ycombinator.com/item?id=16951363 https://news.ycombinator.com/item?id=16951363 https://www.dvratil.cz/2014/06/improved-gmail-integration-in-kde-pim-4-14/ https://www.dvratil.cz/2014/06/improved-gmail-integration-in... https://productforums.google.com/d/msg/gmail/9A5oYELFbu8/7iq7WTVrBAAJ https://productforums.google.com/d/msg/gmail/9A5oYELFbu8/7iq... https://github.com/mscdex/node-imap/issues/71 https://github.com/mscdex/node-imap/issues/71 https://freron.lighthouseapp.com/projects/58672/tickets/1247-gmail-labels-with-non-ascii-characters-not-working#ticket-1247-7 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.
- lawnchair_larry 8y agoIMAP sucks at not destroying your battery though. That’s why everyone was using the (also proprietary) activesync provided by exchange.