Danbooru

Uploads From 3rd Party Imageboards

Posted under General

CodeKyuubi said:

Cease and desists that stop translation efforts, most likely. He's referring to Rignak uploading directly from baka-tsuki.

Right, I didn't think of that. But wouldn't they erase their files if they stop the translation ? In this case, we would have a 404 error if we try to look at the source and wouldn't bring harm to them.

Rignak said:

Right, I didn't think of that. But wouldn't they erase their files if they stop the translation ? In this case, we would have a 404 error if we try to look at the source and wouldn't bring harm to them.

The idea is to not bring them additional DMCA requests to begin with.

A particularly bad third party board for posting from is e-shuu shuu. Typically these consist of images converted from lossy to lossless format for no rational reason. This has led to some users of this site mistakenly believing they are of superior quality just because of the higher file size, and even to upload them and make posts with the original unmodified source child posts.

source:http://e-shuushuu.net/images/

post #2621011 is an example of this. Its source on e-shuu shuu reveals a file name of CmxZyTFUIAAbIP5.png, which matches apart from its file extension to CmxZyTFUIAAbIP5.jpg, the image of the source in the below post.

As should be clear the e-shuu shuu board took the file from Twitter and converted it to PNG, thus inflating the file size.

chinatsu said:

A particularly bad third party board for posting from is e-shuu shuu. Typically these consist of images converted from lossy to lossless format for no rational reason. This has led to some users of this site mistakenly believing they are of superior quality just because of the higher file size, and even to upload them and make posts with the original unmodified source child posts.

source:http://e-shuushuu.net/images/

post #2621011 is an example of this. Its source on e-shuu shuu reveals a file name of CmxZyTFUIAAbIP5.png, which matches apart from its file extension to CmxZyTFUIAAbIP5.jpg, the image of the source in the below post.

As should be clear the e-shuu shuu board took the file from Twitter and converted it to PNG, thus inflating the file size.

We should be treating lossy-lossless posts such as what you're describing as image samples or unwanted/rejected third-party edits. Sure we might be able to grace some of them, but for most, if the original is already upped and the png was upped out of naivete, then it deserves to be deleted.

Recently went through a bunch of lossy-lossless -status:deleted parent:any filetype:png posts and I have to say I'm not that surprised... although the tag is somewhat misused from time to time. One interesting case I've noted, though, is a lossy-lossless png with its parent being the original png. Assumably, what happened is that the parent got converted into jpg, then the jpg got lossy-lossless converted back into png, thus doubling the filesize and legitimizing the jpg compression artifacts.

It's quite strange, the lengths that people have gone to think that apparently higher filesize means better quality. I happen to think the opposite -- if the image data is the same and the compression is better, that's an immediate + for me. This should be the standard, especially now when we have so many image integrity verification tools at hand.

1 2