zlacker

>>dsr12+(OP)
Some tips to maximise user privacy while deploying this tool:

1) The code, for now, runs locally. This is good. To avoid the possibility of the code being tampered with at a later day (for example, it could be modified to send copies of the image to a server), download the webpage and use the saved copy, not the live copy.

2) Do not use the blur functionality. For maximum privacy, this should be removed from the app entirely. There are _a lot_ of forensic methods to reverse blur techniques.

3) Be weary of other things in the photograph that might identify someone: reflections, shadows, so on.

4) Really a subset of 2 and 3, but be aware that blocking out faces is often times not sufficient to anonymise the subject in the photo. Identifying marks like tattoos, or even something as basic as the shoes they are wearing, can be used to identify the target.

>>Ansil8+vn
A replacement for blur could just be black boxes. Seems easy and safe enough.

>>_bxg1+9K
As soon as deepfakes and "thispersondoesnotexist" started happening I wanted a tool that would replace everyone's face with a auto-generated face just so I could do street photography without feeling like I was invading people's right to obscurity

>>jazzyj+3y1
That's a really interesting idea. I'm not sure what the commercial value would be, but the artistic value (and gain in privacy) would be huge. I'm not sure what you'd do about identifying marks like tattoos, but perhaps that isn't the biggest concern when compared to faces.

Could you train a model with your own face as a start, and then run your photos through an existing consumer face-swap app? Or perhaps use a celebrities likeness? I wonder how much the visual 'likeness' of a stranger is worth.