<blockquote>
<p>In this situation, my preferred solution would not involve the editing API at all, but instead be a completely separate service which could be run and scaled entirely independently</p>
</blockquote>
<p>If anyone feels like this is something for Overpass API, here's a query proposal to fetch the object at a given point in time. Ideally, this should be one second before the object was deleted:</p>
<pre><code>[timeout:5]
[date:"2018-03-12T22:47:00Z"];
way(id:539940355);
(._;>;);
out;
</code></pre>
<p><a href="http://overpass-turbo.eu/s/x4C" rel="nofollow">http://overpass-turbo.eu/s/x4C</a></p>
<p>Original object: <a href="https://www.openstreetmap.org/way/539940355" rel="nofollow">https://www.openstreetmap.org/way/539940355</a></p>
<p>I don't have an idea how often deleted features are shown as single object today, so it's very difficult from the outside to assess the performance impact of such a query.</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/1448#issuecomment-373793113">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABWnLUhye63yKSG5AJky015IGl_iLBkMks5te_sugaJpZM4MFd7Q">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABWnLWg8bdIHbbJMC_k4BbFYc-LKk0wBks5te_sugaJpZM4MFd7Q.gif" height="1" width="1" alt="" /></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/1448#issuecomment-373793113"></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":"@mmd-osm in #1448: \u003e In this situation, my preferred solution would not involve the editing API at all, but instead be a completely separate service which could be run and scaled entirely independently\r\n\r\nIf anyone feels like this is something for Overpass API, here's a query proposal to fetch the object at a given point in time. Ideally, this should be one second before the object was deleted:\r\n\r\n```\r\n[timeout:5]\r\n[date:\"2018-03-12T22:47:00Z\"];\r\nway(id:539940355);\r\n(._;\u003e;);\r\nout;\r\n```\r\n\r\nhttp://overpass-turbo.eu/s/x4C\r\n\r\nOriginal object: https://www.openstreetmap.org/way/539940355\r\n\r\nI don't have an idea how often deleted features are shown as single object today, so it's very difficult from the outside to assess the performance impact of such a query.\r\n"}],"action":{"name":"View Pull Request","url":"https://github.com/openstreetmap/openstreetmap-website/pull/1448#issuecomment-373793113"}}}</script>