Danbooru

Post relationships on pictures with different sources and resolutions

Posted under General

I found that there's a few artists who post some of their pictures in their Twitter with a larger resolution than their Pixiv counterparts (Neki (Wakiko) and Yomu (Sgt Epper) for example); and I see there may be valid reasons to make either of them the parent post, but I'm not sure which one should be it.

Personally, I think the Pixiv version of a picture generally should be the parent in case they're the same, but the Twitter versions by these two artists in particular are absurdres and if we compare them to their Pixiv counterparts, the Pixiv ones have lower resolution. Like post #2594647, post #2600294, post #2630931 and post #2630933, to mention some.

And so, I want to ask something. In the case of having two posts with different sources which are the same picture, but the Pixiv one has lower resolution than the other (said second source can be anywhere the artist posted it, doesn't have to only be Twitter), which one should be the parent?

@Mikaeri gave me the idea of asking about this issue in the forum when I asked them about the parent-child relationship on post #2639668.
(I apologize if you were about to create this same topic, Mikaeri)

Nah, no problem. As long as we're able to discuss it somewhere, all is well.

I might've mentioned my opinion before but this is my priority for parenting images:

1. Most recent revision
2. Better file format (png > jpg)
3. Less artifacting (post #2626407 and its parent)
4. Higher resolution
5. Whatever post is still live (post #2613788, post #2227073)
6. If you can't tell, whatever came first I guess: post #2633900 vs. post #2643602

We don't have very specific guidelines for the priority of parenting images that are identical, but perhaps this is the chance to clear some of that up.

evazion said:

Yeah, already moved them. If you go to /wiki_pages/search and search for bodies of `*[[*howto:whatever*]]*`, that should find all pages linking to a given page.

Yes, though do pay mind to the space/underscore interchangeability for wiki links.

Example:

Those all link to the same wiki page.

However, the search for *[[*List of airplanes*]]* will only find links matching the first example.

Replacing spaces/underscores with *'s is workable, but it can generate false positives. An example is a search for *[[List*of*birds*]]*, where you will find two matches but there is actually none.

My usual priorty always comes with pixiv as main parent though just like seen my recent post #2643834 and post #2643833

I don't know why but it feels always feel inferior to upload pictures from twitter as long as their file format is not png or at least for me (if you compare these two, pixiv one looks more vivid and clean). There are some cases where artist usually deletes their works from their twitter account so its better to have more solid source for main parent such as making pixiv upload as main parent. However and lastly I'm also comparing two posts and if the picture have higher resulotion as well as bigger file size then I prefer to make these kind of pictures main post.

Claverhouse said:

Or even, utterly identical duplicates could be chucked out as wastes of space...

Sure, we could only keep the highest quality picture in case there's one or more identical ones around and delete the rest.
howto:upload also has a section about duplicates:

Check for Duplicates

Be sure that your post has not been uploaded by someone else. When uploading an image, use the find similar button to find images which are visually identical to your upload.

If your image has already been uploaded, only upload if you have a higher quality copy. Once you have uploaded your higher quality copy, set all existing copies of the image as child posts of your copy.

On the other hand, though, the duplicate wiki entry states that just "being a duplicate" is not a reason to flag a post.

Anyways, the best course of action to prevent those "wastes of space" as you say, would be only uploading said identical posts in case of them being a revision, or of better quality than the already uploaded one (less artifacting, better file format...) by using the Find Similar function and checking the versions that are already posted and the one we have.

And while using said function is a must to avoid exact duplicates, especially from the same source (except when we know they're revisions and such), I personally think if they have different sources, identical duplicates should stay.

I respect and understand your point of view on this, though.

Updated

It is policy not to delete duplicates. There is ample reason for this, but the most important one being uploader health. If such a policy were enacted, Twitter would practically be a lava zone for uploads.

There was a former moderator by the name rantuyetmai (user #288549) that actually deleted duplicates right off the server even when he had absolutely no permission to by albert or any other admin -- and that's why the permissions are revised to be what they are now.

Anyways, there's more as to why, but it's pretty much a bad idea, mostly because even images from different sources can have different information. The 'best' image isn't always the one with the best resolution, and neither is it with the best file format, the least visible artifacting, the most recent... etc. Take post #2633900 and post #2643602 that I've mentioned before -- there's no way of telling which one is the better one. Maybe one has more artifacts than another, but they're so similar pixel-wise the difference is practically nil (and perhaps it could even be a difference on the compression level)

And as to why image samples are flagged and deleted, you can read topic #13646 and the relevant wiki pages.

Updated

1