public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Nicolas Dorier <nicolas.dorier@gmail•com>
To: Peter Todd <pete@petertodd•org>
Cc: Gregory Maxwell via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Core Devs : can you share your thoughts about all BIPs on this website ?
Date: Sat, 22 Aug 2015 01:58:50 +0900	[thread overview]
Message-ID: <CA+1nnrnqS6+9vEB0KBUpfaF6q2CTXPy-2M8JkHXXm5nXzmx-Lw@mail.gmail.com> (raw)
In-Reply-To: <3B2A58B3-6AF6-4F1C-A6FA-7AEC97F48AD0@petertodd.org>

[-- Attachment #1: Type: text/plain, Size: 2304 bytes --]

My UX skills are lacking a bit. You can edit all your thoughts about each
BIP, HTML is accepted, so you can link to other posts you made somewhere
else.
When you click on a cell in the grid, it forward you to the page that the
dev edited for this BIP.

This website is not only to say "approve", "disapprove", nor is it about a
formal process for reaching agreement.
This is a tool, a portal, which educates people, and permit you to link all
of your thoughts about the various BIP and show it to others.

With the opinions browse able from the same website, you will notice in a
gleam as soon as one of those proposal reach consensus. (I think SIPA's BIP
has a chance to do so, but nobody knows it yet)
Sadly, the most controversial is a BIP, the noisier it is, at the expense
of those which are not. (like sipa's one).

It irritates me a lot that the debate in public mind is "XT or not" /
"Bigger blocks or not", when in reality there is lots of different
proposals that might also reach consensus but are lost in the noise.
I will add any BIP that at least one voter approve and want to push forward.
I plan to add merchants/wallet providers/mining pools later.


On Fri, Aug 21, 2015 at 6:35 PM, Peter Todd <pete@petertodd•org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
>
>
> On 21 August 2015 02:31:51 GMT-07:00, Btc Drak <btcdrak@gmail•com> wrote:
> >On Fri, Aug 21, 2015 at 10:29 AM, Peter Todd via bitcoin-dev
> ><bitcoin-dev@lists•linuxfoundation.org> wrote:
> >> What might be valuable is to ask devs to explain what their threat
> >models are, what should be at the root of their thinking about the
> >blocksize.
> >
> >That's exactly what the "Technical Opinion" column is for.
>
> What if could be used for; theres value in being more explicit.
> -----BEGIN PGP SIGNATURE-----
>
> iQE9BAEBCgAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJV1vDG
> AAoJEMCF8hzn9Lncz4MIAIMtLLA4q7KJiwrYrpjFWme1ys9iyPZiADJGQWG3qKlH
> Q4pEcwWt69jfTUCjLYfegsDW4eEMarejs568iSF70hvGB4OPWrYK3YiM1cWlWtDD
> seN3G/4dJjehL7h1Nz+/OTjTlePkguHctRlJTavel8sI7fg356iMJc1Ggm5Q1ZFl
> CLrivr/CEO7Qk9Uo5ewhnwConKjLygSyv67SSaMJW7pZB06uTX6M3lk11c/RB/C6
> JKPqxkvOmNIX9U8S/G3Y2pYf3/up72IhP0Ugp31iOsz629B2WvEsDYu/0SP61+oZ
> za9HrP2g8OsxVq6SUD3MukmbRVKklvcnro4vk5sOlYI=
> =Jfl+
> -----END PGP SIGNATURE-----
>
>

[-- Attachment #2: Type: text/html, Size: 3068 bytes --]

  parent reply	other threads:[~2015-08-21 16:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19  4:57 Nicolas Dorier
2015-08-21  3:10 ` Btc Drak
2015-08-21  4:45 ` Gregory Maxwell
2015-08-21  5:10   ` Nicolas Dorier
2015-08-21  9:09     ` Btc Drak
2015-08-21  9:32       ` Peter Todd
2015-08-21  9:29   ` Peter Todd
2015-08-21  9:31     ` Btc Drak
2015-08-21  9:35       ` Peter Todd
2015-08-21 10:55         ` Yifu Guo
2015-08-21 11:28           ` Btc Drak
2015-08-21 12:28             ` Yifu Guo
2015-08-21 13:18               ` Oliver Egginger
2015-08-21 13:34                 ` Will Madden
2015-08-21 17:31                   ` Oliver Egginger
2015-08-21 18:07                     ` Will Madden
2015-08-22  3:02             ` odinn
2015-08-21 16:58         ` Nicolas Dorier [this message]
2015-08-21  3:38 Nicolas Dorier
2015-08-21  3:45 ` Eric Lombrozo
2015-08-21  3:54   ` Nicolas Dorier

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=CA+1nnrnqS6+9vEB0KBUpfaF6q2CTXPy-2M8JkHXXm5nXzmx-Lw@mail.gmail.com \
    --to=nicolas.dorier@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=pete@petertodd$(echo .)org \
    /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