Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

just when the models started to be actually good. these policies need quarterly revisions at the current dynamics.


Assuming you're referring to the policies elsewhere that are overly permissive of model-generated code ;)


I'm referring to any policy actually; it cuts both ways. I'd actually suggest a per-model policy - e.g. personally I'd have much less doubts accepting Fable/Mythos patches than Sonnet ones. this is obviously unworkable, impossible to validate and excludes mixed-model workflows, but in spirit the 'smart' models/model mixes should be treated differently than the dumb ones. another case is one-liner (approximately) fixes - I wouldn't even bother to self-report these as AI generated.


Just 6 months before we get AGI!




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: