The discussion centers on improving the visibility and accessibility of Discourse’s Summarize feature, which currently only appears below the OP in topics exceeding 50 replies. Stephen highlights that many users remain unaware of it, suggesting it be added to the topic timeline or progress bar for easier access. orangeandblack5 proposes manual control for OPs/mods to curate summaries, allowing exclusion of non-essential posts — a feature codinghorror notes is partially addressed via staff likes, which heavily weight summary selection. However, orangeandblack5 argues this doesn’t replace intentional curation, especially when staff aren’t active participants. Stephen questions whether this reflects deeper community issues, while orangeandblack5 emphasizes working within existing constraints. sam supports automatically including Staff Notices in summaries, which codinghorror ties to staff participation as a community leadership imperative. Suggestions include onboarding tooltips for first-time users of large topics Stephen and mobile UI placement Ellibereth. codinghorror remains skeptical about the feature’s necessity, advocating instead for preventing megatopics. Hiryuu discovers the feature only appears after 50 posts, confirming its placement under the OP orangeandblack5. Stephen finds value beyond megatopics, even in plugin discussions, and suggests auto-summarizing older topics as an admin tool Stephen, though concerns remain about losing valuable content during pruning. Hiryuu confirms the feature’s behavior post-import, ruling out phpBB-related issues.
I’m constantly surprised by the number of people who aren’t aware of the Summarize button.
Case in point:
To be fair it only appears below the OP of topics which exceed 50 replies, so if you’ve been following the topic since the outset your return visits could well mean you won’t see it pop up.
It would be very useful to have another way to access a summary from the topic timeline and progress bar.
And, while we’re at it, the OP/mods/TL3+ being given the ability to manually include/disinclude posts from the summary would be nice. Especially if they could turn off all non-manually-selected posts for a truly customizable summary for topics that might benefit.
This already happens because staff likes are weighted especially heavily in that summary. So as staff, be sure to like things if you want to affect summarize results.
I find that people are rarely willing to spend the time on manual curation, so as a result it doesn’t happen.
The better advice is to participate in a topic as you normally would and like things that meaningfully contribute to the conversations going on. This benefits everyone.
What if staff aren’t actively participating because almost all of them are focused on a Discourse server running alongside the Discourse instance, and the OPs we have are the kind of people who are extremely likely to take advantage of such a feature?
You make it sound like the community has issues which technology is going to be hard-pressed to remedy. At best it would plastering band-aids over symptoms, right?
That doesn’t sound like a discourse-related problem at all.
Correct, but as a community you have a choice as to whether you visit and post. The payoffs must be outweighing the problems if you’re still compelled to participate.
Anyhow, this is a tangent - as @codinghorror has already pointed out the algorithm which selects posts already includes the opinion of staff as to what should be included. Maybe if you can incline others to try the feature you can garner other feedback which might be useful. My principle concern is with others finding the button.
I hear you, but part of the advice we explicitly give staff is that they need to make participation part of their daily routine too..
Leadership comes from the top. The presence of staff speaks volumes about whether your community is alive and thriving. Don’t just say you believe in this community, demonstrate that through your personal participation and enthusiasm. Lead by example. Reply to questions people have, help your community learn the ropes, gently guide and shape the community as you go.
Ideally access from the topic progress/timeline. Failing that something in the topic controls. It’s a great feature but it’s only visible directly below the OP, so it’s easily forgotten and horribly underused.
That’s not much of an actual proposal. One thing that’s been discussed, but I think would be far too extreme, is for old long topics to be forced into summary mode when you open them.
Reddit actually does something like this as a default for anonymous users.. experiment over there to see what I mean.