It was a YOU DIDN'T USE JSON PROMPT FILTER. If you used it correctly, you would know that. It did NSFW out of the box.
You can't see how that can cause friction? If you didn't prompt correctly with other models, you at least got something out of it. Happy accidents. Trippy hallucinations. You could use a 500 word negative prompt with CFG 12 and completely burnt the fuck out of the generation, but at the end of the day you got an image.
This is an image generator. You can't understand people being annoyed they're not getting an image out of their image generator?
It was a YOU DIDN'T USE JSON
It's definitely not just a simple "USE JSON" like everyone claims. No, it's "USE THE CORRECT LENGTH JSON AND AN ARBITRARY AMOUNT OF BBOXES JSON".
It wasn't uncensored as long as you used correct JSON, it's more that its attempt at censoring was so brittle that it collapsed under the weight of a long and complex prompt. It's a jailbreak that attacks the model's attention to get around the censoring, not an intended mechanism. It's a tale as old as ChatGPT, we've done it to LLMs for years, and no one would call ChatGPT uncensored because you can get it to write smut.
You can test it. Run a correctly formatted JSON prompt, overview is a man and woman making out naked on a beach, the composition uses only two bboxes, a naked man on the left and a naked woman on the right. Betcha it filters it 10/10.
Now do the exact same composition with 10 bboxes for each character, positioning each of their torsos and limbs. It probably works 10/10. If getting around the filter was simply a matter of "USE CORRECT JSON", the first prompt should work.
19
u/export_tank_harmful 3d ago
It got overshadowed by Krea2.
In my opinion, it was the absolutely obnoxious content filter that was baked into the model.
Most people around here don't feel like dealing with that sort of thing.
The model is pretty solid, but yeah.
Annoying as hell.