Through the great work of @ResidentChiefNZ The Stable Horde now supports depth2img, which is a new method of doing img2img which better understands the source image you provide and the results are downright amazing. This article I think explains it better than I could.
See below the transformation of one of my avatars into a clown, a zombie and a orangutan respectively.
To use depth2img you need to explicitly use the Stable Diffusion 2 Depth model. The rest will work the same as img2img.
Warning, depth2img does not support a mask! So if your client allows you to send one, it will just be ignored.
If you are running a Worker you can simply update you bridge code and you mustupdate-runtime as it uses quite a few new packages. Afterwards add the model to your list as usual.
We recently also enabled diffusers to be loaded into voodoo ray, so this will allow you to not only keep the depth2img in RAM along with other models, but also the older inpainting model! Please direct all your kudos to @cogentdev for this! I am already running both inpainting, depth2img, sd2.1 and 15 other 1.5 models on my 2070 with no issues!
If you have built your own Integration with the stable horde such as clients or bots, please update your tools to take into account depth2img. I would suggest adding a new tab for it, which forces Stable Diffusion 2 Depth to be used and prevents sending an image mask. This is to avoid confusion. This will also allow you the opportunity to provide some more information about the differences between img2img and depth2img.
Enjoy and please shower the people behind the new updates with Kudos where you see them!
Hey everyone, I have finally finished integrating Patreon with the Stable Horde. This will allow me to maintain everyone rewards automatically, and adjust them according to your status on patreon as well.
This means for example, if you upgrade your subscription from one tier to the next, you will also receive the adjusted reward on the next month’s cycle without me having to find the time to adjust things
Also there is a new adjustment, where now patrons can utilize the horde even via VPN. The VPN restriction is in place to prevent people sending or requesting unethical or illegal content, so by trying your bank account to your username, you provide a way to block the access if it’s abused this way. This is allowed from the lowest tier, so if you have any reason to use VPN to access the stable horde, feel free to use this.
Finally, as an extra thank you, I have also added a small “candy” even for the lowest tiers!
For all this to work, I need to know your Stable Horde ID, and specifically the #number# next to your username! So please send it to me asap if you haven’t already! If you ever change accounts on the horde, you’ll also need to send me the new ID.
When you provide your Stable Horde id, you will also be listed on the sponsors page . If you would prefer a different alias to be shown on the sponsors, please let me know as well.
With the new nataili bridge we had lost the existing NSFW censorship model which was responsible for ensuring SFW workers who wanted to, did not generate NSFW images. It was also an important part of the censorlist implementation, where even NSFW workers could choose specific words which would activate the censor filter as they are concepts that never belong into pornographic prompts.
Today I’m happy the announce that with the help of hlky, the NSFW filter is back, so there’s no reason for anyone to stick to the old worker code anymore!
To add to that, I’ve also added an extra protection from what I call ‘Corrupt Prompts’ in the horde. That is, prompts which have a chance to generate completely unethical AI images. Now when the prompt detects the specific generation of words, the owner account and IP will be flagged and the request logged.
Nothing is perfect but I plan to keep tweaking the detection for corrupt prompts to ensure I prevent as much as possible from reaching the workers. I also hope that this extra logging will give pause to people who might think to use the horde for unethical purposes.
Unfortunately the safety_checker model responsible for the NSFW detection, takes a bit more of your VRAM to work, so if you find that after downloading the latest version of the bridge, your workers starts crashing, consider reducing your horde power, or unloading a secondary model, such as one of the dreambooths.