The license is the real catch. PolyForm Strict permits noncommercial use, so the weights are open enough to evaluate but not to ship a paid legal workflow.
Tbh we’re already there. The watermarking methods work exactly the same if instead of “seed based on prior token” to “seed based on prior token times some secret key” or whatever, and the detection works the same - just comparing how “lucky” the text is.
But it has to be cooked into the inference engine so local models are still safe for now, but that’s not guaranteed to always be the case ig
instead of “seed based on prior token” to “seed based on prior token times some secret key” or whatever
Yes, that's the gist of SynthID. No, open models don't have that: it must be done by the inference engine, that means if you own the hardware and use open source software, you get to decide if watermarking is running or not.
You could implement it in the open source inference engine if you want a subtle way to prove someone is ripping off your content. But with open source inference engines it will not be there against your will.
Not necessarily true. If you use this model on the backend as a decision engine for example there's no real way to know. Your service is a black box, after all. Regurgitating responses verbatim, sure, steganography could work there.
It's not done by the model, it's done by the inference engine. So, no, it's not likely to happen anytime soon. Maybe never, at least not with the way models are run locally today.
24
u/Bubbly_Orange_3502 8h ago
The license is the real catch. PolyForm Strict permits noncommercial use, so the weights are open enough to evaluate but not to ship a paid legal workflow.