While Duplicate is not a reason for deletion, I think the site should be kept free of "spam posts", for a better search experience. Not that I'm a moderator or trying to guilt anybody for this kind of posts(I did the same mistake once), but it's an opinion.
afaic, spam would be posting stuff for the sake of advertising something
You've got a point there, perhaps "spam" was not an adequate word to use.
Now, for the sake of knowlege, why does danbooru allow duplicates? Isn't that redundant? I think the only purpose it serves is to lengthen the list of post.
You've got a point there, perhaps "spam" was not an adequate word to use.
Now, for the sake of knowlege, why does danbooru allow duplicates? Isn't that redundant? I think the only purpose it serves is to lengthen the list of post.
What would be the consequences? We have a lot of md5 mismatch posts, also multiple twitter postings. MD5 alone is about 22k postings, not all of them have parents, but surely a lot. So you would punish people if you would delete these images, even though there wasn't the duplicate picture when uploaded. MD5 mismatch images aren't exact duplicates, but have slight changes. Still, they look pretty much the same. To delete then the child post isn't that fair and one should wait 2 days (because there is a chance that the artist revise the upload or uploads it on pixiv etc.). What is with this kind of picture that got deleted here? They also shouldn't be deleted, because 1. It was uploaded, i.e. there is a difference between the dA and pixiv upload and 2. even if that weren't the case: It is from a first-party source since it's that artist's dA-Account and wasn't reposted. This is a difference. Now we could handle these posts just like Twitter postings, that won't be approved if it's posted afterwards (and even before the pixiv uploads comes up (and I'm still having problems with this "policy")). But dA works a bit difference than Twitter I think^^.
And btw. this picture has 2,27 MB, while it's parent has 2,25 MB. So not the same size and therefore no duplicate.
What would be the consequences? We have a lot of md5 mismatch posts, also multiple twitter postings. MD5 alone is about 22k postings, not all of them have parents, but surely a lot. So you would punish people if you would delete these images, even though there wasn't the duplicate picture when uploaded. MD5 mismatch images aren't exact duplicates, but have slight changes. Still, they look pretty much the same. To delete then the child post isn't that fair and one should wait 2 days (because there is a chance that the artist revise the upload or uploads it on pixiv etc.). What is with this kind of picture that got deleted here? They also shouldn't be deleted, because 1. It was uploaded, i.e. there is a difference between the dA and pixiv upload and 2. even if that weren't the case: It is from a first-party source since it's that artist's dA-Account and wasn't reposted. This is a difference. Now we could handle these posts just like Twitter postings, that won't be approved if it's posted afterwards (and even before the pixiv uploads comes up (and I'm still having problems with this "policy")). But dA works a bit difference than Twitter I think^^.
And btw. this picture has 2,27 MB, while it's parent has 2,25 MB. So not the same size and therefore no duplicate.
Well, if it serves a porpuse, let it be, then. I'm no mod anyways. I was just curious about posts and duplicates.
Leave a comment