>>93651564That's why I rarely use 4tan.
For /co/, the usual procedure is to search with desuarchive, and then get any full images I need using fireden or
yuki.la, since desuarchive's image server is dying.
>>93651576The filename from
>>93650954 is 1499216190594.png.
Neither of these links work though:
https://i.4cdn.org/co/1499216190594.pnghttps://i.4cdn.org/ic/1499216190594.pngSo it doesn't look like the image was posted there. However, that may be because either the file, post, or containing thread was deleted on 4chan.
The next approach is to search for the post numbers on /co/ and /ic/ made around that time in the archives.
For /co/, the timestamp 2017-07-05 12:56:30 AM (UTC) falls between posts
>>93648516 and
>>93648517. In particular,
>>93648516 is an image post with timestamp 2017-07-05 12:56:29 AM (UTC), while the next image post is
>>93648517 with UNIX timestamp 2017-07-05 12:56:31 AM (UTC). Which means whoever posted
>>93650954 didn't copy it from a /co/ thread.
For /ic/, the timestamp 2017-07-05 12:56:30 AM (UTC) falls between posts
>>>/ic/3048016 and
>>>/ic/3048017. Again,
>>>/ic/3048015 is an image post with timestamp 2017-07-05 12:53:52 AM (UTC), while the next image post is
>>>/ic/3048022 with timestamp 2017-07-05 01:00:20 AM (UTC). Which means whoever posted
>>93650954 didn't copy it from an /ic/ thread either.
So wherever
>>93650954 got it from, it wasn't /co/ or /ic/, but either some other board on 4chan, or some other chan that uses UNIX timestamps.
Moreover, the archive image hash for the image in
>>93650954 is 7vAZbhuAOMdPVsGuqKTX1w (foolfuuka archivers use MD5 in Base64), but if you try searching that hash on all foolfuuka archives listed at
http://archive.4plebs.org/_/articles/credits/you'll find no matches, except for this post
>>93650954. This might be because
>>93650954 edited the pic though, so it's not conclusive. I'd need to write some archive scripts to go any further.
