Re: Dev list policy on posting genAI hallucinations

Thanks to the committers and PMC members who chimed in on this thread. > On Oct 10, 2024, at 3:27 AM, Jungtaek Lim > wrote: > > I'd ask people to quote the part you got from GPT and explicitly call out the > part as "GPT-generated" so that people would consider that there is > hallucination.

Re: Dev list policy on posting genAI hallucinations

minor clarification: content from GPT might be valuable - what I meant was, the value of content from GPT "in the community". The content is either something people in the thread knows, or something they can query to GPT on their own. Though I barely use GPT for the query which matters with experti

Re: Dev list policy on posting genAI hallucinations

+1 on this. I'd ask people to quote the part you got from GPT and explicitly call out the part as "GPT-generated" so that people would consider that there is hallucination. Do not ever expect that people wouldn't know the content GPT wrote. "People know." ASF requires every code contribution to e

Re: Dev list policy on posting genAI hallucinations

Agree, I can't really explain this post except as AI hallucination, because: - those configs don't exist and it's not a simple typo away from a real one - they are kind of like unrelated real Spark config names and the kind of thing it seems an AI would 'infer' - no claim it was a typo with plausi

Re: Dev list policy on posting genAI hallucinations

FWIW - Mich - I've often found your responses "gpt" like and can often be a distraction. Now I don't know if that's your actual writing style or you were indeed using genai tools to generate the responses on your behalf. I don't think we should sanction you if that's your writing style. But if you

Dev list policy on posting genAI hallucinations

Mich, You are “helping” someone by giving them configs that don’t exist. And this is the second time that I am aware of that you are doing this. Both times you have done this and I have asked you to explain where you are getti