We're discussing this one here at Ryver HQ, but I don't think we're quite ready to concede that the best course of action is to keep trying forever. Right now, we will try for several minutes, at which point, it seems very common in other services we use as well, to alert the user that something is wrong.

One reason is that the client at some point is going to have missed so much potential incoming content that it really needs to be completely refreshed/reloaded anyway.

We are building a Task Management feature that will allow you to create tasks from posts, comments or chat messages (or just create tasks on their own). Each forum and team will have its own Tasks tab. You can choose to keep the tasks in a simple list format or add categories and create a "Task Board" (like Trello).

Additionally, we plan to add support for creating simple lists using markdown.

We really like this concept. A timeline for adding anonymous access support is a little fuzzy right now though. This does tie into another request, which is to support a "read only" user type. If we can get that implemented, it would pave the way for anonymous access in specified forums/teams.

Thank you for this feedback! We have an upcoming effort to completely revisit our navigation bar, and you have covered some of the "ToDos" on that list. I'll add your full suggestion to our project task list for this feature.

This is a pretty cool idea. If we allowed you to select an existing Post, perhaps it could add the chat transcript as a comment on that post?

This is not against our philosophy! We are in the process of changing some things around architecturally so that we can support a back option within the client, and if you are running Ryver in your browser, could even use the browser back button.

Note that for links to posts, we DO in theory support your getting "back" to where you were, because we slide in the post and allow you to close it and still be in your chat room. The exception to that is if you have an in-progress message. In that case, the client will open the linked post in its own tab to "protect" any in-progress work. Though...I think we might be able to do something about that scenario as well.

Thanks for this feedback, Josh. Interestingly, the OPEN FORUMS and PRIVATE TEAMS used to work exactly as you describe. Clicking on them would slide them in, and you needed to explicitly choose to pin them.

There were a couple of different problems this caused. First, people were getting confused by the fact that they had previously accessed a Team or Forum, but now it was "gone" (because it wasn't in their nav bar). And second, somebody would end up with a team/forum in two places. One in the pinned tabs area, and another slid in on the list view. They would start a comment or chat message in one place, and then later find their way to the other one and think we lost their in-progress message.

Ultimately, it seemed we were losing more people to confusion than we were helping people by giving them that flexibility.

I'm curious...another request we have that has been up-voted quite a bit is to facilitate "groups" in the nav bar, where you could group together teams and forums, and collapse/expand those groups. Would having that option lessen your need/desire to slide open the teams and forums from the list view?

Thank you for this feedback. We have a few things in the works for this! We are within days of testing a new user onboarding flow where Eddy Bot greets the user, asks them to type a chat message, and then tells them about OPEN FORUMS, PRIVATE TEAMS and DMs.

In the first pass, there won't be overlays, but we'll try to keep the info short and clear. Perhaps with links they can click to take them to the Forums/Teams lists. We do plan to do a "phase 2" that introduces overlays for those very basic concepts.

We are also talking about having Eddy Bot wait 24 hours, then come back and introduce the user to the concept of "Posts".

Hi Austin - When you select a user from the navigation bar and it takes you to the chat room, it should definitely be putting the focus in the chat input box.

Or are you talking about when you are trying to @mention somebody and you use your mouse to select them from the auto-complete list? We did have an issue with that which was fixed in chat with the update we pushed out two days ago.

But that issue does still exist if you do @mention/auto-complete in a comment on a post. It retains focus if you use your keyboard to select the person, but if you use your mouse, the Comment input box loses focus. We're still trying to come up with a fix for that one.