Remove–AI–Watermarks – CLI and library for removing AI watermarks from images

168 points - yesterday at 10:30 PM

Source

Comments

akersten yesterday at 10:59 PM
There's an underappreciated comment in the other thread about SynthID and OpenAI [0] that captures what (IMO) the hacker ethos on this should be. We care about privacy, we should not accept tools that barcode our every digital move. (note that the counter of "well, they don't do that yet" is not particularly convincing)

[0]: https://news.ycombinator.com/item?id=48200060

cush today at 4:29 AM
I love that this is exactly one position above OpenAI Adopts SynthID Watermarks
site-packages1 yesterday at 10:46 PM
I don't know I really like the definitive indicator that something is AI so I can completely ignore anything else that comes from them.
b3ing today at 2:32 AM
Watermarking images generated from trained data on stolen copyrighted material, I get why so they can try to tell if something is real or not but something seems wrong
Tiberium yesterday at 10:52 PM
This is a bit misleading as for Gemini it only properly removes the visible watermark. To remove SynthID it has to regenerate the image at low noise with SDXL, which will likely destroy a lot of small details, plus won't work for higher res properly (NB2 and GPT Image 2 support up to 4K image outputs)
dostick today at 3:55 AM
To remove Gemini watermark, open dev tools and block http request to watermark. It is overlaying logo in client.
j2kun yesterday at 10:53 PM
> Use cases where the threat model fits: You are preserving art or historical record against false-positive "AI-generated" labels.

Sorry, how does using AI to generate images have anything to do with this? Image generators cannot insert watermarks into things they did not generate, and it seems highly unlikely that you will get a false-positive watermark on human-generated art, especially if, as the readme says, these watermarks have high enough fidelity to trace to a specific session id. Plus the modifications to the image needed to erase watermarks would necessarily change the thing being "preserved."

[edit]: the more I read the more I'm convinced, the claimed use cases in the README are bullshit and the real reason is to provide a tool that helps people bypass "AI-generated" labels on social media for AI slop.

airstrike yesterday at 11:28 PM
Regardless of one's opinion about this particular project, it seems obvious to me that the path forward is proving authenticity of non-AI resources rather than attempting to watermark all the AI-generated ones.
a-dub yesterday at 11:33 PM
watermarking only really works when the scheme is secret.

putting cyphertext in high frequency noise is old news. in generative land would be far more interesting to use the generative flexibility to encode in macrostructure.

UrbanNorminal today at 2:13 AM
Can't we instead just use open source models?
redox99 yesterday at 11:58 PM
There's quite a bit of difference in the before and after. I hope they can find a way that better preserves details.
deleted today at 2:28 AM
yalogin today at 12:25 AM
This is brilliant pace. What I expected to see
deleted yesterday at 11:00 PM
sscaryterry yesterday at 11:28 PM
Yin and yang.
gbraad yesterday at 11:27 PM
I just saw the announcement about OpenAI or so going to use SynthID and all I thought was; what can d be read(located) can be removed. Seems the tool already exists, proving my point.
tamimio yesterday at 11:25 PM
Amaze amaze amaze

- Rocky

andrew_kwak today at 3:51 AM
[dead]
grebc yesterday at 11:14 PM
What’s wrong with showing off AI bro? Why the shame?