Thread: Bumping old threads.

  1. #1
    Officially An Architect brewbuck's Avatar
    Join Date
    Mar 2007
    Location
    Portland, OR
    Posts
    7,396

    Bumping old threads.

    If there's a "policy" that we should not bump old threads, then why are we able to do it? If the moderators don't want threads older than, say, 10 days, to be bumped... Why is the thread still available for posting?

    It seems borderline rude to yell at people for bumping threads when the threads are right there and open for posting.
    Code:
    //try
    //{
    	if (a) do { f( b); } while(1);
    	else   do { f(!b); } while(1);
    //}

  2. #2
    Registered User VirtualAce's Avatar
    Join Date
    Aug 2001
    Posts
    9,607
    Not sure. Can this be automated by the board?

  3. #3
    Officially An Architect brewbuck's Avatar
    Join Date
    Mar 2007
    Location
    Portland, OR
    Posts
    7,396
    Quote Originally Posted by Bubba View Post
    Not sure. Can this be automated by the board?
    Seems like the kind of feature that probably already exists... "Close thread after X days of no activity"
    Code:
    //try
    //{
    	if (a) do { f( b); } while(1);
    	else   do { f(!b); } while(1);
    //}

  4. #4
    Devil's Advocate SlyMaelstrom's Avatar
    Join Date
    May 2004
    Location
    Out of scope
    Posts
    4,079
    I'm not sure about vBulletin, but from my experience as administrator at some IPB boards, they allowed configuration to automatically close threads after an N number of days of inactivity. If I recall the details, however, inactivity referred to day without any views rather than days without any new posts. I could be mistaken on the details though and I have no idea if vBulletin has the same option.

    We used it once but ultimately found that the number of complaints from topic starters PMing us asking "WHY WAS MY TOPIC CLOSED!?!" (despite the fact that the rule was posted in red and in bold in every single "Read this before posting" sticky on the forum) was too overwhelming and removed it.

    That said... now that I'm thinking back, I believe the feature might have been a third-party hack rather than an official feature of IPB.
    Sent from my iPadŽ

  5. #5
    Officially An Architect brewbuck's Avatar
    Join Date
    Mar 2007
    Location
    Portland, OR
    Posts
    7,396
    Quote Originally Posted by SlyMaelstrom View Post
    We used it once but ultimately found that the number of complaints from topic starters PMing us asking "WHY WAS MY TOPIC CLOSED!?!" (despite the fact that the rule was posted in red and in bold in every single "Read this before posting" sticky on the forum) was too overwhelming and removed it.
    Back in my days of admining a board (too long ago to bother mentioning), one thing I discovered is that although people whine whenever you moderate them with automated policies, they whine even WORSE when you do it by hand.

    At least with software, there is no room to argue that somebody was being unfair. The same program makes the same decision every time, regardless of who you are.
    Code:
    //try
    //{
    	if (a) do { f( b); } while(1);
    	else   do { f(!b); } while(1);
    //}

  6. #6
    Devil's Advocate SlyMaelstrom's Avatar
    Join Date
    May 2004
    Location
    Out of scope
    Posts
    4,079
    Quote Originally Posted by brewbuck View Post
    Back in my days of admining a board (too long ago to bother mentioning), one thing I discovered is that although people whine whenever you moderate them with automated policies, they whine even WORSE when you do it by hand.
    I would say that'd be true if we actually bothered to manually close every single thread after 10 days of inactivity. However, we didn't and the complaints were significantly less (actually near non-existent on that particular issue). This is due to the fact that people tend to believe that their topic was closed due to their own fault, especially when they don't see any agitating replies. So what you'd get is hundreds of PMs from topic-starters of threads that were never going to be bumped in the first place asking what they did that got it closed because generally nobody looks at the way a topic is evolving more than the person who started it.
    Sent from my iPadŽ

  7. #7
    Reverse Engineer maxorator's Avatar
    Join Date
    Aug 2005
    Location
    Estonia
    Posts
    2,318
    What's the hype against bumping old threads anyway? Who cares?

    I always notice this paradox - people advise you to use search to find similar threads so you wouldn't make a new one, but you can't post in them because of the bumping thing and you still have to make a new thread. Damned if you do, damned if you don't.
    "The Internet treats censorship as damage and routes around it." - John Gilmore

  8. #8
    C++ Witch laserlight's Avatar
    Join Date
    Oct 2003
    Location
    Singapore
    Posts
    28,413
    Quote Originally Posted by maxorator
    I always notice this paradox - people advise you to use search to find similar threads so you wouldn't make a new one, but you can't post in them because of the bumping thing and you still have to make a new thread.
    The idea is that if you found your answer then you don't need to start a new thread in the first place. If you have not found your answer then you should start a new thread since whatever thread you post in is unlikely to be relevant anyway, or if it is relevant, then whatever answers are given to your question would then be found by a future search on the same topic.

    Along those lines, I would tolerate a situation where someone digs up an old thread and corrects a serious mistake in the given solution.
    Quote Originally Posted by Bjarne Stroustrup (2000-10-14)
    I get maybe two dozen requests for help with some sort of programming or design problem every day. Most have more sense than to send me hundreds of lines of code. If they do, I ask them to find the smallest example that exhibits the problem and send me that. Mostly, they then find the error themselves. "Finding the smallest program that demonstrates the error" is a powerful debugging tool.
    Look up a C++ Reference and learn How To Ask Questions The Smart Way

  9. #9
    Complete Beginner
    Join Date
    Feb 2009
    Posts
    312
    Quote Originally Posted by laserlight View Post
    Along those lines, I would tolerate a situation where someone digs up an old thread and corrects a serious mistake in the given solution.
    I don't like the idea of automatically closing threads, for the same reason. Additionally, not everyone may have enough free time and/or constant access to the web; in a thread, I'd rather see an elaborate posting every two weeks than some guy constantly posting without thinking in 5 minute intervals. Besides, bumping old threads doesn't seem to be a big issue anyway. If we'd really stick to the forum guidelines, we could immediately answer every second thread with "use the fine search function".

    Greets,
    Philip
    All things begin as source code.
    Source code begins with an empty file.
    -- Tao Te Chip

  10. #10
    spurious conceit MK27's Avatar
    Join Date
    Jul 2008
    Location
    segmentation fault
    Posts
    8,300
    ditto ditto ditto

    I think old threads should be left open. No one will get killed.
    C programming resources:
    GNU C Function and Macro Index -- glibc reference manual
    The C Book -- nice online learner guide
    Current ISO draft standard
    CCAN -- new CPAN like open source library repository
    3 (different) GNU debugger tutorials: #1 -- #2 -- #3
    cpwiki -- our wiki on sourceforge

  11. #11
    Malum in se abachler's Avatar
    Join Date
    Apr 2007
    Posts
    3,195
    Quote Originally Posted by brewbuck View Post
    Back in my days of admining a board (too long ago to bother mentioning), one thing I discovered is that although people whine whenever you moderate them with automated policies, they whine even WORSE when you do it by hand.

    At least with software, there is no room to argue that somebody was being unfair. The same program makes the same decision every time, regardless of who you are.
    A rule of 90 days with no posts would eliminate 99% of the problem bumps and you should probably just ban anyone that whines about a thread that old getting closed.

  12. #12
    Registered User
    Join Date
    Oct 2001
    Posts
    2,129
    I prefer leaving threads open so you can post "continued in another thread" posts.

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Replies: 5
    Last Post: 10-17-2008, 11:28 AM
  2. problem with win32 threads
    By pdmarshall in forum C++ Programming
    Replies: 6
    Last Post: 07-29-2004, 02:39 PM
  3. bumping threads
    By creeping_death in forum Windows Programming
    Replies: 1
    Last Post: 08-27-2003, 02:50 AM
  4. About bumping one's own threads..
    By Cobras2 in forum A Brief History of Cprogramming.com
    Replies: 3
    Last Post: 03-14-2002, 10:08 AM