Skip to main content


in reply to ASRG

Don't forget #Nightshade, which screws around with the image enough to harm an AI image generator but is still recognizable to the human eye. (The Blender art in my banner has been Nightshaded!)

Edit: nightshade.cs.uchicago.edu/wha…

This entry was edited (2 months ago)
in reply to ASRG

another take that I hope I have time to write:

An app that feeds either static text or a poisoned Markov Chain, but it writes back one byte at a time, and tries to delay the client as much as possible. It would probably would have to have start with a big delay, and every time the client disconnects, it registers the IP and the delay in a db so next time it tries a lower delay until it finds the best delay for each client.

Unknown parent

mastodon - Link to source
kjaerulv
@balslev skal ind på siderne!
in reply to ASRG

I would also add the following:

- Nightshade ("poison pill" for AI)
nightshade.cs.uchicago.edu/
...which is part of Glaze (glaze.cs.uchicago.edu/)

- Fawkes (poison your face for facial recognition services)
sandlab.cs.uchicago.edu/fawkes…

in reply to F4GRX Sébastien

Thanks for sharing. Sounds like it's a problem all image obfuscators have to deal with.
This entry was edited (2 months ago)
in reply to ASRG

And, for something lightweight and easy for anyone to implement, may I submit a #WordPress plugin prototype:

kevinfreitas.net/tools-experim…

#AI