stable-diffusion VS invisible-watermark

Which is a 1-click install of Stable Diffusion with an alternative web interface. You can choose a different approach but this one is pretty simple and I am new to this stuff.

an invisible watermarking of the outputs, to help viewers identify the images as machine-generated.

It sounds like you just want to set up Stable Diffusion to run locally. I don't think your computer's specs will be able to do it. You need a graphics card with a decent amount of VRAM. Stable diffusion is in Python as is almost every AI open source project I've seen. If you can get your hands on a system with an Nvidia RTX card with as much VRAM as possible, you're in business. I have an RTX 3060 with 12 gigs of VRAM and I can run stable diffusion and a whole variety of open source LLMs as well as other projects like face swap, Roop, tortoise TTS, sadtalker, etc...

Use specific GPU on multi GPU systems · Issue #87 · CompVis/stable-diffusion · GitHub

I dealt with this in one of my posts. At least SD 1.1 till 1.5 are all trained on a batch size of 2048. The version pretty much everyone uses (1.5) is first pretrained at a resolution of 256x256 for 237K steps on laion2B-en, at the end of those training steps it will have seen roughly 500M images in laion2B-en. After that it is pre-trained for 194K steps on laion-high-resolution at a resolution of 512x512, which is a subset of 170M images from laion5B. Finally it is trained for 1.110K steps on LAION aesthetic v2 5+. This is easily verified by taking a glance at the model card of SD 1.5. Though that one doesn't specify for part of the training exactly which aesthetic set was used for part of the training, for that you have to look at the CompVis github repo. Thus at the end of it all both the most recent images and the majority of images will have come from LAION aesthetic v2 5+ (seeing every image approx 4 times). Realistically a lot of the weights obtained from pretraining on 2B will have been lost, and only provided a good starting point for the weights.

stable diffusion · CompVis/stable-diffusion@2ff270f · GitHub

Here for example --> https://github.com/CompVis/stable-diffusion

I'm not sure your online tool is working. I tried it with the watermarked example image from https://github.com/ShieldMnt/invisible-watermark, and your tool returned that it did not detect a watermark:

The public availability and quality of LLMs and stable diffusion have been an unprecedented disaster for spam mitigation largely because there is no effective way to determine if this content was created and posted by a human being. Particularly with text content, the amount of information present is so small that I don't believe there is a way to definitively analyze it and concretely say whether or not it was generated by an LLM. The only potential way to do so that I can think of would be to check every comment against the output of each LLM service provider, but that's a futile endeavor because you can go back to inserting typos and substitutions, reorder the text or omit some of it, mash multiple outputs together, or even self-host an LLM and skip all the bullshit from the start. At least the images and videos being created by stable diffusion can be watermarked reasonably well.

i found an article but i don't understand it... is there any video tutorial of anything?

Creating invisible watermark encoder (see https://github.com/ShieldMnt/invisible-watermark)...

Tools to add this kind of watermarking are publicly available or could be reimplemented by in house developers if they don't like FOSS licenses.

Most major AI generators embed invisible watermarks into the images so that they can detect them and avoid training on generated imagery later. I know Stable Diffusion uses this python library to do it: https://github.com/ShieldMnt/invisible-watermark I haven't bothered to look up others but they have similar steps.

It uses the same library as Stable Diffusion (https://github.com/ShieldMnt/invisible-watermark) without giving credit in its github repository which does not even contain the sources of its 3 lines of code. This watermark doesn't protect anything, it would be necessary that the robots that retrieve the images from the internet make the effort to read the watermark to not add them in their dataset (best case scenario, totally utopian). The repository is suspicious and could be a way to install malware.

- Stable diffusion uses https://github.com/ShieldMnt/invisible-watermark by default unless you check "Do not add watermark to images" in settings

"This script incorporates an invisible watermarking of the outputs, to help viewers identify the images as machine-generated."