Agreed (also excepting ninja edits) but it might be really difficult to determine what type of edit is actually meaningful vs. what type of edit is just a typo. Things could be both - a one or two letter change could totally change the semantic meaning of a sentence.
In Fact only new post should be considered as “Activity” and not the post editing.
Nope, I disagree with that. I frequently post something short, then later realize that I should have elaborated further or wish to add another detail or even a question. If the post has already been read, then my edit will likely never be seen. Marking edited posts as a new is an awesome feature.
I’m torn on it. Yes, it goes against everything you know about forum software to date. But I think the good of it outweighs the bad here and that this is really a good thing happening within Discourse instead of an issue.
Remember that Discourses aim is to turn the forum world upside down. They are doing things that go against everything you were accustom to.
We could set a rule of thumb. Like considering the post is new if the diff shows it’s changed by 50% or more.
How about a “this is a minor change” tickbox, like in dokuwiki?
Bad idea. An automatic detection that enables flagging the edit post as new will more often get in your way rather then help.
On the other hand, a detection that disables this feature may work, but it should really only trigger on tiny edits such as typo corrections.
Maybe we need another filter type like active.
Editing posts is something I do almost every post. (I know, I know, “re-read before submitting”).
My “ninja edits” are usually minor typo fixes. But my later edits are to correct mis-information - eg. forgetting a “not” or an “un” changes everything, or as mentioned to add what I consider to be important details I originally overlooked.
I don’t think any amount of computing power can subjectively determine when an edit is a significant change.
IMHO if “edit bumping” is felt to be a problem then post editing should be completely disabled after a few minutes. But then many would simply post the additions/corrections in a follow-up post which would bump the topic anyway, and also increase the post count.
Also it’s worth noting that the topic is only bumped if the last post is edited.
As @mcwumbly noted only edits to the last post cause topic to be bumped. Not edits to any post in the topic
This is by design, feel free to discuss an alternative implementation, but there is no bug here.
We turned on tagging and have been tagging, and moving some threads to new categories. It seems that sometimes the bumped_at is being updated and we are causing a bunch of old threads to re-appear unintentionally. Is there some way to turn off this behavior. Right now, I’m having to manually edit bumped_at in the console which is a painstaking way to organize the forum.
New posts bump the topic, and edits to the last post. If the first post is also the last post…
What I’m asking is, where is the GUI option to change bumped at, similar to
No such feature exists
OK, sorry to nag, but I think some way to bypass (or at least revert) changes to bumped_at would be nice for moderators … I took over an old VB forum with 190k posts, and was in bad shape. It’s been a challenge.
You can bypass the edit bump by doing bulk edits. From the topic list, click the bulk select icon, select the posts you wish to tag (or recategorize) and use the admin wrench. This does not create an edit log, so no bumps.
Awesome thanks @jomaxro!
Does this also apply when closing topics?
I’m considering closing a few thousand old imported topics per this suggestion:
Hoping they won’t all jump to the top of