Pretty please. Just use the parenting function.
And at the very least, tell us what it's a duplicate OF so we can parent it if you can't figure out how.
Thanks.
Updated
Posted under General
When you post an picture, there is a field for an parent post.
You put the originals post number to that field. You can find the number sequence in the url to the original post. Just copy that sequence to the parent post field.
I'm sorry if I remembered it wrong. However, you should atleast realize what I'm refering to if you have posted a single pic.
I don't have any pictures to post. Instead I was going to identity all the duplicate images that already exist. I think if you take a moment to put yourself in the shoes of someone who is new to this site, you would see it is not obvious to work out the best way of doing that.
Persona said:
Er...guilty of this. Although I don't see why you would want an exact copy of an image on the site as a parent of the original, rather than just getting rid of it. Is this just in regards to resized/cropped images?
I think that's to avoid another person uploading it again, basically (especially if there's multiple "official" versions, such as a wallpaper version or a larger version).
Although when I think about it, if you delete an image, it does the same thing since the hash is saved. So yeah, good question actually?
Persona said: Er...guilty of this. Although I don't see why you would want an exact copy of an image on the site as a parent of the original, rather than just getting rid of it. Is this just in regards to resized/cropped images?
Well, personally I would be in agreement and would delete, but site policy is to only delete for rules violations, and so that's what I'm going with. It also prevents someone else from uploading an image with the exact same hash (though I was under the impression deleting it did the same).
So yes, duped just get parented and tagged "duplicate".
jxh2154 said:
Well, personally I would be in agreement and would delete, but site policy is to only delete for rules violations, and so that's what I'm going with. It also prevents someone else from uploading an image with the exact same hash (though I was under the impression deleting it did the same).So yes, duped just get parented and tagged "duplicate".
Okay, thank you for clearing that up, and sorry for the unnecessary flagging in that case. Someone actually parented my duplicate image, but when I realized it was the same as it's parent I thought I should try to fix it.
Persona said: Okay, thank you for clearing that up, and sorry for the unnecessary flagging in that case.
That's fine. I'm not actually pissed at anyone, the subject line is all in caps to get people's attention. And so far it has for three people, and those are only the ones who admitted it =P So I think it worked,
Parent: http://danbooru.donmai.us/post/show/122303
Child: http://danbooru.donmai.us/post/show/167355 (duplicate)
I've hashed both images with the original from the artists website and have determined the parent is the original image.
In this case, would it be beneficial to remove all tags, save the duplicate tag, from the child post? This would free the site of some of the clutter from duplicates and the post would still be available, since it's effectively inheriting the parent posts tags.
Granted, a reupload with tags of the child image would mess this up.
testure said: In this case, would it be beneficial to remove all tags, save the duplicate tag, from the child post? This would free the site of some of the clutter from duplicates and the post would still be available, since it's effectively inheriting the parent posts tags.
No, it's probably best to just leave the tags.
What I think albert should do, if he gets the chance, is put a border around child images. I like seeing it around the parent, but something to distinguish a child from the thumbnail results view would be awesome.
It's not "useless" because no doubt the majority of all tagging, flagging, uploading etc is done by a very small percentage of danbooru users, and at least the most prolific will see it. However, it should probably be part of the flagging dialog box that comes up to include this warning. Then everyone sees it.