Isdupe working as intended, or?
I seem to recall having a couple of times where an * isdupe invocation was required.
This morning I called dupe on a video, and instead of waiting for someone else, siftbot wrote:
This video has been declared a duplicate by the original submitter; transferring votes to the original video and killing this dupe - dupeof declared by demon_ix.
This video has been nominated as a duplicate of this video by demon_ix. If this nomination is seconded with *isdupe, the video will be killed and its votes transferred to the original.
Note - I wasn't the original submitter of the video.
After that, the video was duped, and didn't wait for an isdupe invocation.
Is it broken, or am I missing something?
This morning I called dupe on a video, and instead of waiting for someone else, siftbot wrote:
This video has been declared a duplicate by the original submitter; transferring votes to the original video and killing this dupe - dupeof declared by demon_ix.
This video has been nominated as a duplicate of this video by demon_ix. If this nomination is seconded with *isdupe, the video will be killed and its votes transferred to the original.
Note - I wasn't the original submitter of the video.
After that, the video was duped, and didn't wait for an isdupe invocation.
Is it broken, or am I missing something?
4 Comments
Yesterday, I did a dupeof on a video (neither the dupe or original were mine), and it duped them straight away and did not wait for the isdupe invocation.
Again. http://www.videosift.com/video/Oh-Boy-14-to-22-inches-of-snow-Meteorologist-freaks-out?noredirect
You have to do the programmer call... oooh @lucky760! *blows duck whistle*
*quack!*
It should be fixed now.
Discuss...
Enable JavaScript to submit a comment.