Why can we not mark a pqueue as dead?

I like to browse through VideoSift to see all kinds of new videos. Mostly, this is not just what is on the front page, but also videos sitting in people's pqueues and other older videos that mostly everyone has long forgotten about.

So, occasionally I come across a pqueue video that is dead. Normally I would just nudge the submitter by posting a comment on their profile that lets them know... however a lot of times these users have disappeared into the Ethernet never to return.

This sucks because this video is trapped in limbo. I can't fix it by marking it dead and letting it get to the dead pool to fix, nor can I submit it myself, as per the sift guidelines (Chapter 30, Section 5 of the FAQ states "Duplicates will be * discarded. A duplicate video is one which contains content already on VideoSift in a published, queued, personal queued, or dead video submission.")

So in conclusion, I would like to be able to mark pqueues as dead too.

As usual, thanks for tuning in.
alien_concept says...

I totally think the same thing, there's a vid in someone's pqueue that is dead right now, they're not around and I wanna promote it badly! It just seems right to allow others to fix pq vids for you, so then they can get sifted possibly if you're not around for a while too

lucky760 says...

The reasons for this are all technical ones. It's not impossible, just something that would require a lot of time-consuming, bug-creating, gut-hacking work to implement.

If you're interested in the details, it's basically because siftbot only knows a single status for a video (e.g., queued, pqueued, published, dead, etc.) So if the status is changed from one to the other then back again, siftbot must make an assumption about what to go back to. E.g., currently if a post is published then it goes dead then it gets fixed, siftbot knows after getting fixed it should go back to being published. However, if a post goes from queued or pqueued to dead and it gets fixed, siftbot would assume it's supposed to go back to being published, but that's obviously incorrect.

So, the sloppy business would have to redesign all posts to perhaps remember 2 statuses like "current" and "actual" status or something. But doing that will require a major rewrite of a ton of code that could cause a lot of unforeseeable bugs and complications and permanently break the site altogether. Is that what you want? IS THAT WHAT YOU WANT?!


NetRunner says...

>> ^lucky760:
So, the sloppy business would have to redesign all posts to perhaps remember 2 statuses like "current" and "actual" status or something. But doing that will require a major rewrite of a ton of code that could cause a lot of unforeseeable bugs and complications and permanently break the site altogether. Is that what you want? IS THAT WHAT YOU WANT?!


Why not make a new state for "Dead PQueue"? That way it would be a less back breaking change, I'd imagine.

Stingray says...

>> ^lucky760:
So, the sloppy business would have to redesign all posts to perhaps remember 2 statuses like "current" and "actual" status or something. But doing that will require a major rewrite of a ton of code that could cause a lot of unforeseeable bugs and complications and permanently break the site altogether. Is that what you want? IS THAT WHAT YOU WANT?!


Thanks for explaining it. I sympathize with you as I am also a coder and understand how it sucks to implement given the current design.

How about this:

Only allow published or pqueued videos to be flagged as dead. Once a video is fixed or marked as notdead, an if statement can check the vote count and sort it appropriately...


if (VideoVoteCount >= 10)
{
    SendToPublished();
}
else
{
    SendToPqueued();
}

lucky760 says...

>> ^NetRunner:
Why not make a new state for "Dead PQueue"? That way it would be a less back breaking change, I'd imagine.

This would be equally daunting because all the code is built to use the "dead" status so adding a new "deadpq" would mean modifying everything to check for both statuses. But good thinking.


>> ^Stingray:
Thanks for explaining it. I sympathize with you as I am also a coder and understand how it sucks to implement given the current design. How about this: Only allow published or pqueued videos to be flagged as dead. Once a video is fixed or marked as notdead, an if statement can check the vote count and sort it appropriately...

Thanks for the empathy. That's a very solid compromise, to just allow pqueued vids to have dead invoked. I think we can go ahead with that solution.

Send this Article to a Friend



Separate multiple emails with a comma (,); limit 5 recipients






Your email has been sent successfully!

Manage this Video in Your Playlists

New Blog Posts from All Members