# Will disable\_jump\_reply make a return?

**URL:** https://meta.discourse.org/t/will-disable-jump-reply-make-a-return/116558
**Category:** UX
**Created:** [May 1, 2019, 11:16am UTC](https://meta.discourse.org/t/will-disable-jump-reply-make-a-return/116558 "2019-05-01T11:16:38Z")
**Posts on this page:** 1
**Showing post:** 32

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [May 2, 2019, 3:30am UTC](https://meta.discourse.org/t/will-disable-jump-reply-make-a-return/116558/32 "2019-05-02T03:30:21Z")

</div>

> [@Rock8man](#):
>
> At Qt3, we don’t even have a thread per season on Game of Thrones, we just have one giant thread.

Then that’s the problem you should address. [Megatopics are not a good idea.](https://meta.discourse.org/t/the-megatopic-public-good-or-public-menace/85592)

I’d also add if the topic is really that chatty and random, why would you _care_ if you lose your place in reading it? What difference does it make? The idea that your read position needs to be meticulously and accurately tracked becomes nonsensical at that point. If you don’t read some specific part of mega random rambling chat topic, _nothing of value has been lost._

---

_[View the full topic](https://meta.discourse.org/t/will-disable-jump-reply-make-a-return/116558)._