Language…
11 users online:  AmperSam, CroNo, Darolac, Green, Guido_Keller, Isikoro, JezJitzu,  Linkdeadx2, Sweetdude, timothy726, tOaO - Guests: 269 - Bots: 386
Users: 64,795 (2,377 active)
Latest user: mathew

#39: Bump warning message in old threads

Link Thread Closed

New FeatureResolved

Just for the sake of creating an issue and trying out the system. Not an urgent request by any means.

I think it'd be useful if the reply form in old threads had a bump warning. Something like a noticeable text box saying "you're about to bump this thread, consider making your own instead" near the form would do.

(the questions is how to define "old". Ideally you'd need to factor in the sticky status, the position in the thread list, the age of the last reply, and the tutorial status.)


 
This issue has been part of our internal todo list for a strikingly long time. I even coded an implementation for it back in June, but the pull request has remained stagnant for quite some time. This is a result of multiple factors. The main one is that our rules regarding bumped threads are not as strict as they used to be, along with one of the reasons you mentioned - some forums (like tutorial forums) may need stricter or looser thresholds.

If we manage to come to a conclusion about our exact bumping rules and the use cases of the warning, implementation of this issue should be quite fast because most of the code for it already exists (not accounting the merge conflicts which have appeared since it was made).
I think it's easy; just make it a message saying "hey, this thread hasn't been posted in in over a month, so make sure your post is really warranted, maybe make a new thread instead". Plead for common sense, which is pretty much what is enforced by moderation.
It's easily the best thing I've done
So why the empty numb?
Still no decisive response from the forum team, so I went ahead and implemented this. The threshold is separately configurable for each forum and no forums currently use the feature, so you won't immediately see any changes. Anyhow, the coding side of this done - unless WhiteYoshiEgg voices a complaint about the implementation, the issue will be closed in the next few days.

New FeatureResolved

Link Thread Closed