<p><a href="https://github.com/gravitystorm" class="user-mention">@gravitystorm</a> osmcha and probably every other use case that needs to access any user information already hits the user endpoint (at least once), example <a href="http://api.openstreetmap.org/api/0.6/user/100950">http://api.openstreetmap.org/api/0.6/user/100950</a> I suspect referring to a dump of the data (which currently doesn't exist) is not going to be very popular (not to mention premature optimisation etc).</p>
<p>Even if my suggestion of simply adding a last block attribute is considered too hackish, a -separate- API doesn't seem to make sense when additional information can simply be added to the already existing blocks section in the user API (even in the worst case we are not talking about more than a handful of entries).</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/issues/1618#issuecomment-325188199">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABWnLaVWk2MDzvQ9UCmXdJMVdITPseGHks5scTtYgaJpZM4PBfE2">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABWnLS7w7da2Yvx9ieHuAIAS3VP2vqCvks5scTtYgaJpZM4PBfE2.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/issues/1618#issuecomment-325188199"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue 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":"@simonpoole in #1618: @gravitystorm osmcha and probably every other use case that needs to access any user information already hits the user endpoint (at least once), example http://api.openstreetmap.org/api/0.6/user/100950 I suspect referring to a dump of the data (which currently doesn't exist) is not going to be very popular (not to mention premature optimisation etc).\r\n\r\nEven if my suggestion of simply adding a last block attribute is considered too hackish, a -separate- API doesn't seem to make sense when additional information can simply be added to the already existing blocks section in the user API (even in the worst case we are not talking about more than a handful of entries)."}],"action":{"name":"View Issue","url":"https://github.com/openstreetmap/openstreetmap-website/issues/1618#issuecomment-325188199"}}}</script>