Requested feature overview description.
e621:cheatsheet#Sorting should be updated to include the remaining means of sorting results
Why would it be useful?
I can only guess what some of the newer sort mechanisms are. I'd update the cheatsheet myself if I had access to edit it and knew exactly what they all were, but, some I am absolutely clueless on.
The sorting mechanisms (and my guesses about what they are), are below.
I am guessing some of the information based on the Source Code and what I can figure out from it's contents.
| Exists in Cheatsheet | Missing from Cheatsheet | ||
|---|---|---|---|
| Order | What it does | Order | My Guess What it does |
| order:change | Sorts by last update sequence | order:arttags | Most Artist Tags first |
| comment_bumped | Posts with the newest comments | order:arttags_asc | Least Artist Tags first |
| comment_bumped_asc | Posts that have not been commented on for the longest time | order:change_asc | Sorts by least recent update sequence |
| order:comment_count | Most comments first | order:change_desc | redundant/identical to order:change |
| order:comment_count_asc | Least comments first | order:chartags | Most Character Tags First |
| order:duration | Video duration longest to shortest | order:chartags_asc | Least Character Tags First |
| order:duration_asc | Video duration shortest to longest | order:comment | per source code: Posts last commented at (I can't determine the difference from order:comment_bumped) |
| order:favcount | Most favorites first | order:comment_asc | per source code: Posts that have not been commented at for the longest time (I can't determine the difference from order:comment_bumped_asc) |
| order:favcount_asc | Least favorites first | order:comment_count | Most Comments first (doesn't appear to be an "_asc" equivalent to this order) |
| order:filesize | Largest file size first | order:conttags | Most Contributor Tags first |
| order:filesize_asc | Smallest file size first | order:conttags_asc | Least Contributor Tags first |
| order:id | Oldest to Newest | order:copytags | Most Copyright Tags first |
| order:landscape | Wide and short to tall and thin | order:copytags_asc | Least Copyright Tags first |
| order:portrait | Tall and thin to wide and short | order:duration_desc | redundant/identical to order:duration |
| order:mpixels | Largest resolution first | order:gentags | Most General Tags first |
| order:mpixels_asc | Smallest resolution first | order:gentags_asc | Least General Tags first |
| order:random | Orders posts randomly * | order:id_desc | Newest to Oldest, identical to default sort |
| order:score | Highest score first | order:invtags | Most Invalid Tags first |
| order:score_asc | Lowest score first | order:invtags_asc | Least Invalid Tags first |
| order:tagcount | Most tags first | order:lortags | Most Lore Tags first |
| order:tagcount_asc | Least tags first | order:lortags_asc | Least Lore Tags first |
| order:metatags | Most Meta Tags first | ||
| order:metatags_asc | Least Meta Tags first | ||
| order:note | Posts with the newest notes | ||
| order:note_asc | Posts that have not been noted for the longest time | ||
| order:rank | The Source Code suggests it's meant to show what's trending based on score and age | ||
| order:spectags | Most Species Tags First | ||
| order:spectags_asc | Least Species Tags first | ||
| order:updated | I have no clue beyond the implication it's related to updates. it changes randomly each refresh. Even AI analyzing the Source Code can't give me an answer I understand. | ||
| order:updated_asc | I have no clue beyond the implication it's related to updates. This one remains the same because whatever is affecting it's alternate isn't affecting it. Even AI analyzing the Source Code can't give me an answer I understand. | ||
| order:updated_desc | redundant/identical to order:updated |
What part(s) of the site page(s) are affected?
Posts, search, e621:cheatsheet#Sorting
