<blockquote>
<p>So the question is, if we accept this, are we then expected to do the same for every other mobile app that chooses to follow the same path? Where would that end?</p>
</blockquote>
<p>We do not have a precedent law here, each provider is decided on separately. And I assume, next time there will be a similar discussion. I'd be happy to see another OSM-based app with millions of users making pull requests to the website.</p>
<p>Now really, what it blocking this pull request? I removed the only non-technical blocking feature, I have tested the branch, this PR does not worsen the website or change any of the workflows. The service will be up next month, and we'd like to make the whole transition to the new sign-in process. How can I help with reviewing this? Is there something I can do?</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/pull/1433#issuecomment-296692304">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABWnLe-O2QJG5c4H2WQka8aXgAQLU7DNks5rzLZFgaJpZM4L8Kyb">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABWnLf9UmlR12vFvlStdwxCZWBGKJNnjks5rzLZFgaJpZM4L8Kyb.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
<link itemprop="url" href="https://github.com/openstreetmap/openstreetmap-website/pull/1433#issuecomment-296692304"></link>
<meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/openstreetmap/openstreetmap-website","title":"openstreetmap/openstreetmap-website","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/openstreetmap/openstreetmap-website"}},"updates":{"snippets":[{"icon":"PERSON","message":"@Zverik in #1433: \u003e So the question is, if we accept this, are we then expected to do the same for every other mobile app that chooses to follow the same path? Where would that end?\r\n\r\nWe do not have a precedent law here, each provider is decided on separately. And I assume, next time there will be a similar discussion. I'd be happy to see another OSM-based app with millions of users making pull requests to the website.\r\n\r\nNow really, what it blocking this pull request? I removed the only non-technical blocking feature, I have tested the branch, this PR does not worsen the website or change any of the workflows. The service will be up next month, and we'd like to make the whole transition to the new sign-in process. How can I help with reviewing this? Is there something I can do?"}],"action":{"name":"View Pull Request","url":"https://github.com/openstreetmap/openstreetmap-website/pull/1433#issuecomment-296692304"}}}</script>