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

[Andy Allan]

> AFAIK, we currently don't an API to support this use case.

Yes, we would need to add an API either for messages, or for a more unified notifications system.

> Would you think it makes sense to follow up on the proxy email concept I outlined earlier on?

I'm not sure about this approach. We would then end up with a third party calling our API, to receive a proxy email address, that they then create and send emails to, in order to create messages in our API programmatically via emails, which need to be queued and parsed and acted on internally. That's instead of creating a message or notification directly via an API call. It seems a bit indirect to me, and it makes some things (like rate limiting API calls) harder to manage. 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.


-- 
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-454846187
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20190116/84f6341d/attachment.html>