Dealing with Queue Rot in VS 3.0
One of the things we're struggling with in the new version, is what to do about the queue.
Our initial idea is to stop automatic SiftBot discards and allow posts to stay in the queue for as long as the member wants. With this persistance though, comes the concept that the longer a post is in the queue, the harder it becomes to escape:
* Under 4 days: 10 votes to publish
* Under 8 days: 15 votes to publish
* Under 12 days: 20 votes to publish
* Under 16 days: 25 votes to publish
* Any older: 30 votes to publish
Queue limits still apply, so if you reach your quota, and you want to post something new, you would have to *discard one of your older sifts that is still in the queue. There would be no SiftBot sweeps to auto-discard older queued videos.
Any thoughts, ideas or alternatives to this system are most welcome.
Our initial idea is to stop automatic SiftBot discards and allow posts to stay in the queue for as long as the member wants. With this persistance though, comes the concept that the longer a post is in the queue, the harder it becomes to escape:
* Under 4 days: 10 votes to publish
* Under 8 days: 15 votes to publish
* Under 12 days: 20 votes to publish
* Under 16 days: 25 votes to publish
* Any older: 30 votes to publish
Queue limits still apply, so if you reach your quota, and you want to post something new, you would have to *discard one of your older sifts that is still in the queue. There would be no SiftBot sweeps to auto-discard older queued videos.
Any thoughts, ideas or alternatives to this system are most welcome.
Load Comments...
Discuss...
Enable JavaScript to submit a comment.