Live data from Hacker News

Gmail API

developers.google.com

111–120 of 147 posts

Re: Gmail API

#112
post #39

Earlier quoted context omitted.

Granularity is the key here. I run a small self-tracking service (zenobase.com), and would love to let my users pull in some "metadata" from their email (e.g. the number of messages in the inbox, or the number of messages sent by hour). But I don't want my users to trust me with unrestricted access to their email.

A meta data only permission would be cool. Access to from, to, cc, date, labels, etc for all mails but no access to the actual content would be good.

You could label it "NSA access".

Re: Gmail API

#113
post #56

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.

I couldn't image handling email without a service like this, so I've built one as my first out-of-Codecademy project. I'm kinda proud that it works!

Free to use: http://www.pfalke.com Open source: https://github.com/pfalke/returnx

Re: Gmail API

#116

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…

Just a heads up, your Youtube videos on the home page won't play in Chrome if you loaded the page over HTTPS (you get a blank pop-up and the "This page contains insecure content." message). Slick product you have!

Re: Gmail API

#117

I like the idea of opening gmail up to developers via a public API, but I don't like that it comes at the cost of removing support for an open standard like IMAP. I'm worried that API access could be cut back or eliminated entirely in the future depending on developer uptake, leaving gmail entirely inaccessible to third-party applications. Edit: I'm going off of this sentence: >It will replace IMAP, a common but comp…

TBH, I've never understood why more people didn't explore the multipart content type feature of email to extend email. It's typical to have plaintext and html in the same email, but why no JSON using a well defined and published JSON-schema.

I'm pretty sure that absolutely nothing is preventing this, and you could start sending emails with JSON inside right now. The hard part is probably finding something meaningful for it to do.

Re: Gmail API

#118
We (http://grexit.com) let users share Gmail labels. We're very happy to see this release as it has been a pain to build and scale our service over IMAP.

It'd be interesting to see what kind of limits (no. of calls, concurrency etc.) that Google has put on the API. Has anyone trying this out hit of any of these issues yet?

Re: Gmail API

#119

Sadly, the API doesn't support search, which makes it extremely limited for all but trivial apps.

it does support search EDIT: see https://developers.google.com/gmail/api/v1/reference/users/t... and look at the 'q' parameter

I stand happily corrected.
Post reply on HN