Bringing up the two day FS/WTB limit again (in General)
I was wondering why the FS/WTB threads close down after two days, and went searching through the forum. Naturally, I found that my question had been answered, except nothing actually happened:
Now that the esteemed NightStrike has the power to do so, what about removing or extending the two day limit, and making all those forgers happy who complain every thread that their previous thread closed?
no, if you want to advertise you have to pay the fee instead of bumping ad infinitum.
July 15 2008 6:53 PM EDT
I thought replying to a FS/WTB thread cost the same as posting a new one..?
Forging threads aren't posted in FS/WTB and they also have a way longer life span...
And a forger can't complain about closed threads because closed forging threads are a sign of true forgers staying true to forging.
I'm going to be vain and put myself as an example here.
I think I'm currently wearing down my 5th forging thread without taking a break from forging. See if you can find somebody else who can say that.
Really, it's something to be proud about rather than complain about.
You're [GB] right, and I can't think of any other reason for this.
Removed FS/WTB autoclose entirely.
July 15 2008 7:40 PM EDT
Fixed better. *smile*
July 15 2008 8:49 PM EDT
July 15 2008 9:25 PM EDT
all hail jon!
July 15 2008 9:34 PM EDT
Thanks Jon! Now, I don't have to read about all those forgers being annoyed about their threads closing!
BTW, you probably want to change the text on the FS/WTB page that still says that the threads close after two days.
July 16 2008 7:50 AM EDT
Well done BSS!!
I'm going to bump this thread again, because it still says
"FS/WTB threads are closed after two days, and deleted after six months."
on the main page of the FS/WTB forum, although that is now not true any more.
This thread is closed to new posts.
However, you are welcome to reference it
from a new thread; link this with the html
<a href="/bboard/q-and-a-fetch-msg.tcl?msg_id=002URY">Bringing up the two day FS/WTB limit again</a>