These are all great usability observations that I have to agree with based on my own personal experience. I don’t have a clue on what’s fixable or where these improvements would fall on the current list of priorities for the team. Not discounting them, Drac, but just being upfront that even obviously good ideas 💡 can be sidelined because of higher priorities. I do know that the team is always interested in better ideas from the community, and as a long-time regular you will notice things that a new user would probably overlook.
Knowing the potential delay in getting an optimum solution implemented for a given issue, I’m always looking for hacks that get me the results I want now. I realize that these hacks have probably annoyed @Factotum in the past because they tend to be of the rubber band and chewing gum variety, but we all come to this with different perspectives on how to continually improve Cake.
One hack I can share for dealing with monster threads like this, which currently is at 400+ posts and counting.
1. Once you’ve read at least one post in a thread, you will see a blue dot 🔵 next to the current count whenever a new comment is posted. You will see these blue dots in the For You, Following, Featured and All timelines.
2. When you see a mega-thread with a blue dot 🔵, indicating there are new posts, click the blue dot.
3. You will be brought to the first post, the posts will become unreadable, and the system will attempt to bring you to the newest posts while showing a blue New posts button in the lower right of your screen.
4. Press the blue new posts button and the new posts will load in a fraction of the time normally required.
Reverse Chronological Order
I hated Twitter whenever they tried to mess with reverse chronological order.
On the Well, the first post is post zero and always stays. Every 100 posts or so they archive them to a new link, which you can access the old posts from, and you then only see post 0 and posts 101-200. In this way, you avoid having to create a new thread or suffering through the inevitable lag time when reading mega-threads.
I would love if Cake could do this since I could then share a link on social media to post 0 and posts 401 to current, of the above coronavirus discussion.