@francistrdev Now I'm even more confused than before!
This is my original comment that @dannwaneri references in his post.
Could you clarify, please? Do I have to mark all my posts with a disclaimer? That's not a problem for me. I just want to know. It seems a bit absurd, but I'll do it if it's mandatory to prevent my posts from going unread. I joined this community with the intention of sharing my experience with young developers and discussing with experienced developers like myself. Not that my way of building things is the best, it's my proven method after 40 years, and maybe someone might be interested in trying it. Why do I use AI to help me refine my posts? Because sometimes a simple translation loses the real meaning of what I'm trying to express in Italian, and I don't want to run the risk of appearing pedantic or arrogant. AI helps me with this because it understands the nuances of technical and spoken language. I believe that, as I wrote in the comment, a post should be judged based on its value (not so much technical), but rather its human value and its contribution to the community. Thanks for your attention.
I will add another consideration if it can be helpful.
Why not to decide a default predefined banner by DevTo to insert in the post so the bot checker can ignore it?
So it leave the decision to judge to the readers. They know it the post is done with the assistance of AI and and can judge by themself.
Another situation is for posts entirely written as spam by bots.
I add this a separate comment because is another topic to consider for me.
Thank you.
That's actually a cleaner solution than the current text disclaimer. A platform-native badge that signals AI assistance without requiring the author to write their own disclosure — standardised, consistent, machine-readable and visible to readers without being buried at the bottom of the post. @fm 's "detect quality not AI" and your banner idea are pointing at the same thing: structural signals rather than text enforcement. Worth putting directly in Francis's post as a suggestion since Ben and Jess are watching that thread.
Marco your situation is precisely the one that exposes the policy's weakest point. Using AI to bridge a language barrier — to make sure your 40 years of experience reads the way you intend it to in a language that isn't your first - is not what anyone meant by "AI-generated content."
But the disclosure requirement doesn't distinguish between those cases. For now: yes, add a one-line disclaimer. It's a low-cost way to protect your visibility until the guidelines catch up to the nuance.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
@francistrdev Now I'm even more confused than before!
This is my original comment that @dannwaneri references in his post.
Could you clarify, please? Do I have to mark all my posts with a disclaimer? That's not a problem for me. I just want to know. It seems a bit absurd, but I'll do it if it's mandatory to prevent my posts from going unread. I joined this community with the intention of sharing my experience with young developers and discussing with experienced developers like myself. Not that my way of building things is the best, it's my proven method after 40 years, and maybe someone might be interested in trying it. Why do I use AI to help me refine my posts? Because sometimes a simple translation loses the real meaning of what I'm trying to express in Italian, and I don't want to run the risk of appearing pedantic or arrogant. AI helps me with this because it understands the nuances of technical and spoken language. I believe that, as I wrote in the comment, a post should be judged based on its value (not so much technical), but rather its human value and its contribution to the community. Thanks for your attention.
Marco
I will add another consideration if it can be helpful.
Why not to decide a default predefined banner by DevTo to insert in the post so the bot checker can ignore it?
So it leave the decision to judge to the readers. They know it the post is done with the assistance of AI and and can judge by themself.
Another situation is for posts entirely written as spam by bots.
I add this a separate comment because is another topic to consider for me.
Thank you.
That's actually a cleaner solution than the current text disclaimer. A platform-native badge that signals AI assistance without requiring the author to write their own disclosure — standardised, consistent, machine-readable and visible to readers without being buried at the bottom of the post. @fm 's "detect quality not AI" and your banner idea are pointing at the same thing: structural signals rather than text enforcement. Worth putting directly in Francis's post as a suggestion since Ben and Jess are watching that thread.
Marco your situation is precisely the one that exposes the policy's weakest point. Using AI to bridge a language barrier — to make sure your 40 years of experience reads the way you intend it to in a language that isn't your first - is not what anyone meant by "AI-generated content."
But the disclosure requirement doesn't distinguish between those cases. For now: yes, add a one-line disclaimer. It's a low-cost way to protect your visibility until the guidelines catch up to the nuance.