4 ms·
Many good reasons have been presented here. And on the other side, is there any reason not to do it? (part from the effort required to put it in place)
by tjoff 3y ago
Many good reasons have been presented here. And on the other side, is there any reason not to do it?
(part from the effort required to put it in place)
- bogdan 3y agoI guess it's a form of tracking and we don't like that
- brucethemoose2 3y agoThere is nothing personally identifiable in the watermark though, no more than other image metadata. And yeah, you can see the watermarking code in the huggingface pipeline now. Its pretty simple, and theres really no reason to disable it.
- adventured 3y agoWhat exactly is in the watermark? Other image metadata is commonly used to track people, or used in combination with a few other hints to track people. If it's strictly a primitive watermark with absolutely nothing unique per mark, then it might be no big deal.
- brucethemoose2 3y agoIt is. See for yourself: https://github.com/huggingface/diffusers/blob/2367c1b9fa31266e55e628f2fbbbb2b115e08eaf/src/diffusers/pipelines/stable_diffusion_xl/watermark.py https://github.com/huggingface/diffusers/blob/2367c1b9fa3126... I see no reason to disable it. Its fast, and its no more personal than basic metadata like image format and resolution... I can't think of any use case for disabling it other than passing AI generated images as authentic.