[openstreetmap/openstreetmap-website] Add allow_read_email oauth permission (#1431)

[mmd]

> in order to create messages in our API programmatically via emails, which need to be queued and parsed and acted on internally.

We already have this in place as of today! Try sending a direct message via osm.org from user A to user B, and have user B reply to the email they receive. Currently, that email address has the format <m-<number>-<number>@messages.openstreetmap.org>. It can be easily reused and represents a one-way communication channel between those two users.

> If all we were doing was accepting messages and/or notifications then it would make more sense, but each client app will already be using our API anyway.

Depends a bit on the use case. I'm really having notifications in mind, where your Garmin or map download is ready for download. In any case, sending emails would be more universally available and avoids the extra effort for everyone to implement some new (osm proprietary) messaging API. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/1431#issuecomment-454863865
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20190116/d78aebff/attachment.html>