Posting without bumping topic?

AI-generated summary

The discussion revolves around the idea of posting without bumping a topic to the top. Sujan initiated the conversation, stating that they sometimes want to post a message that is relevant to the thread but not to the entire forum. david replied that there isn’t a way to post without bumping the topic, suggesting the use of the ‘like’ button instead. However, Sujan felt that liking is insufficient, especially in cases where there are multiple posts ping-ponging a problem.

Mittineague suggested sending personalized messages, while HAWK mentioned that editing the timestamp can be a manual workaround. anon61128213 proposed giving moderators the ability to edit timestamps to “unbump” topics, which HAWK thought was a reasonable idea.

The conversation led to the suggestion of implementing a “do not bump” feature, with erlend_sh mentioning that it would require developer input. tgxworld revealed that the server-side logic for this feature already exists, and erlend_sh proposed exposing the “do not bump” settings in the composer cog.

Various use cases were shared, including moderation tasks and adding solutions to old Q&A posts. codinghorror supported the feature as a staff option, and habeycole suggested a topic setting for admins and moderators. The feature has now been implemented as a staff-only feature, as announced by riking.

Sometimes I want to write “Good job”, “Great you found the solution” or something that is relevant to all the people in the thread and especially the last poster, but not relevant for all the people in the forum in general.

Is there a way to post something without bumping the whole topic to the top?

There isn’t a way to post without bumping the topic. For the cases you describe, maybe you could just use the ‘like’ button?

8개의 좋아요

Liking is much less part of a “conversation”.

The usecase I have here is often >10 post ping pong debugging a problem, suggestion solutions etc. Only reacting with a like feels.. insufficient.

(Of course I totally get that this is a special use case and maybe also not the intended way to use Discourse. Was still hoping this was possible)

1개의 좋아요

You could send them a personalized message.

I think the members getting something like
“Hi memberABC
Thanks for contributing to the discussion, blah, blah schmooze”
would make them feel appreciated.

3개의 좋아요

You can edit the timestamp (so it drops back down the feed) for a manual workaround.

Is it possible to give moderators the ability to edit timestamps in order to “unbump” topics?

Usecase:

I’m editing the “this topic was closed”-post of an old topic to add a link to a more recent topic (so people who find the old topic through the search function know where to go) but don’t want the old topic to get bumped.
This happens quite a lot and I can’t always ask an admin to jump in. Usually I just end up not editing the post and hope people find a recent topic by themselves.

3개의 좋아요

I can’t think of a solid reason why not. @erlend_sh – thoughts?

See also:

https://meta.discourse.org/t/possible-to-edit-timestamp-of-comment-s/73493?u=mcwumbly

2개의 좋아요

There could be a lot of subtle complexity to this so it requires dev input. @tgxworld did you have a cursory look at how difficult this would be to do?

Seems to me like the OP’s idea of having a “do not bump” checkbox might be easier to implement, but even that is a tough sell as far as prioritization goes.

Usually bumping is not nearly as disruptive as one would think. We’ve gotten pretty good at glancing over things we don’t care about :wink:

5개의 좋아요

The server side logic has already been implemented in the past

Difficulty on the client side will depend on where we expose the “do no bump” settings.

5개의 좋아요

I’m interested in this feature for a different use case. Sometimes I edit people’s topics to change their category, add tags, etc. If no one has replied yet, this bumps the topic, which I dislike as there’s no new information essentially.

3개의 좋아요

Probably the composer cog:
50

“Hide details” and “Blur spoiler” are probably even more obscure use cases than “do not bump”.

4개의 좋아요

We’ve had issues with this on our forum as well WRT moderation. There are a number of things we want to do that are blocked because we don’t want to spam Latest:

  • Go through bug reports and close all solved issues that never previously closed
  • Mass-fix miscategorization of feature requests / bug reports when we still allowed users to post in top-level category
  • Add solutions to a bunch of our old Q/A posts to improve value of search
9개의 좋아요

I do support this as a staff option.

8개의 좋아요

안녕하세요 @codinghorror, 이 기능이 아직 구현되었나요?

다른 사용 사례에서는 관리자 및 모더레이터에게 적용할 수 있는 ‘도트 넘버(bump) 금지’ 기능을 추가할 수 있는 주제 설정이 있는 것이 가장 적절하다고 생각합니다.

예를 들어, 제 커뮤니티에서는 사용자가 흥미로워할 만한 흥미로운 주제에 featured(추천) 태그를 붙여서 이동시킵니다. 동시에, 추천 주제에 새로운 게시물이 추가될 때마다 해당 주제가 위로 올라와 순서가 바뀌는 것을 원하지 않습니다. 예를 들어, 12월에 경기가 열렸을 때(그리고 관련이 있을 때) featured 태그가 붙어 있던 첼시 대 토트넘 스레드가, 누군가 오늘 그 주제에 답글을 달거나 다른 게시물을 추가하면 관련성이 없어지는데, 그렇게 되면 해당 주제가 featured 태그/스레드 목록의 맨 위로 올라오게 됩니다. 제 의도를 이해해 주셨으면 좋겠습니다.

이 기능은 이제 스태프 전용으로 구현되었습니다:

2개의 좋아요

위 내용을 참고해 주세요. 운이 좋네요, 해당 기능이 이미 존재합니다! :wink:

2개의 좋아요

아, 정말 예쁘네요! 알려주셔서 감사합니다! :wink:

1개의 좋아요