Getting the Most Out of Our Discourse Part 2: Some Practical Tips & Tricks for a Smoother Experience

Last time I spoke about the importance of community, of the social side of Discourse, and what we can do to leave it a better place than we found it.

This is a subject I intend returning to but this time I want to focus on more practical usage of the software that can make our experience here easier, quicker, and hopefully more functional.

:hammer_and_wrench: Under-The-Hood

Tip 1:

For topics with more than 20 replies use the Discourse Ctrl + F function to search within a topic.

Why do I love this neat trick? Results will display the post number and user so you can click and quickly jump to what you want.

Example:

Here is one set of results (screenshot only captures the top ones but you get the idea)

Tip 2:

The Ubuntu Support Template and some troubleshooting commands.

We do encourage you to use this but obviously there are no obligations.

Why is it important?

We think it helps keep information more focused and better structured. The faster volunteers can focus in on the issue, the more likely you will get an answer that will help resolve whatever issue you are facing.

Please remember to remove any extranous information not relevant to your post.

For faster and more focused help, provide as much detail as possible (even if you think it might not be relevant, often it will be).

Additional troubleshooting information can also be invaluable.

Here are some common commands to run in the terminal that will help us to help you:

  • slow booting: use systemd-analyze or systemd-analyze blame
  • boot logs: use sudo journalctl -b -p 3 --no-pager
  • your fstab may also often have clues that can help diagonose issues with booting or mounting drives cat /etc/fstab
  • more commands for drives and mounts: sudo blkid sudo fdisk -l lsblk -f
  • general system information, install inxi with sudo apt intall inxi and post the output of inxi -Fxxrz

These are just a few examples, feel free to share your favourite troubleshooting commands.

As always, we kindly ask users to please wrap terminal or script output with code tags for easier reading and analysis.

Highlight the output in your reply and use either </> in the composer or Ctrl + E on the keyboard.

Tip 3:

Be descriptive (no, not like Shakespeare or Chaucer) with your topic titles.

Why is this so important?

Discoverability and Searchability

We want users here and across the internet to find good content quickly and easily. Think of it like a map where only main roads are shown and one where paths, side roads, rivers and other natural obstacles are displayed.

The more keyword rich the title, the better it can be searched for and found by other users.

Instead of “Update Issues,” which is very generic and non-specific consider something like “Update Manager Displays Update Errors.”

Use tags to help enhance discoverability.

Enhances User Engagement

Your fellow users and volunteers are more likely to help when they see an issue being clearly communicated.

We understand not all our users are native English speakers but please make an effort, even using AI tools, to help formulate more descriptive titles.

In the long run, we all benefit from this.

Provides a Better User Experience

Users can quickly scan topic lists and decide which discussions are relevant to them, saving time and reducing frustration. Good titles set accurate expectations for the content inside.

Supports Effective Moderation and Organization

As a volunteer and community moderator, believe me this is also important. The more time moderators can dedicate to guiding users to existing topics and relevant information, the less time we need to spend on “cleaning up” duplicate or irrelevant content.

Again, I want to stress that we all benefit from these small but important details.

See our posting guidelines for more information about titles (amongst other things).

Final Thoughts:

In the first post I quoted from the FAQ and this week I want to close with another important idea.

Improve the Discussion

Help us make this a great place for discussion by always working to improve the discussion in some way, however small. If you are not sure your post adds to the conversation, think over what you want to say and try again later.

The topics discussed here matter to us, and we want you to act as if they matter to you, too. Be respectful of the topics and the people discussing them, even if you disagree with some of what is being said.

One way to improve the discussion is by discovering ones that are already happening. Spend time browsing the topics here before replying or starting your own, and you’ll have a better chance of meeting others who share your interests.

As usual, feel free to post comments, questions, your own tips and tricks.

Don’t forget to watch the tag to stay tuned for the next episode.

Final bonus tip:

The latest upgrade now allows users to save multiple drafts, so go ahead and prepare your replies to the topics that interest you and come back to them when ready.

You can find all your drafts under your user profile.

7 Likes

Thank you for these ideas, Rubi.

My browser (Chrome) uses that function to search within the web page, so it doesn’t work as you might expect in Discourse.

To access this function in Discourse if this applies to you, press the search button (the magnifying glass at the top right of the Discourse page) and then the wording “in this topic” just under the search bar.

To add force to your comments, I often see in forums titles such as, “Help meee!!!” or “Urgent!!!”

I tend to skip those, because I have no idea whether or not I can help with the problem. Extra exclamation marks or question marks make no difference — what makes a difference is, as you say, a succinct description of the problem or question.

I’ll add that expletive-ridden rants generally don’t result in helpful answers, because the poster is so engaged with their own anger that they forget to explain the problem in clear detail. It’s quite humorous that such rants are often (not always) due to either a misunderstanding or a user error.

For how long is a draft saved until it’s deleted?

2 Likes

I believe the default setting for drafts that are unchanged/unedited is to auto-delete them after 180 days of inactivity.

Will follow-up about this and report back here if needs be.

The topic needs to have more than 20 replies (sometimes more than 21-22) and then the Discourse function should override it.

But your suggested method is also possible of course.

This is possible for topics of any length of course.

The thing I liked about the trick I mentioned was to be able to speed up searches in longer topics.

1 Like

Check for apt/deb packages that are not properly fully installed:

dpkg-query -l | grep -P -v '^[hi]i '

List active apt sources & their priorities, as well as any individually-pinned packages:

apt-cache policy
2 Likes

As a moderator in several forums myself, I very much empathise with these comments. Lack of concise information and ranting both frustrate and irritate me equally, and they either get ignored, reprimanded, or in the case of extreme aggressive or abusive rants, banned temporarily or even permanently. The last especially applies in cases where a user argues with staff rather than discussing anything.

1 Like