Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Gmail API

developers.google.com

Post reply on HN
Print view View original

101–110 of 147 posts

Re: Gmail API

#101

Post by thmcmahon »

0x0 wrote: post #90
nairteashop wrote: post #75

Earlier quoted context omitted.

> why would you want to snooze an email? I use my Gmail inbox as sort of a todo list. If a conversation is in my Inbox, it needs attention from me - I need to do some work related to it, reply to it, forward it, etc. Once I'm done with an email thread, I immediately archive it. If you use this workflow (many do), snoozing an email is useful. I use it primarily for threads where I'm not able to reply and provide infor…

Sounds like you should start using flags instead ("stars" in web-gmail?) Then your todo list should be easily accessible through a filtered list of flagged messages. Most IMAP clients offer this out of the box.

Or just use snoozing (I use mailbox) and this problem is solved. I could not go back to using a mail client that doesn't have this feature.

Re: Gmail API

#102

Post by click170 »

iLoch wrote: post #57
xienze wrote: post #48

I can't believe how many people are stoked about this. If you look at https://developers.google.com/gmail/api/auth/scopes , basically apps can do a combination of a) have full control, b) read everything, c) do everything but delete emails, or d) read/write/send drafts. Granting that level of access with no fine-grained control to 3rd party apps seems insane to me. I predict at least a couple major security incidents…

While I somewhat agree with you, it's not as though these problems didn't already exist with IMAP. I think a better way of looking at it is this is the first step in removing the password from 3rd party access. Maybe at some point in the future they'll add more fine-grained access, but for now removing the credentials from the process seems like a good first step. Not sure why they really need an API though. Seems to…

I too would like to know what the benefit of HTTPifying things is, aside from leveraging existing infrastructure.

This was the reason Google provided for not supporting Git in Google Code initially. They do support git now though.

Re: Gmail API

#103

Post by McGlockenshire »

jtmoulia wrote: post #99
jobu wrote: post #22

It would take something pretty amazing for me to allow anyone access to my gmail account. LinkedIn definitely made me skeptical on allowing even trustworthy-seeming companies access to my contacts.

Do you not give any applications IMAP access to your email?

There's a tremendous difference between an email client, whose job is merely to show me my messages, and an application that is not an email client that is designed to do something to my messages other than let me read them.

Everyone's fine with the former, but the second should always give people the creeps.

Re: Gmail API

#104

Post by akerl_ »

pud wrote: post #56
alooPotato wrote: post #17

We (Streak, YCS11) have been using this API for a few days to build our email snoozing feature ( https://www.streak.com/email-snooze-in-gmail ). The API is really nice to use and makes interacting with Gmail way easier relative to IMAP. I'm surprised they don't recommend using this API to build full email clients. I fully expected that to be one of the core use cases. The reason its hard (currently) to build a mail c…

If anyone wants to snooze email without auth'ing your Gmail account, here's one I built in 2008 that's still going strong. http://hitmelater.com/ It costs $30/yr for the high-end service but send me a note and I'll give you a link to signup for free.

Any chance your project is open source? I would do this to something like 2 emails a year, but I'm intrigued by how it works from the technical aspect. Is there a database, or just exim/postfix magic?

Re: Gmail API

#105

Post by comex »

alooPotato wrote: post #17

We (Streak, YCS11) have been using this API for a few days to build our email snoozing feature ( https://www.streak.com/email-snooze-in-gmail ). The API is really nice to use and makes interacting with Gmail way easier relative to IMAP. I'm surprised they don't recommend using this API to build full email clients. I fully expected that to be one of the core use cases. The reason its hard (currently) to build a mail c…

Is there any way to use this feature without all the other Streak stuff cluttering up the UI (among other things, the "box" icon on every message in list view, Pipelines on the left, big button on the top, six new buttons in compose view). The CRM stuff looks spiffy, and getting the snooze feature through you is good advertising in any case, but I don't currently have a use case for those features, so I can't use the extension if it's going to fill up the UI with them.

Re: Gmail API

#106

Post by tlogan »

alooPotato wrote: post #17

We (Streak, YCS11) have been using this API for a few days to build our email snoozing feature ( https://www.streak.com/email-snooze-in-gmail ). The API is really nice to use and makes interacting with Gmail way easier relative to IMAP. I'm surprised they don't recommend using this API to build full email clients. I fully expected that to be one of the core use cases. The reason its hard (currently) to build a mail c…

Feedback: your snoozing feature is confusing because it overlaps with your reminders. Should I use reminder or snooze?

Re: Gmail API

#107

Post by alooPotato »

comex wrote: post #105
alooPotato wrote: post #17

We (Streak, YCS11) have been using this API for a few days to build our email snoozing feature ( https://www.streak.com/email-snooze-in-gmail ). The API is really nice to use and makes interacting with Gmail way easier relative to IMAP. I'm surprised they don't recommend using this API to build full email clients. I fully expected that to be one of the core use cases. The reason its hard (currently) to build a mail c…

Is there any way to use this feature without all the other Streak stuff cluttering up the UI (among other things, the "box" icon on every message in list view, Pipelines on the left, big button on the top, six new buttons in compose view). The CRM stuff looks spiffy, and getting the snooze feature through you is good advertising in any case, but I don't currently have a use case for those features, so I can't use the…

omg yes.

We're working on making all of our features togglable. Stay tuned.

Re: Gmail API

#108

Post by alooPotato »

tlogan wrote: post #106
alooPotato wrote: post #17

We (Streak, YCS11) have been using this API for a few days to build our email snoozing feature ( https://www.streak.com/email-snooze-in-gmail ). The API is really nice to use and makes interacting with Gmail way easier relative to IMAP. I'm surprised they don't recommend using this API to build full email clients. I fully expected that to be one of the core use cases. The reason its hard (currently) to build a mail c…

Feedback: your snoozing feature is confusing because it overlaps with your reminders. Should I use reminder or snooze?

This is a good point. Typiucally, reminders are useful for reminding your team about a box (a deal or customer...) that needs to be looked at. Snoozed emails are just for you and remind you about a particular email.

There is clearly some overlap in use case and we're working on making that better but wanted to get out Snoozing as soon as possible.

Post reply on HN