From: Yuval Kogman <nothingmuch@woobling•org>
To: "/dev /fd0" <alicexbtong@gmail•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Covenants Support - Bitcoin Wiki
Date: Sat, 7 Dec 2024 02:42:44 +0100 [thread overview]
Message-ID: <CAAQdECALHHysr4PNRGXcFMCk5AjRDYgquUUUvuvwHGoeJDgZJA@mail.gmail.com> (raw)
In-Reply-To: <6d375199-834e-4630-8b5c-fcc5ed137cb1n@googlegroups.com>
On Sat, 7 Dec 2024 at 02:10, /dev /fd0 <alicexbtong@gmail•com> wrote:
>
> There are 7 options available to share opinion on an opcode and only 2 include community support. If a developer wants to ACK a proposal it is possible to use to 'prefer' or 'acceptable' and 'no' for NACK.
the 6 options (+ "evaluating", which is not in the space) represent
only a subset of the product of two independent dimensions:
- a given dev's (hopefully reasoned) opinion on the technical merit of
a proposal
- and their (speculative, vibes based) opinion about community support.
> At the end of the day bitcoin developers build for community so if someone wants to play safe and use 'deficient' and 'wanting', its their choice and I think we should allow such freedom to express themselves.
to allow that full freedom to express themselves 8 options seem
necessary, not counting "evaluating":
{ no, weak, acceptable, prefer } x { sufficient community support,
insufficient }
(or alternatively, { no, weak, acceptable } is the technical merit
dimension, and then "prefer" seems redundant?)
anyway, supposing all pairs of values were expressible, the latter is
confounded or arguably even ill defined see
https://en.wikipedia.org/wiki/Keynesian_beauty_contest (and this is
exacerbated by the fact that the two values are combined into a single
dimension, e.g. if i strongly prefer something but it lacks community
support), so to allow people to e.g. only express a technical opinion,
and abstain from speculating on community support, we'd want:
{ ⊥, weak, acceptable, prefer } x { ⊥, sufficient, insufficient }
(where evaluating = (⊥, ⊥))
finally, even if the full set of possibilities was expressible, and
assuming the infinite regress of speculating on others' opinions about
others opinions was not an issue, it would still not be totally
orderable, so the color scheme is arguably misleading
both the partial ordering and the speculative nature add a lot of
ambiguity, i.e. different answers are likely to mean different things
to different respondents and to people reading the table
--
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/CAAQdECALHHysr4PNRGXcFMCk5AjRDYgquUUUvuvwHGoeJDgZJA%40mail.gmail.com.
next prev parent reply other threads:[~2024-12-07 1:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 14:08 /dev /fd0
2024-12-06 21:45 ` Jonas Nick
2024-12-07 0:29 ` /dev /fd0
2024-12-07 1:42 ` Yuval Kogman [this message]
2024-12-09 20:13 ` Anthony Towns
2024-12-09 20:45 ` Brandon Black
2024-12-11 13:28 ` Anthony Towns
2024-12-11 15:11 ` Brandon Black
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=CAAQdECALHHysr4PNRGXcFMCk5AjRDYgquUUUvuvwHGoeJDgZJA@mail.gmail.com \
--to=nothingmuch@woobling$(echo .)org \
--cc=alicexbtong@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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