05/02/25 - NAS is now selectively allowed on the soybooru. See https://wiki.soyjak.st/SoyBooru_guide and https://booru.soyjak.st/post/view/116224 for details.
05/02/25 - Uploads with fewer than 5 (five) tags and a variant tag will be denied
04/28/25 - There's a new sheriff in town. Send all concerns, complaints, and suggestions to soysneed@soyjak.st
IP 13.59.216.3 has been banned until the end of time because of VPN Detected
If you couldn't possibly be guilty of what you're banned for, the person we banned probably had a dynamic IP address and so do you.
this one was a little more challenging than the last few because the original image was so crusty it was only usable as a reference. used wholesome soyjak as the base, found the original .png of the bullet hole, aligned everything in more or less the same position as the original picture, and reconstructed the tears using the blue in ms paint's default palette (#3f48cc). there was also a layering issue in the original where the blood splatter and tears were layered above the glasses and eyebrows/wrinkles, which has been corrected in this version.
other improvements: transparent background, filesize reduced from 57.7KB to 38.1KB (-33.97% reduction). could have saved a lot more if i reduced the bullet hole's color depth to 8-bit, but opted not to for realism's sake
ideally, the picture in >>9 should be replaced with this one instead, instead of deleting >>9 altogether. a catbox download of the original image should also be linked to in the comments for internet archeology's sake, but not hosted on the booru itself so people aren't downloading a deprecated version
Warrior-Z: @Warrior-Z: Also, not sure if moving things into slots is possible but I'll take a look, but when you have duplicates, make sure they are the same image, and not any improvements or any remasters added.
Hellcat: @Warrior-Z: was tagging the worse duplicate in those cases. all of the ones in the series:soyjak_restoration_projects are fixes of old ones that had some image artifacts/transparency issues, alterations are documented in the comments section. i should've warned you that some of them were really old legacyjaks, but yeah
Warrior-Z: @Hellcat: It's fine, it was only like 2, and they are still here, archived under your name, which is alright. As long as it's still here, and there's no clutter.
Hellcat: @Warrior-Z: so for moving posts, the github readme for shimmie2 (https://github.com/shish/shimmie2/wiki/Settings) mentions something about "image options," don't know what this would look like on your end obviously, but i believe you would just have to manually change the $id flag?
there is also a trash extension if you look under the System tab, so there should be some sort of trash/recycle bin for recently deleted posts. again, don't know what that would look like on your end, but i think the functionality is there
- Reply
this one was a little more challenging than the last few because the original image was so crusty it was only usable as a reference. used wholesome soyjak as the base, found the original .png of the bullet hole, aligned everything in more or less the same position as the original picture, and reconstructed the tears using the blue in ms paint's default palette (#3f48cc). there was also a layering issue in the original where the blood splatter and tears were layered above the glasses and eyebrows/wrinkles, which has been corrected in this version.
other improvements: transparent background, filesize reduced from 57.7KB to 38.1KB (-33.97% reduction). could have saved a lot more if i reduced the bullet hole's color depth to 8-bit, but opted not to for realism's sake
ideally, the picture in >>9 should be replaced with this one instead, instead of deleting >>9 altogether. a catbox download of the original image should also be linked to in the comments for internet archeology's sake, but not hosted on the booru itself so people aren't downloading a deprecated version
- Reply
- Reply
- Reply
- Reply
- Reply
there is also a trash extension if you look under the System tab, so there should be some sort of trash/recycle bin for recently deleted posts. again, don't know what that would look like on your end, but i think the functionality is there