# Near Real-time Discussions (not chat) - Optimizing Features

**URL:** <https://meta.discourse.org/t/near-real-time-discussions-not-chat-optimizing-features/32349>\
**Category:** Feature\
**Tags:** planned\
**Created:** [August 21, 2015, 12:44am UTC](https://meta.discourse.org/t/near-real-time-discussions-not-chat-optimizing-features/32349 "2015-08-21T00:44:16Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![charleswalter](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/charleswalter/32/116433_2.png) [@charleswalter](https://meta.discourse.org/u/charleswalter)\
**Post date:** [August 25, 2015, 3:51pm UTC](https://meta.discourse.org/t/near-real-time-discussions-not-chat-optimizing-features/32349/19 "2015-08-25T15:51:35Z")

</div>

Facebook messages work fine with an input box at the bottom and the conversation continues to scroll if the person you are speaking with is typing. Even old school chat rooms generally had the input box at the bottom with the messages continuing to float up. Perhaps it just becomes a user option on whether the messages should auto-appear or not.

Perhaps it would detect if you are replying at the very bottom of a topic, or inline to a previous reply. If I am replying inline to someone’s reply, then it wouldn’t scroll. If I’m at the very bottom of the thread, then yes, continue loading new replies as they come in.

---

_[View the full topic](https://meta.discourse.org/t/near-real-time-discussions-not-chat-optimizing-features/32349)._