# Unfortunately I had to pull the plug
**URL:** https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508
**Category:** Community Building
**Created:** [5월 12, 2019, 1:41오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508 "2019-05-12T13:41:22Z")
**Posts on this page:** 20
**Page:** 2
### Author:  [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)
#### Post date: [5월 12, 2019, 8:21오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/22 "2019-05-12T20:21:54Z")
You can do non-onebox links like this
[https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/1](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/1)
[https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/2](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/2)
etc
But yeah. If an OP could be tagged as “contents list” and auto generate that stuff, it might be useful.
---
### Author:  [@orangeandblack5](https://meta.discourse.org/u/orangeandblack5)
#### Post date: [5월 12, 2019, 8:21오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/23 "2019-05-12T20:21:59Z")
It’s moreso that only people _looking_ to read the types of threads we have that get that big would ever put in the effort to do so.
---
### Author:  [@orangeandblack5](https://meta.discourse.org/u/orangeandblack5)
#### Post date: [5월 12, 2019, 8:22오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/24 "2019-05-12T20:22:43Z")
The problem with that is it _only_ works if you’re going for breaks based on post count, not actual post content.
---
### Author:  [@DNSTARS](https://meta.discourse.org/u/DNSTARS)
#### Post date: [5월 12, 2019, 8:27오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/25 "2019-05-12T20:27:29Z")
How does that differ from having page numbers though? If there’s 50 posts per page over 10k then as you’ve said you have 200 references that don’t go to anywhere contextual. If the issue in fact is “huge unwieldy topics” then someone who cares enough about the content needs to segment it and if no one cares enough to make it legible throw it away.
It would be nice to have a means to do a TOC that spanned into other people’s posts down the navigation line though, that would be epic.
---
### Author:  [@orangeandblack5](https://meta.discourse.org/u/orangeandblack5)
#### Post date: [5월 12, 2019, 8:28오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/26 "2019-05-12T20:28:31Z")
The difference is you don’t have 10,000 posts on one page slowing things down and crashing your browser, and you can point people to a specific page.
---
### Author:  [@orangeandblack5](https://meta.discourse.org/u/orangeandblack5)
#### Post date: [5월 12, 2019, 8:29오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/27 "2019-05-12T20:29:57Z")
At the very least, the option to enable pages on some level would be extremely welcome.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [5월 12, 2019, 8:30오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/28 "2019-05-12T20:30:04Z")
Thanks for the detailed report! Sorry things did not work out.
As for the 502 errors, it sounds like the server was under-powered for the database size? How many posts, topics and users were there, and what were the cpu, ram, and disk stats of your server? You’d also want to use a CDN for a large site to reduce load.
---
### Author:  [@DNSTARS](https://meta.discourse.org/u/DNSTARS)
#### Post date: [5월 12, 2019, 8:32오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/29 "2019-05-12T20:32:31Z")
I hear you, i’m not fighting your desires but for the discourse staff etc imo a means to somehow integrate staff/High trust controlled bookmarks next to the nav timeline would be baller.
---
### Author:  [@orangeandblack5](https://meta.discourse.org/u/orangeandblack5)
#### Post date: [5월 12, 2019, 8:34오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/30 "2019-05-12T20:34:52Z")
I agree that would work, which is why I have brought it up before and again here.
There are pretty much the two options discussed above for minimal-work management of megathreads - pages or direct timeline control. Being able to push a button to mark posts directly on the timeline scroll bar thingy and attach them to the bottom of the OP would be very welcome. So would the ability to enable pages. Both in combination would be amazing. But right now, neither exist, and pages seem easier to implement, are more familiar, and could also benefit from future timeline improvements.
---
### Author:  [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)
#### Post date: [5월 12, 2019, 8:36오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/31 "2019-05-12T20:36:40Z")
> [@DNSTARS](#):
>
> It would be nice to have a means to do a TOC that spanned into other people’s posts down the navigation line though, that would be epic.
> [@DNSTARS](#):
>
> imo a means to somehow integrate staff controlled bookmarks next to the nav timeline would be baller.
One thing I’ve seen on a [non-Discourse forum](http://resetera.com) is the ability for staff or approved users to mark posts as important.
When I return to a discussion thread at a later date, the important posts that have been made since I last visited are neatly presented to me just above the point I jumped back to. Very useful.
In Discourse that could be on the timeline in some way as well as going into the TOC OP.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [5월 12, 2019, 8:39오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/32 "2019-05-12T20:39:11Z")
That’s the question, right? Have you looked into how the feature works?
---
### Author:  [@orangeandblack5](https://meta.discourse.org/u/orangeandblack5)
#### Post date: [5월 12, 2019, 8:40오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/33 "2019-05-12T20:40:47Z")
Honestly no, I have not.
---
### Author:  [@ChrisBeach](https://meta.discourse.org/u/ChrisBeach)
#### Post date: [5월 12, 2019, 8:40오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/34 "2019-05-12T20:40:57Z")
> [@orangeandblack5](#):
>
> Pages would be a welcome feature, yet as of last time I checked in the devs seem staunchly against it.
I cannot stand paging. It’s so 1990. So PHPBB 😣
Topics of 20,000 posts are a big ball-ache for members of online communities IMO. If a forum has developed a topic with 20,000 posts, it means the forum has become a chatroom. And that’s not good, given that forums are intended for long-term, organised content, as opposed to transient feed-like chatter.
Discourse has the “summarise” button to avoid users having to wade through every post of a mega-topics, and Discourse allows sophisticated moderation. There are plenty of ways to avoid mega-topics, and it sometimes takes a firm hand by the admins in setting out the goals of the forum, and explaining to users the benefits of well-organised content. It’s worth it, though.
---
### Author:  [@orangeandblack5](https://meta.discourse.org/u/orangeandblack5)
#### Post date: [5월 12, 2019, 8:42오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/35 "2019-05-12T20:42:35Z")
> [@ChrisBeach](#):
>
> Topics of 20,000 posts are a big ball-ache for members of online communities IMO. If a forum has developed a topic with 20,000 posts, it means the forum has become a chatroom. And that’s not good, given that forum conversation should be well-organised for long-term usage of content, as opposed to transient feed-like chatter.
None of our massive threads are chatrooms.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [5월 12, 2019, 8:44오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/36 "2019-05-12T20:44:48Z")
Here’s a good example, [this topic has 1700 posts](https://us.forums.blizzard.com/en/wow/t/stop-throwing-gear-around-and-rewarding-mindless-play/169732/).
Summarized it’s reduced to the [100 replies based on the underlying interaction stats which Discourse collects](https://us.forums.blizzard.com/en/wow/t/stop-throwing-gear-around-and-rewarding-mindless-play/169732/?filter=summary).
It’s incredibly effective at cutting through the cruft.
The tools already exist to make consuming or managing large topics quite straightforward. Not even trying the feature undermines any criticisms or calls for alternatives.
OTOH, if you try it and dislike it then there’s an opportunity to provide feedback on posts which were picked up or missed. You can help make the feature more useful and relevant to _everyone._
> [@orangeandblack5](#):
>
> None of our massive threads are chatrooms.
_Maybe_. Regardless, no topic **needs** to be 20,000 responses either. Creating serialised topics or just daily topics achieves the same thing, and Discourse being Discourse a bidirectional link between them is maintained when the new topic links back to the old.
Heck, if you’re really determined you can automate that process, but it really shouldn’t be necessary.
---
### Author:  [@gingerbeardman](https://meta.discourse.org/u/gingerbeardman)
#### Post date: [5월 12, 2019, 8:47오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/37 "2019-05-12T20:47:45Z")
Thanks for that. I wasn’t aware of Summarise.
---
### Author:  [@orangeandblack5](https://meta.discourse.org/u/orangeandblack5)
#### Post date: [5월 12, 2019, 8:49오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/38 "2019-05-12T20:49:15Z")
> [@Stephen](#):
>
> The tools already exist to make consuming or managing large topics quite straightforward. Not even trying the feature undermines any criticisms or calls for alternatives.
>
> OTOH, if you try it and dislike it then there’s an opportunity to provide feedback on posts which were picked up or missed. You can help make the feature more useful and relevant to _everyone._
While I do entirely agree with this point, and will be doing such moving forwards, I think the fact that I’ve been using Discourse on the daily for two years now and never once knew what exactly this does speaks to a poor explanation of the feature next to the button to activate it. It sounds like you would just offer to type up a summary. 🤷♂️
---
### Author:  [@orangeandblack5](https://meta.discourse.org/u/orangeandblack5)
#### Post date: [5월 12, 2019, 8:51오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/39 "2019-05-12T20:51:47Z")
My immediate reaction to trying it out is that the OP/mods/TL3+ should be able to add posts manually.
They should also not count towards the 100 auto-generated posts - that’s still less than 1% of all posts in a 10,000+ post topic, a fine number but still a fraction of the total info.
---
### Author:  [@Merlls\_Rizzini](https://meta.discourse.org/u/Merlls_Rizzini)
#### Post date: [5월 12, 2019, 9:03오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/40 "2019-05-12T21:03:04Z")
> [@eesty](#):
>
> One-click quoting, something which every other platform can do, is three-click process in Discourse. My users read a post, then want to have a “quote” button that loads the quote in a composer, simple. Yes Discourse can “quote” but it takes a few clicks and my users did NOT like this at all.
Same problem with me. Its kinda confuse that you need to click in button inside editor.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [5월 12, 2019, 9:07오후 UTC](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508/41 "2019-05-12T21:07:21Z")
> [@Merlls\_Rizzini](#):
>
> Same problem with me. Its kinda confuse that you need to click in button inside editor.
Why? You can just select text from within a post, then click the ‘quote’ button which appears next to the selection:
It will create a new reply including the quoted text. That’s how I responded to you.
[이전 페이지](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508.md?page=1)
[다음 페이지](https://meta.discourse.org/t/unfortunately-i-had-to-pull-the-plug/117508.md?page=3)