public inbox for [email protected]  

help / color / mirror / Atom feed

From: Adrian Klaver <[email protected]>
To: Greg Sabino Mullane <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: Planet Postgres and the curse of AI
Date: Wed, 17 Jul 2024 13:48:14 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKAnmm+tbPMdP8ccrJ-o_LVgC6ADdOEoh2=J+zyWNLab6B3+_Q@mail.gmail.com>
References: <CAKAnmm+tbPMdP8ccrJ-o_LVgC6ADdOEoh2=J+zyWNLab6B3+_Q@mail.gmail.com>

On 7/17/24 10:21, Greg Sabino Mullane wrote:
> I've been noticing a growing trend of blog posts written mostly, if not 
> entirely, with AI (aka LLMs, ChatGPT, etc.). I'm not sure where to raise 
> this issue. I considered a blog post, but this mailing list seemed a 
> better forum to generate a discussion.
> 

> 
> Do we need a policy or a guideline for Planet Postgres? I don't know. It 
> can be a gray line. Obviously spelling and grammar checking is quite 
> okay, and making up random GUCs is not, but the middle bit is very hazy. 
> (Human) thoughts welcome.

A policy would be nice, just not sure how enforceable it would be. How 
do you differentiate between the parrot that is AI and one that is 
human? I run across all manner of blog posts where folks have lifted 
content from the documentation or other sources without attribution, 
which is basically what AI generated content is. AI does like to 
embellish and make things up(ask the NYC lawyer suing the airlines about 
that), though that is a human trait as well.

> 
> Cheers,
> Greg
> 

-- 
Adrian Klaver
[email protected]

view thread (12+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Planet Postgres and the curse of AI
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox