Danbooru

Flag Vandalism

Posted under General

provence said:

Don't know what you mean. The post is already 7 days old, so it should not be pending anymore.
But yes, it used to be possible, some users received feedback for flagging pending posts. If it is still possible, then it should be changed.

Oh, derp, forget it. Forgot it was in the red queue for a second, I'm like half-asleep right now.

Well, anyways, whoever did that should probably receive a reprimand.

It looks like it was fixed in issue #1327, but reverted because it prevented the system from creating "Unapproved in the three days" flags on pending posts. I think this could be avoided now though, now that we're using DanbooruBot for system-generated flags.

Chiera said:

post #2777312
The scan artifact clause excludes posts that were originally uploaded by the artist. And this was uploaded by the artist to Twitter.
Seems wrong to delete Twitter images for reasons like that and it happened twice on that post already.

jpeg artifacts, but yes.

ion288 said:

Um, is md5 mismatch a valid reason to flag? Not that I would mind seeing a few duplicates go but there are 38k of them.

post #2582744 post #2722111 post #2539636 and more.

No, it’s not, IMO. Quite often they’re old versions of revised posts that some users like to keep around. In fact, all three posts you mentioned are old versions.

If it’s an MD5 mismatch due to being a third-party edit, a post can be flagged for that instead, especially if it’s a stupid modification, introduces more artifacts or is a lossy-lossless conversion.

1 22 23 24 25 26 27 28 29 30 58