Users are discussing the addition of an orderdesc modifier to Discourse’s advanced search to allow descending order for any sort field (e.g., orderdesc:views, orderdesc:likes). meglio proposes this as a universal solution for reverse sorting, noting potential use cases like identifying low-engagement content or improving SEO. riking suggests using order:-views or order:-latest syntax instead. sam expresses skepticism about the need for orderdesc:likes or orderdesc:views, but is open to adding order:earliest for rare cases. meglio counters that unexpected use cases may arise, advocating for a consistent operator. chadwhitacre supports the feature for managing forum “inbox” workflows by sorting posts from least to most recent. riking offers the Unanswered filter as an alternative and mentions a PR adding “Oldest Update” sorting, seeking better naming. Canapin shares personal experience searching within topics and notes confusion between “Latest Post” and “Latest Topic” sorting, suggesting clearer chronological options (ascending/descending) would be helpful — even if used mostly for fun. The thread highlights demand for flexible, intuitive sorting controls beyond the current defaults.
struggling to think of use cases for orderdesc:likes or orderdesc:views, though I am open to possibly adding order:earliest (its quite rare to need though)
We should find a way to allow for opposite ordering for any ordering type (kind of a universal way of doing it), then easier to remember and use.
You never know what one could come up with
I’d use orderdesk:likes to identify which type of material is the worst in terms of people likes and not create similar topics, or not include them in the lists.
orderdesc:views might possibly indicate topics that need some more useful information to get more attractions from organic search.
I think there might be more use-cases I can’t think of, why not just make it possible with a single operator.