Sankaku Channel/Duplicate Overload: From Twitter

Hey guys first post here.

I had to point out that the sheer amount of duplicate/potential duplicate is getting out of hand.

I am not sure if there is someone uploading these or theres a bot doing the uploading, but I suggest holding back on uploading images onto this site from twitter for few weeks so to make sure the artist uploaded the image on twitter exclusively.

From my observation, the twitter version is downsized and compressed.

Unless there is an easy way to get rid of the inferior version, I wish people would take an extra step to make all of our quality of life on sanchan better.

Cheers

If you make sure to tag the higher quality version as the parent of the low quality duplicate and then flag the low quality version I will get to deleting it much faster.

Don’t tag “duplicate” the posts that have the best quality and are supposed to stay. Your change to Post #4433147 was bad.

gamesahoy said:
I wish people would take an extra step to make all of our quality of life on sanchan better.

You called? Don't worry, my quality of life is pretty good. ;)

Bad jokes aside, I really wish uploaders were forced to use the "similar post" feature. Then again, people probably use some kind of upload program anyways.
The amount of duplicates isn't getting smaller. I'm daily finding at least half a dozen - at least it feels that way.
It doesn't help that there is a flag limit of 10 posts per day - I stopped flagging because of it and because it's hard to keep track of what's already flagged and what not.
I also don't quite understand the need for flagging, isn't it enough that it is tagged as a duplicate?

Will there ever be a day, where we can just mass delete all duplicates? I mean, if there really will be lost something of value, it will be reuploaded, won't it?

sanchan said:
Will there ever be a day, where we can just mass delete all duplicates? I mean, if there really will be lost something of value, it will be reuploaded, won't it?

The problem is so many posts are incorrectly tagged as duplicates.
I've been grinding down a dozen or so a day when I can get around to it.

Please continue flagging, and when you can't please be sure to tag the lower quality post as the duplicate, and set it as a child of the quality one.

Slowly but surely we'll be cleaning up.

sanchan said:
Will there ever be a day, where we can just mass delete all duplicates? I mean, if there really will be lost something of value, it will be reuploaded, won't it?

Even better, just mass delete all duplicates that are crap resolution. Nothing of value will be lost.

SampleText said:
Even better, just mass delete all duplicates that are crap resolution. Nothing of value will be lost.

Sounds like a very bad idea.

Tallcat said:
The problem is so many posts are incorrectly tagged as duplicates. (...)
Please continue flagging (...)

I'll continue flagging then. If I run into the flag limit again, I'll probably create a "to flag" pool for the rest, so I can flag them later.

Is there an easy way (programmatical way) of checking if a post is already flagged? It's sometimes hard keeping track.
I already wrote a script to help with parenting (adds "Choose Parent" and "Set Parent" modes) and I'm working on a "Flag duplicate" option with default text and parent ID.

Maybe I'll create a (private) "flagged" pool - that way anyone can immediately see that a post is already taken care of.
Maybe I make it so the script removes a post from the "to flag" pool and adds it to the "flagged" pool.
Maybe I'll just throw those two ideas out the window. Don't know at this point.

Flagged posts have a red outline and show the reason for the flag within the post for me. Is that moderator only?

ALAKTORN said:
Flagged posts have a red outline and show the reason for the flag within the post for me. Is that moderator only?

As Contributor, i see the same thing as you.

ALAKTORN said:
Flagged posts have a red outline and show the reason for the flag within the post for me. Is that moderator only?

I just tested it and had a look how the borders are implemented (it's a css class).
The red outline is overwritten by the greenish child/parent outlines. I'm pretty sure the reason is that the "img.flagged" class comes before the "img.has-children" and "img.has-parent" in the style.css.
"img.pending" (for approval) comes after the parent/child stuff and that definitely shows.
So someone just has to rearrange the css classes and the red border should always appear.
In the meantime, I'll fix it per script.

Inside the post itself, the flag reason definitely isn't shown (for me), but I just noticed, that the flagged post has an "Appeal" option. That's a bit weird, since it's an appeal for deletion, but the post was only flagged. But as long as it appears when flagged, it's all I need.