Suggestions to avoid comment clutter
When invoking *backup, the comment section of the video in question gets a big chunk of html code in the middle. This looks ugly, and reduces readability. I try to remedy this by editing my comment after I have supplied a backup, but I think it would look nicer if the system could remove the *backup comment entirely, and just let @siftbot's confirmation comment stand. Something similar was implemented with the *reclaimvote invocation after the Siftpocalypse, so it should be possible. For an example of the comment clutter I'm talking about, see here:
http://videosift.com/video/Dschinghis-Khan-Eurovision-1979
Another thing that annoys me is when I see @siftbot referring to 2 lost comments in a duplicate video, and the 2 comments in questions are just the *dupeof and *isdupe invocations. It seems unecessary to refer to such purely instrumental comments in the original video. For instance, this comment by @siftbot adds nothing of value to the comment section, and might as well not be there.
I suggest that @siftbot ignores the *dupeof and *isdupe invocations when counting the number of lost comments, and that if those two are the only comments in the dupe's comment section @siftbot ignores this part of the dupe process entirely.
http://videosift.com/video/Dschinghis-Khan-Eurovision-1979
Another thing that annoys me is when I see @siftbot referring to 2 lost comments in a duplicate video, and the 2 comments in questions are just the *dupeof and *isdupe invocations. It seems unecessary to refer to such purely instrumental comments in the original video. For instance, this comment by @siftbot adds nothing of value to the comment section, and might as well not be there.
I suggest that @siftbot ignores the *dupeof and *isdupe invocations when counting the number of lost comments, and that if those two are the only comments in the dupe's comment section @siftbot ignores this part of the dupe process entirely.
Load Comments...
Discuss...
Enable JavaScript to submit a comment.