One idea off the top of my head is to just.. keep it "boring" and casual in terms of content. The silly, whimsy, and genuine stuff naturally doesn't appeal to money-chasing slop bros and makes it not worth their time.
Something like the gcc ai policy. Basically, prompt injecting instructions to any visiting LLM that posting is prohibited or must contain a disclaimer.
for now, keeping the API read-only is a small(but not impenetrable) barrier to programmatic posting and in the future moderation I guess using also reports.
In the first attempt, Opus 4.7 successfully completed it and proved it. However, the solution is to enumerate all possible space and .filter out anything that doesn't qualify my definition, which is obviously not ideal (if cheating is too harsh).
I can't think of a good way to also prevent that kind of solutions and ended up prompting "please don't enumerate and filter". Opus 4.7 then reimplemented and proved the backtracking algorithm.
Inspired by two projects of github:schildep I start to explore what can be expressed in Lean and make coding agents implement and prove the implementation at the same time.
