After thinking about this some more, there may another consequence to a "thread moved" reply and a potential drawback.
Again, for clarity, the problem exists only for threads that (a) need to be moved to another forum and (b) have zero replies at the time the thread is moved.
If the moderator moves the thread and leaves a reply saying "thread moved => greater exposure deserved," then the thread is taken off the zero reply list.
To my knowledge, this has the following effects:
- The thread will not receive the benefit of zero-reply list jockeys
- The thread will not receive the benefit of LQ zero-reply drives
- The thread will not receive the automatic re-bump in the forum before scrolling off to page 2
So, the suggestion I made (and followed up by k3lt01) is to edit the original post (rather than reply) or send a PM.
In the interest of being objective, I did think of a drawback. It's easiest to explain with an example:
- User accidentally posts a "Linux Newbie" question in a low-traffic forum (e.g. "Introductions") around 2:00 AM Central Time (i.e. whatever time daily LQ traffic drops off)
- User's post is not reported or otherwise attracts the attention of a moderator until seven hours later
- The thread is moved to "Linux Newbie" and the post is edited to avoid taking the thread off the zero-reply list.
The consequence of this scenario is: unless the thread's posting time is reset to the time of the move, then the thread might show up halfway down the Newbie forum's thread list. In a worst-case scenario, imagine there are enough new threads in the Newbie forum that the moved thread might end up on page 2--maybe causing a problem for the zero-reply re-bump logic.
In the above paragraph, I say "might show up" because I don't know how LQ's code handles thread moves. Threads seem to be sorted in reverse-chronological order based on last activity--which is where my example stems from. But I know enough to realize that just because it
looks like it's ordered that way does not mean that it
must be ordered that way.
EDIT:
For clarity, when I mention the "drawback" above, it is in reference to implementing a no-reply mechanism when moving a thread (i.e. the very thing I am suggesting). I'm just trying to be upfront that a no-reply mechanism may carry with it some other technical issues to consider.