Answered An official view on AI posts

[roydan]

This is more of a question than a request, although I'm sure my views on the matter are clear to some.

I think that AI is awesome for phrasing and refining content but it also makes it very easy to post 100s of content-less comments an hour.

Where is the line drawn on that matter?

 

[UnusualSubstance]

Blatant AI copy and paste jobs not relevant to the original poster's question should be removed, imo.

Maybe a warning for "Inappropriate AI Usage"?

 

[TheVigilante]

Blatant AI copy and paste jobs not relevant to the original poster's question should be removed, imo.

Maybe a warning for "Inappropriate AI Usage"?

This!

Since we have many members of the forum who are good at spotting AI garbage and reporting so no one can get away

 

[Champagne]

It's fine for spell checking and such, but just to inflate the post count is against the rules. If you see any of these posts then please report them. Thank you.

 

[Rem]

I think
as a general census should be at the very least
Google Bard/Gemini generated post should be banned and the user warned for straight out using trash.
At least until they improve their model

 

[Zwielicht]

I whole-heartedly agree that there needs to be an official stance.

I have no issues with people using it to translate their posts or clean up their spelling and grammar. The real issue comes from when it’s just straight-up copy/pasted.

If it’s blatant like that, definitely report it and a warning (which I’m calling “notices” here) will be sent out.

I’ll work on writing up a site guide about it and adding a warning in. I’ll update this thread once I’m done.

 

[Zwielicht]

Rules - Our Stance On AI Posts

AI-generated content is everywhere these days, there's no denying that. Right now, even some of the biggest forums have an influx of AI-generated content. At the time of writing this, Office Outlaw does not have this problem, but as this forum grows, we will no doubt encounter this issue. What...

officeoutlaw.com

I'm making a warning on it now, but I'll mark this as resolved.