The EU’s AI rules are having an impact.
Archived version: https://archive.is/20260811122405/https://www.theverge.com/ai-artificial-intelligence/977823/anthropic-claude-ai-watermarks-c2pa-text-images
The EU’s AI rules are having an impact.
Archived version: https://archive.is/20260811122405/https://www.theverge.com/ai-artificial-intelligence/977823/anthropic-claude-ai-watermarks-c2pa-text-images
As I understand it, you’re right that you need a good length of output to be able to detect the watermark, because only then can you see the statistical effect with confidence. And in code there are usually various options for how you get something done, and they could watermark generated code by adding a distinctive pattern to its preferences for certain constructs over others. But again, it would have to be subtle, so you’d need a large enough sample of its output before you could see the effect.
It should be fairly easy to stop this detention even in code.
You just need to set very strict “rules” the AI must follow when writing code.
Variable and method names etc. Must follow a specific formula.
Have a different AI write your docs etc.
If you’re just vibe coding everything, the watermark would work. So maybe a good thing. But it’ll be whack a mole, and if you’re careful I’m sure you can stop the detection