New behavior of posts under Stories
The posts under stories used to appear in one long list, oldest at the top, newest at the bottom, exactly the same as threads on the boards. I can sort of understand changing that to break them up into pages, but why did you reverse the order so the newest post appears first?
As on the boards, many posts are replies to earlier posts, so it doesn't make sense to start with only the most recent two or three posts. And on any given page, if you want to follow the discussion you have to start at the bottom of the page and work your way up. That's very awkward and counter-intuitive - you read one post from top to bottom, then scan back up to the top of of it and further up to the top of the next post, then read it top to bottom - what a recipe for eyestrain!
I realize that there is a button that lets you reverse the order of posts to show oldest first, but the default appears to be set to "newest first" and even if I change it, every time I open a new topic, or even reopen the same topic a minute later, it's reset to newest first. It's such a pain in the butt that I've pretty much stopped reading Stories.
I apologize if this has been addressed already but a quick search didn't bring up anything.
-
-
I've bumped this old thread because the "new" behavior I described was so annoying that I had stopped reading Stories completely for a long time. Today I checked in on Table Manners and discovered that - mirabile dictu! - they're all on one page again!
Thanks, Chow engineers. But they used to be listed oldest first, which made for logical reading top to bottom, especially as many commenters respond to one another's posts. Now they're backward, and I don't know about everyone else but I find it quite awkward to read a page from bottom to top. Could you possibly add a switch to reverse this? Or is there one already and I'm just not seeing it?
›2 Replies-
-
re: Engineering
I agree on both counts! 1) Thanks for putting all the comments back on one page!
And 2) can we get the choice of ordering oldest or newest first?In fact, given that the regular Chowhound posts are always displayed oldest to newest, it would be seem to make the most sense if that were the default. If we can only have it one way, it would be nice if it were consistent with the rest of the site.
In any case, thanks for getting rid of that annoying paging!
-
-
-
I'm glad I finally found this topic. I hate the new changes too. I've switched over to "oldest first" many times and it seems to default to newest first the next time I go into a story.
I also don't get why when I click "view all" posts, I still don't see all the posts. What's the point of having a view all option if it still picks the newest/oldest based on my settings at that moment?
›9 Replies-
re: queencru
Good point - "view all" should mean view all, not view next ten or whatever.
You know, chow techs - given how few casual chow users even know this board exists, let alone what it's for, I suspect that user dissatisfaction is much more widespread than this brief thread would indicate. Try putting a poll on the Stories page to see what users really think of this new behavior - I'd be willing to bet there are very few people who consider it an improvement over the previous setup.
-
re: BobB
I agree with BobB. On top of all these, there's the fact that you even have to click a button just to read the whole damn answer if it's more than a few lines. What is the purpose of that? Why is that at all helpful to the user? If I want to stop reading someone's post, I'll stop reading; conversely, to collapse the post so that I have to be proactive to continue reading it makes me not want to bother.
-
re: tatamagouche
What's worse is that there is no "expand all" option, so you have to click all 25 comments separately. This is especially frustrating if the site is running slowly or if you're on a slower connection. At least have some preference in the account area where you can set it to show all, oldest to newest permanently, instead of requiring you to do all of this every time you go to a story.
-
re: queencru
This is classic site developer behavior (and I can say that, having been one) - add new features just because your new toy box (software toolkit) allows it, regardless of whether said features are useful, useless, or - as in this case - actually detrimental to the functionality of the site from a real user's perspective.
The new Story setup "does more things" and "looks cooler" - how could anyone not love that?
I always used to drill into my team - if the USERS aren't happy, it ain't working right!
-
-
-
-
It just struck me why it is that this new "functionality" may not seem so egregious to the techs working on it: when you're testing the site from a workstation connected directly to the servers, you click a link and you get a page, immediately. But for those of us who are connected over DSL circuits of varying reliability, you click a link, you get a page - eventually. Sometimes in a second or two, often in ten seconds or more (especially when "adlinks" is slow).
So when I have to click four or five links to get the info I used to get in one, it's a MAJOR disincentive to casually check something out.
Why did you take something that worked perfectly well as it was and turn it into this mess?
-
Hi All,
Thanks for the feedback. We are working on implementing functionality that would save/hold your chosen reading preference for oldest first, or newest first.
This is how it would work; if you are not logged in, we will save it for as long as your visit lasts - until you close the browser or navigate away from the the site. If you are logged in, we will save it to your user preferences so the next time you come back you will see the oldest first (if that is what you chose for your preference).
Our next launch date is still being worked out, but hope this feature helps to make reading the story comments enjoyable again.
›2 Replies-
re: CHOW HQ
Thank YOU for the inside dope! I still don't understand why the change was made at all, though - even with a sticky "show oldest first" you still need to click Read All to see more than the first two or three, and even then you don't really get to read all, you only see the next page, and have to click again to get the following page, and so on. Before, all I had to do to see the most recent posts in a thread I've been following was hit End to go to the bottom of the page.
We don't have this page-by-page behavior on regular threads (where after the first 300 or so it might actually be helpful), why add it to Stories, which rarely have enough responses to become unwieldy on a single page?
Looks to me like a feature that was implemented just because the software allows it, regardless of whether it adds anything to the user experience.
-
-
-






