HyperKitty thread order is not correct.
It appears that !97 (merged), while fixing #151 (closed), has created a new issue. Namely, while the thread view shows all the messages now, the initial message is at the top but subsequent replies are in inverse chronological order (newest first) rather than thread order with replies after the message replied to. Running the Django management thread_order_depth job will fix this, but we should be able to get it right from the beginning.