[openstreetmap/openstreetmap-website] Filter out changesets that are too old when sorting in ascending order (PR #4164)

[Anton Khorev]

Someone might want to sort changesets by close time if they want to show closing events independently. In [my changeset viewer](https://github.com/AntonKhorev/osm-changeset-viewer) there's an option to show them with output looking like this:

![cset-viewer-closed-csets](https://github.com/openstreetmap/openstreetmap-website/assets/4158490/cfd14bb4-d3bc-4d2c-a959-9c161025cf86)

Most of changesets on this image were made by StreetComplete. They can overlap in all kinds of ways. Sorting by open time and by close time may give significantly different results. Therefore any sudden change to sorting in the API may break already written code. For example, [this paging code](https://github.com/woodpeck/osm-revert-scripts/blob/54e99458bd029030b7e0d42141d392bc8f2ae4e2/UserChangesets.pm#L80) relies on changesets being sorted by `created_at`.

Here's a small example of changesets that change order depending on if they are sorted by open or close time: https://api.openstreetmap.org/api/0.6/changesets?user=550156&time=20220923T185808Z,20220923T195831Z

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/4164#issuecomment-1679860252
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/pull/4164/c1679860252 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20230815/797bda4e/attachment.htm>