[aaronbrethorst]

Which JSON-based email standard would that be, exactly?

[e12e]

I believe ops point was that any stable api would be preferable to: "Yeah, there's an api, but we refuse to document it, and we'll randomly depricate stuff if you try to use it to build something that isn't gmail". The team behind gmail is probably one of the best qualified to hammer out a working api for email of json (what we have + a bit of what we want + stability and versioning). No reason why they couldn't publish that as an RFC and let people implement a front end for dbmail or whatnot that spoke the same api.

[aaronbrethorst]

Except for competitive reasons and opportunity cost.

[toomuchtodo]

Thank you. This is what I was getting at. I hope we get closer to this with https://www.mailpile.is/

[toomuchtodo]

Not a standard yet, but this just made it to HackerNews: https://nvlope.com/

"nvlope gives you full control over your mail with a full-blown JSON API. You can build an email client with just 3 API calls - threading included!"

http://developer.nvlope.com/