3 ms·
> Proprietary Clients: You cannot use your own email client to access Hey. The stated justification for this is just lazy imo. Even Gmail which launched with a
by Wowfunhappy 5y ago
> Proprietary Clients: You cannot use your own email client to access Hey. The stated justification for this is just lazy imo. Even Gmail which launched with a then unique labels and smart organization still allows IMAP support. The Screener could very well have been a mapped IMAP folder, and you could just move to Inbox to accept new emails in. When you build on top of an open protocol and then refuse interoperability, it reeks of an old Microsoft playbook.
I’d actually flip this around—I don’t see any reason Hey couldn't and shouldn't just be an email client, which could work with any existing service.
Unless it's a strategy to lock in users. No deal for me, thanks.
- joshka 5y ago> I’d actually flip this around—I don’t see any reason Hey couldn't and shouldn't just be an email client, which works with any existing service. This is the main thing that keeps me from even trying it. But also the lack of import of many years of existing mail.
- mattl 5y agoI imported all of my previous year's email into HEY by opening my Gmail mailbox in mutt, selecting all the messages in INBOX (for example) and using mutt's bounce feature to bounce them over to HEY.com. Yes, the screener went nuts for a moment when I had thousands of emails to evaluate but it brought over some of the mail I get regularly and has been a game changer for me in terms of email productivity.
- qshaman 5y agoBecause they wont be able to plug in RoR or rant on how you should "embrace the monolithic" and use Hey as a success story, and their fans will be very unhappy ;) Because with those people, is their way or the highway.