Better-osm-org: a script that adds useful little things to osm.org

TrickyFoxy · July 1, 2025, 8:12pm

1.1.2: hotfix again, this time to fix object diffs

Please note that osm.org can now also show the number of comments next to changeset links

github.com/openstreetmap/openstreetmap-website

Reorganize changeset history info into two lines, reuse it in element details

master ← AntonKhorev:changeset-line

открытые 01:08AM - 01 Jul 25 UTC

AntonKhorev

+58 -42

Currently if you open `/history` you'll see something like this: ![image](https…://github.com/user-attachments/assets/cb5c6259-71e8-41d6-b9c9-253f06b1d121) In most of the cases each changeset entry has this visual structure: ~~~ (comment tag) Closed (time) by (username) · (n comments) #(id) (n changes) ~~~ Sometimes in case of a longer username the structure is: ~~~ (comment tag) Closed (time) by (n comments) (username) · #(id) (n changes) ~~~ The username is moved to the next line, id is moved to the right. It would be easier to examine the history if things were moving around less often. That's what this PR tries to do, and hopefully it solves a couple of other problems. For usernames to be less often carried over to next lines, we can make their lines longer. We can do it by not having comments/changes counts on the side, moving them below that line instead and arranging them horizontally, on the same line with ids: ~~~ (comment tag) Closed (time) by (username) #(id) (n changes) (n comments) ~~~ ![image](https://github.com/user-attachments/assets/c4ad8f40-b7af-4c7e-b481-a6df5343cf5b) Long usernames will get carried over, but they won't shift ids to the right: ![image](https://github.com/user-attachments/assets/2aae8105-2de5-4d7e-b168-875c73b814cb) Another advantage of this arrangement is that you get two columns for changes and comments counters. If you're interested in discussed changesets, you can visually scan the column with comments counters. Nonzero counts should be even easier to spot because there aren't any edit counts right below them. This should help with https://github.com/openstreetmap/openstreetmap-website/issues/5757#issuecomment-3017341686. Additionally we can take the id-counters line and reuse it in element details, as requested in #3621. This should be useful on element history pages when looking for controversial changes to a single element. Edit counts are irrelevant for this goal and are not shown. ![image](https://github.com/user-attachments/assets/20e9ba12-4b87-4fd6-b4d6-786a16152218) --- Fixes #3621. Fixes #5757 further.