From: Oghenovo Usiwoma <eunovo9@gmail.com>
To: nt yl <wrapperband@googlemail.com>
Cc: bitcoinmechanic@ocean.xyz, bitcoindev@googlegroups.com
Subject: [bitcoindev] Re: AI-assisted drafts and disclosure
Date: Thu, 20 Nov 2025 18:48:02 +0100 [thread overview]
Message-ID: <CAOCjZ9RmtKWALV033EENs=wzt43GUG9k4mOeJkAzvyp2e2xj9w@mail.gmail.com> (raw)
In-Reply-To: <CAGvrRVJaWUzmiCbOVjh9A9wD75f1LvGrBAwh-1+HtODN-07CQA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2166 bytes --]
> Clear disclosure of AI assistance as a process note, not a stigma.
I agree with you, but I think disclosure of AI assistance will be treated
as "stigma", even if that was not its intention. This is my issue with the
"AI-label". If I use AI for research, do I have to add "AI label" to my
BIP? at what point do I have to add the label?
- Novo
On Thu, Nov 20, 2025 at 1:16 PM nt yl <wrapperband@googlemail.com> wrote:
> Hi Oghenovo Usiwoma and Bitcoin Mechanic,
>
> You wrote:
>
> In my humble opinion, I believe that humans will continue to use the
> easiest method available to them to achieve their goals. If we agree that
> humans will do this, then there will be a lot of AI-assisted content. If I
> did write an AI-assisted BIP draft, why would I add this "AI-label" to my
> BIP when I know that it will cause reviewers to ignore it?
>
> As a disabled person who uses AI tools, my view is that AI will soon be
> part of most serious workflows, much like reading the manuals and prior
> discussions is today. Used well, it can summarise long threads, prioritise
> issues, deduplicate proposals, and help check code for obvious bugs.
> Refusing to use any such tools can be a step backward in productivity.
>
> The key is how we use them. I would support:
>
> -
>
> Clear disclosure of AI assistance as a process note, not a stigma.
> -
>
> Strong norms that final authorship, technical accuracy, and
> accountability rest with the human proposer.
> -
>
> Encouraging A.I. for review support, not for replacing understanding.
>
> This balances transparency with practical benefits and keeps the bar on
> rigour where it belongs.
>
> Best,
> Wrapper
>
> https://www.zerogpt.com/ 0% A.I.
>
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAOCjZ9RmtKWALV033EENs%3Dwzt43GUG9k4mOeJkAzvyp2e2xj9w%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 2923 bytes --]
prev parent reply other threads:[~2025-11-21 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 12:16 'nt yl' via Bitcoin Development Mailing List
2025-11-20 17:48 ` Oghenovo Usiwoma [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOCjZ9RmtKWALV033EENs=wzt43GUG9k4mOeJkAzvyp2e2xj9w@mail.gmail.com' \
--to=eunovo9@gmail.com \
--cc=bitcoindev@googlegroups.com \
--cc=bitcoinmechanic@ocean.xyz \
--cc=wrapperband@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox