MIME-Version: 1.0
References: <CAKAnmm+tbPMdP8ccrJ-o_LVgC6ADdOEoh2=J+zyWNLab6B3+_Q@mail.gmail.com>
 <c7320b248d8b6294a325f87fa9ae98ebbd68f185.camel@cybertec.at> <aae1616a4ebf8eb129b2510c75d4c335a028d623.camel@cybertec.at>
In-Reply-To: <aae1616a4ebf8eb129b2510c75d4c335a028d623.camel@cybertec.at>
From: David Rowley <dgrowleyml@gmail.com>
Date: Fri, 19 Jul 2024 01:33:42 +1200
Message-ID: <CAApHDvrsbj-hCUhB=N+Hbzm2e0a5AjCe6MbB3KMgpDEF15q5CQ@mail.gmail.com>
Subject: Re: Planet Postgres and the curse of AI
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Greg Sabino Mullane <htamfids@gmail.com>, pgsql-general <pgsql-general@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://www.postgresql.org/message-id/CAApHDvrsbj-hCUhB%3DN%2BHbzm2e0a5AjCe6MbB3KMgpDEF15q5CQ%40mail.gmail.com>
Precedence: bulk

On Fri, 19 Jul 2024 at 00:31, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
> Perhaps there could be a way to report misleading, bad content and a policy that says
> that you can be banned if you repeatedly write grossly misleading and counterfactual
> content.  Stuff like "to improve performance, set fast_mode = on and restart the database".

As a first step, maybe it's worth just privately writing to the
offenders telling them what's been seen, giving them a chance to
improve and letting them know what they're doing isn't going
unnoticed.  If I was doing this and someone pointed out lots of silly
mistakes with something I'd published, I'd be very embarrassed and I'd
reconsider my blog writing approach.

It might also be worth considering if we want to have a policy on LLM
usage in https://www.postgresql.org/about/policies/planet-postgresql/
.  If we want to disallow blogs written by LLMs then we'd need to be
careful about how we define that as doing something like using an
LLM-based spell checker does not seem like it should be disallowed.
But to what degree exactly should that be allowed?

David