Originally posted by DotComGod
ok, relooking at it now.
-=DCG=-
Thanks DCG!
I am heading over to VB hacks archives to see if there is somethere there that we could use to deal with Bumps in a better way.
It would be real nice if those that would like to have this done better also invest some time to dig through to VB archives to explore better ways to implement this.
On a second thought, there might be a way to deal with this in a completely different way.
How about extending DNF AUP to include a statement on what wil be Acceptable and Unacceptable Bump behavior, and then enforcing the revised AUP.
For example, what if DNF were to constitute a fine (say, DNF$25) per incident for repeat Bump offenders. Don't shoot me, I am just thinking aloud!
I see a genuine need for people to bump a thread to reflect price changes, bid updates, etc. It may be a real bad idea to ban those. However, if DNF AUP were to clearly spell out acceptable and unacceptable bumps, those who willingly engage in unsafe Bump practices, pay DNF$25/incident to a common DNFBucks kitty or something. If everyone want me to safe-guard those DNFbucks, I will be glad to watch-dog your kitty!
I promise, I will be a good Watch-Dog! By the end of the year, we may have enough DNFBucks in there for a great New Year Eve Party!
I really think a procedural solutions might be better in this case than a programmatic fix. Just like every social problem does not call for a government pork-barrel program, every policy related issues does not have to call for a extreme programming marathon.
Ok, everybody, let's pull away from the keyboard for one minute and think about this... Ok, I am back at my keyboard back now.
JMHO, trying to think out side the box...