public inbox for [email protected]
help / color / mirror / Atom feedFrom: Laurenz Albe <[email protected]>
To: Greg Sabino Mullane <[email protected]>
Cc: David Rowley <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Planet Postgres and the curse of AI
Date: Tue, 23 Jul 2024 17:50:59 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKAnmmJEZBCAb2E1BgCrTHKXu2TYqKOgTkANWbQ1mCLZBLeNgQ@mail.gmail.com>
References: <CAKAnmm+tbPMdP8ccrJ-o_LVgC6ADdOEoh2=J+zyWNLab6B3+_Q@mail.gmail.com>
<[email protected]>
<[email protected]>
<CAApHDvrsbj-hCUhB=N+Hbzm2e0a5AjCe6MbB3KMgpDEF15q5CQ@mail.gmail.com>
<CAKAnmm+v7Rby=QKs-TCDjr42tjazcndJOPw_6pZVFadU7v9rWw@mail.gmail.com>
<[email protected]>
<CAKAnmmJEZBCAb2E1BgCrTHKXu2TYqKOgTkANWbQ1mCLZBLeNgQ@mail.gmail.com>
On Tue, 2024-07-23 at 10:38 -0400, Greg Sabino Mullane wrote:
> > Why not say that authors who repeatedly post grossly counterfactual or
> > misleading content can be banned?
>
> Perhaps as you hint at, we need a policy to not just discourage AI-generated
> things, but also wrong/misleading things in general
I have been known to make mistakes in my blogs...
We shouldn't discourage people who happen to blog something wrong.
That's why I used strong verbiage like "grossly counterfactual".
Yours,
Laurenz Albe
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: <[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