Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1shFAp-00F8oc-KU for pgsql-general@arkaria.postgresql.org; Thu, 22 Aug 2024 21:16:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1shFAn-005e54-Nw for pgsql-general@arkaria.postgresql.org; Thu, 22 Aug 2024 21:16:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1shF7c-005Ywm-UV for pgsql-general@lists.postgresql.org; Thu, 22 Aug 2024 21:13:33 +0000 Received: from mail-vk1-xa2b.google.com ([2607:f8b0:4864:20::a2b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1shF7a-000xUC-C5 for pgsql-general@lists.postgresql.org; Thu, 22 Aug 2024 21:13:32 +0000 Received: by mail-vk1-xa2b.google.com with SMTP id 71dfb90a1353d-4fd19da17dfso72550e0c.1 for ; Thu, 22 Aug 2024 14:13:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=xzilla-net.20230601.gappssmtp.com; s=20230601; t=1724361208; x=1724966008; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=yo8FXvITnlSgZ75yj5hV0j20df/U+kXRXAvW9lt/j9Q=; b=HuzOxEQXRwDSttg+nbeQs47F6VVluL7sVmHFNtLKclYGNP/qGxVQix3i7p7VxC0apr PFkdP1Y0uQ5fIhv9R1SRg/KJHFWSh/0X6OP0JaVaO6nW29XhxK2jgIwsnC2MgM7ktftd x0GxQ6NrZDdJCapUq9YdkK2IqF3dD0+T4TStOFKP1TjTHHgxpAOJOZO+0tmt9dztNNje O/Px9scaAfgCDuot0KvIzq3qv6hUSptgTsEpHbht7eDrBd+QOyZNGVdanUd9Skktkgmn cS5skYEZO++vP9HV32OusrrvP1xrdqxkEv+cv/ts06qlSAWtnQJhIE9syPWl3segfFOT ZYpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724361208; x=1724966008; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=yo8FXvITnlSgZ75yj5hV0j20df/U+kXRXAvW9lt/j9Q=; b=ML/qcz/jB4APE/nGREmYRzw5aW57hICDVTsszdDNS7MHcnEywHESxfWV5K9Y5pUAU6 WUvsL7La+DCatpfv0HFtY1OCf2UKSQP4c4pZOXBeBzKFNrQG2mb35woBmuB0s7m97291 JuZszkic+mdJMHRVQU+VwBsO7rjyBpl9kcTRKcIrJBlZ43lJoSa2r+HToOIdjsg+FciR Y7TADkCmEniB3xaU3BDAtVUMOC8UVsQLN9e2xLarUzIaoXRAssk3Zgp2P032dKVwKrI/ URndSmsz8HYEPOkmS1BKLGLqyNvB8tXwr/X1OrJrMSycBbbvIfPjJXw/7/W/q0IeRxcM xbgA== X-Forwarded-Encrypted: i=1; AJvYcCUHy1mQ3fpPIt2slZ2XFLvZRjM48pL27BZwTybbFasJf6k/BGgZkJyMgOUyeUB6Szv/TdkCpFAQn69oMCO1@lists.postgresql.org X-Gm-Message-State: AOJu0YxyOm4S6pENjYlMQ+OKTsHvWBd+pbOikyheTKmHtsx0vDuPTgvT C551c7CBJ0YKsiqrmv6frTbWudNlmhAmc/f0kaKrRjrQHOCqmTLOwyCaILn7RLDg8VyYIEGAITS 8x/f2+2hPWhw0WyMqE00hCitF/Vq99kSm1IFasw== X-Google-Smtp-Source: AGHT+IHiKNTdZuNw1LU4bCNyK2U2jx7DiTjfMLdfzZjGqbWhQkumG1gnjFKa+BDzsQICZnn83J0mtqE6w3sk1jrHdyg= X-Received: by 2002:ac5:c9b5:0:b0:4f9:a30:d855 with SMTP id 71dfb90a1353d-4fd045690b1mr3216325e0c.3.1724361207951; Thu, 22 Aug 2024 14:13:27 -0700 (PDT) MIME-Version: 1.0 References: <54c731a5825ba6da520ada38597c03605aba6b09.camel@cybertec.at> <33fd1eed05bb498e7110407e1d738873476844f2.camel@cybertec.at> In-Reply-To: From: Robert Treat Date: Thu, 22 Aug 2024 17:13:17 -0400 Message-ID: Subject: Re: Planet Postgres and the curse of AI To: Greg Sabino Mullane Cc: Avinash Vallarapu , Laurenz Albe , David Rowley , pgsql-general Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Aug 20, 2024 at 8:33=E2=80=AFAM Greg Sabino Mullane wrote: > > On Tue, Jul 23, 2024 at 12:45=E2=80=AFPM Avinash Vallarapu wrote: >> >> However, I do agree with Lawrence that it is impossible to prove whether= it is written by AI or a human. >> AI can make mistakes and it might mistakenly point out that a blog is wr= itten by AI (which I know is difficult to implement). > > > Right - I am not interested in "proving" things, but I think a policy to = discourage overuse of AI is warranted. > >> People may also use AI generated Images in their blogs, and they may be = meaningful for their article. >> Is it only the content or also the images ? It might get too complicate= d while implementing some rules. > > > Only the content, the images are perfectly fine. Even expected, these day= s. > >> >> Ultimately, Humans do make mistakes and we shouldn't discourage people a= ssuming it is AI that made that mistake. > > > Humans make mistakes. AI confidently hallucinates. > I think this is a key point, and one that we could focus on for purposes of discouragement. Ie. "Blogs that are found to repeatedly post incorrect information and/or AI style hallucinations may be restricted from contributing to the planet postgres feed. This will be determined on a case by case basis." While it is likely impossible to come up with a set of rules that will satisfy some of the more legalistic folks among us, this would be a simple warning that would at least encourage folks to make sure they aren't posting bad information and leave a door open for enforcement if needed. And yes, this assumes that the folks running planet will enforce if needed, though I don't think it requires heavy policing at this point. Robert Treat https://xzilla.net