Re: We should require AI disclosure
Goffi <[email protected]> Wed, 08 Jul 2026 12:26:56 +0200
| Newsgroups | gmane.network.jabber.standards-jig |
|---|---|
| Message-ID | <[email protected]> |
--===============6786826438210497731== Content-Type: multipart/signed; boundary="nextPartB2_N8RLnQSip-53ymwfkEA"; micalg="pgp-sha512"; protocol="application/pgp-signature" --nextPartB2_N8RLnQSip-53ymwfkEA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8"; protected-headers="v1" From: Goffi <[email protected]> To: XMPP Standards <[email protected]> Subject: Re: [Standards] Re: We should require AI disclosure Date: Wed, 08 Jul 2026 12:26:56 +0200 Message-ID: <[email protected]> In-Reply-To: <CAMJaV9=ci3RYuJZWGBh0j0gVmMQCyh602tghFW1RKh8xvDV2ug@mail.gmail.com> MIME-Version: 1.0 Hi Guus, Le mercredi 8 juillet 2026, 11:04:45 heure d=E2=80=99=C3=A9t=C3=A9 d=E2=80= =99Europe centrale Guus der=20 Kinderen a =C3=A9crit : > First, prior art. Goffi, you're the one with the most energy on this and > you're seeing it from the Council side. Would you be willing to take this > on? No I'm not. I'm already at the edge of burn-out and can't cope with anythin= g=20 more. Our editor/council chair said twice that he won't continue if we start to s= ee=20 too much AI slops in our inbox, and we do start to see submission made with= AI=20 (I don't qualify them as "slop" at all for the moment, but I already feel t= he=20 AI impact). We regularly see FOSS projects and other organisations complaining about th= e=20 wave a slop PRs. I think that this is a potential problem, and it's better to anticipate ( I= =20 think the English proverb is "better safe than sorry", but for this one I= =20 like more the French "Mieux vaut pr=C3=A9venir que gu=C3=A9rir"). If nobody else see an issue there, so just let it be. I have neither the ti= me=20 nor the energy to fight in endless debates for a simple suggestion to discl= ose=20 AI use. Best, Goffi --nextPartB2_N8RLnQSip-53ymwfkEA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEsNZvWyEnjW9SVudbKqmcu6xuKwwFAmpOJfAACgkQKqmcu6xu KwxHBAf/arQpeHGIkvZXAybN5vE3pQeLItWcoUfy0lBHoLONGnAReS+oGOlCYPZ/ dkHVoghr7hmTStNI6PwRTJIW+m067mQSXZOqRzb8/44pQKHf3/+DodkMsh2ACqlw C03HbOI6KRDm+SzSAggqXoWGzqYW/KfFKcvL0mxlp44Q848cMqH8Nwiisml8XY5j FwQ8eQd6Hd2EEmfRjdr6vc5HNzfMv6bKDRybpYQfrHt9SZEGifJ84NcJDtStnUGM E5wLlTMN1nSjtA5iQVdeXy6rcnvOOtxCgL0264JtMws/fmd5yy2DuzJNvGzUVaB6 zUnj+SyaP9GrdM5fXGRJfx6MLvqDvA== =rbvl -----END PGP SIGNATURE----- --nextPartB2_N8RLnQSip-53ymwfkEA-- --===============6786826438210497731== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Standards mailing list -- [email protected] To unsubscribe send an email to [email protected] --===============6786826438210497731==--