The discussion revolves around an issue with search results when using the combination of “in:first” and “order:latest” on the Weird sort order when search topics/posts with “in:first” and “order:latest” combination thread. jesus2099 initially reported that the results were not sorted by the latest post as expected. Moin pointed out that the issue is caused by the “in:first” filter, which prioritizes the creation date of the first post over the latest activity. jesus2099 acknowledged this and updated the topic title. JammyDodger suggested that this behavior is not a bug but rather the expected result of using “in:first” with the latest filter. However, jesus2099 countered that it would be more intuitive for the results to be ordered by the latest activity, especially in a topic search result list. A potential workaround is to use the “by relevance” option, which produces the desired results.
I think it’s because you search in:first. The post you get as a result is not 19h old, it seems to be from 2017.
But I understand your problem. If searching in:first there is no difference between sort by latest post and sort by latest topic.
I don’t think this is a bug? If you use the in:first filter by latest it will give you the results of the first post in date order. This seems to be working as expected?