Hacker News Reader

If they can combine this ease of accessibility for developers with a security model on the end-user side, I think it can be a solid win.

I'd love to see granularity in what the API can access, for example, TripIt may request something like "Grant access to emails from the domain travelocity.com, usairways.com, etc.," and I can know with confidence that they will not have access to the rest of my inbox.

View on HN

It doesn't have that level of granularity, just four auth scopes:

1) Full access to the account

2) Do everything but permanent deletes of threads and messages

3) Read everything, but no write access

4) Create/read/update/delete drafts and send messages/drafts, but no access to anything else

Finer-grained access (especially for reads, but there are some use cases for finer-grained sending controls, too) would be better, but this is, AFAIK, a step ahead of any other email API.

EDIT: source https://developers.google.com/gmail/api/auth/scopes

I immediately checked for that level of scope when they announced it, my post was merely a "this would be pretty amazing for security conscious end-users" not "this part of the API is cool" -- a wishlist item have you.

Reply on news.ycombinator.com