public inbox for [email protected]
help / color / mirror / Atom feedFrom: David Rowley <[email protected]>
To: Laurenz Albe <[email protected]>
Cc: Greg Sabino Mullane <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Planet Postgres and the curse of AI
Date: Fri, 19 Jul 2024 01:33:42 +1200
Message-ID: <CAApHDvrsbj-hCUhB=N+Hbzm2e0a5AjCe6MbB3KMgpDEF15q5CQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAKAnmm+tbPMdP8ccrJ-o_LVgC6ADdOEoh2=J+zyWNLab6B3+_Q@mail.gmail.com>
<[email protected]>
<[email protected]>
On Fri, 19 Jul 2024 at 00:31, Laurenz Albe <[email protected]> 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
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], [email protected]
Subject: Re: Planet Postgres and the curse of AI
In-Reply-To: <CAApHDvrsbj-hCUhB=N+Hbzm2e0a5AjCe6MbB3KMgpDEF15q5CQ@mail.gmail.com>
* 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