# Experience from slow hotel connection

**URL:** <https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421>\
**Category:** Feature\
**Created:** [18 Maggio 2016, 3:41am UTC](https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421 "2016-05-18T03:41:04Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [19 Maggio 2016, 12:50pm UTC](https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421/3 "2016-05-19T12:50:28Z")

</div>

I agree we can do a bit better with spotty connections and post staging, it is quite easy to repro, we just add a “sleep 5” into the controller that is saving the post.

When we stage a post I think we have a few options:

- (super duper fancy) work offline, if it was not saved, try to save it again later when online (retry saves)

- (fancy) if it has not been saved after say 1 second, we can display a message “saving post” - or change color to grey.

- (simple) display “staged” content in grey, then turn it to black when the server knows the content was saved. (like lots of chat programs do)

@codinghorror which poison do you prefer here?

Regardless, if staged content does not get through a draft should be there, if that is not the case there is a bug here.

I find the naive (simple) approach to be pretty distracting for day-to-day usage, so would prefer we go with (fancy) at least.

---

_[View the full topic](https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421)._