On the backend, I've boosted original_posts from the mailing list but I also think we can do a better job ordering the groupings of threads.
Let's display the original_post as the parent of the grouping and if there are no original_posts, let's go in date order which you can pull from the created_at field OR you can pop the resource identifier off after the last slash (e.g. as in 018045 of https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-July/018045.html) and use that number to order them (lowest first).
On the backend, I've boosted original_posts from the mailing list but I also think we can do a better job ordering the groupings of threads.
Let's display the original_post as the parent of the grouping and if there are no original_posts, let's go in date order which you can pull from the created_at field OR you can pop the resource identifier off after the last slash (e.g. as in 018045 of https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-July/018045.html) and use that number to order them (lowest first).