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 1sUBZX-0017yh-Jg for pgsql-general@arkaria.postgresql.org; Wed, 17 Jul 2024 20:48:23 +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 1sUBZV-0059Gz-OQ for pgsql-general@arkaria.postgresql.org; Wed, 17 Jul 2024 20:48:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sUBZU-0059FR-TE for pgsql-general@lists.postgresql.org; Wed, 17 Jul 2024 20:48:21 +0000 Received: from fhigh8-smtp.messagingengine.com ([103.168.172.159]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sUBZR-00057D-Pk for pgsql-general@lists.postgresql.org; Wed, 17 Jul 2024 20:48:20 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailfhigh.nyi.internal (Postfix) with ESMTP id F1EE81140145; Wed, 17 Jul 2024 16:48:15 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 17 Jul 2024 16:48:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1721249295; x=1721335695; bh=JlCGf0dNYh+0zH1Rwa6QTZqaos/3qoMl6VTnxoy/pqU=; b= HtoO34Z7zETiCtb3M3kgfIZnfBte4RZQ4suK24MNVPOr6HirClWhpB3s8jKBSO/x W00gxkZ/aePvTonoFL8a5krNHFrahx9qmj6ZmToOW5gO40XV686GAG9UyXoLOS/i oetuGzENJua+0VSsLqUx9CFanNe3rUfR/nhDwUXHSX5T9z3BvwtKFzpjfkZloIIV JK/CMoMgN2F2FyCNI90i2n+FXL0q30RFWLYZQSL9Rs7gJXnUiZeCnbIOURqyrgGz SL+GTrGfyIvR8ocSZlI/n1JyB7kNwEUupwWdAyICXNzuwuxCdQ5mYZgT1z6VsMjP SYoAFXD8JxOI4W4rKOlomA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1721249295; x= 1721335695; bh=JlCGf0dNYh+0zH1Rwa6QTZqaos/3qoMl6VTnxoy/pqU=; b=X cN9Y48DT6FU8dwGQ+JHGruB5pG2/Ja1YhEjUCHXMlxYeHLbm7iH83XaraQf37Ksa zMuegAJ0niKi19/2cQYYVTiAOm7f7ZvHjGAUbXgI4aVOeFO86zYQEzr26y6CD8ex f7aLe84dpVr/wEzEhT2wp2UJg+R3VvbNtzexP8FDsFar37vz94ahpgg/6o+RO8MS 0iTRVu6xz8p0p0Rxb9YhkS7ExPhXIJMzWmtneadpu7TJz1l0VLesRBatNoYLDlpl NGForBj92IMR+VoYvoMxB41eaBIah6p/qYMjBmnWMMGG316DgWlKdPJk2UKLz+XG Eg3g2JQHKgtA4lKDp9V/w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrgeejgdeivdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepkfffgggfuffvfhfhjggtgfesthekre dttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhl rghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeffleegieefgf evudehtdfhkeeutdffjeevgeffgeejvedthefgudeiteefheejheenucevlhhushhtvghr ufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvg hrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 17 Jul 2024 16:48:15 -0400 (EDT) Message-ID: <5ea4e73d-944c-4c3d-b99f-af0c8f6b4f98@aklaver.com> Date: Wed, 17 Jul 2024 13:48:14 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Planet Postgres and the curse of AI To: Greg Sabino Mullane , pgsql-general References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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 adrian.klaver@aklaver.com