← Back to post

Edit history

Most recent

To bring another data point to the issue the OP is bringing (personally I don't use the "Hot" order, I'm accustomed with using chronological ordering; just helping the OP with additional data point from a slightly older account to the glitch they're observing): to me, "Hot" correctly sorts the entries by the number of upvotes (edit: and it also takes into account the amount of replies)... Except it only does so for the items that were fetched for the current scrolling page, which is 15 entries. When the user scrolls down to the end of the list, Catodon fetches another 15 entries, but these will be sorted independently from the previous entries, so it gets a stairway-like effect when it comes to upvote counting across entries.

It seems to be just the "hot" order, though, and maybe the "Active" (I didn't test the "Active", it likely experiences the same phenomenon given it probably does chunked fetching too). The "new" sorting order is working as intended.

Edited to correct my oversimplification of "hot = upvotes" and to bring additional screenshot from the "staircase effect".

Screenshot of forums, sorted by new, correctly displaying entries chronologically for the forums I follow (mostly entries from Superb Owl).Screenshot of the same forums, now sorted by hot, seemingly displaying entries by the amount of upvotes, except it's missing some recent Superb Owl threads with more upvotes.Additional screenshot of me scrolling further down into the list sorted by "hot". Notice how the "buffy will be eating well..." post with 166 upvotes appears after a "é hoje, rabisquarta de..." with no upvotes whatsoever.
Edited

To bring another data point to the issue the OP is bringing (personally I don't use the "Hot" order, I'm accustomed with using chronological ordering; just helping the OP with additional data point from a slightly older account to the glitch they're observing): to me, "Hot" correctly sorts the entries by the number of upvotes (edit: and it also takes into account the amount of replies)... Except it only does so for the items that were fetched for the current scrolling page, which is 15 entries. When the user scrolls down to the end of the list, Catodon fetches another 15 entries, but these will be sorted independently from the previous entries, so it gets a stairway-like effect when it comes to upvote counting across entries.

It seems to be just the "hot" order, though, and maybe the "Active" (I didn't test the "Active", it likely experiences the same phenomenon given it probably does chunked fetching too). The "new" sorting order is working as intended.

Edited to correct my oversimplification of "hot = upvotes" and to bring additional screenshot from the "staircase effect".

Original

To bring another data point to the issue the OP is bringing (personally I don't use the "Hot" order, I'm accustomed with using chronological ordering; just helping the OP with additional data point from a slightly older account to the glitch they're observing): to me, "Hot" correctly sorts the entries by the number of upvotes... Except it only does so for the items that were fetched for the current scrolling page, which is 15 entries. When the user scrolls down to the end of the list, Catodon fetches another 15 entries, but these will be sorted independently from the previous entries, so it gets a stairway-like effect when it comes to upvote counting across entries.

It seems to be just the "hot" order, though, and maybe the "Active" (I didn't test the "Active", it likely experiences the same phenomenon given it probably does chunked fetching too). The "new" sorting order is working as intended.