MIME-Version: 1.0
In-Reply-To: <CABm2gDpYdBjyCB=Dor0eE-FdPv9PbVXzWyJf0BPyQ4SDm9VznQ@mail.gmail.com>
References: <CABm2gDpYdBjyCB=Dor0eE-FdPv9PbVXzWyJf0BPyQ4SDm9VznQ@mail.gmail.com>
Date: Wed, 19 Aug 2015 19:21:06 -0500
Message-ID: <CABaSBawX26u9XJRPdoYnPpSgG85P4pr917fjUuxhmPnO8Ek5rw@mail.gmail.com>
From: Bryan Bishop <kanzure@gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>, 
	Bryan Bishop <kanzure@gmail.com>
Content-Type: multipart/alternative; boundary=001a1141a5109d8638051db320dc
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Separated bitcoin-consensus mailing list (was Re:
 Bitcoin XT Fork)
Precedence: list

--001a1141a5109d8638051db320dc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 19, 2015 at 3:59 AM, Jorge Tim=C3=B3n <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Apparently that existed already: http://sourceforge.net/p/bitcoin/mailman=
/
> But technical people run away from noise while non-technical people
> chase them wherever their voices sounds more loud.
>

FWIW, and I mentioned this opinion in #bitcoin-dev on IRC, but I am
perfectly fine with receiving everything through a single mailing list. I
used to read the Wikipedia firehose of recent edits because I thought
that's how you were supposed to use the site. Edits per second eventually
reached beyond any reasonable estimate of human capacity and then I
realized what was going on. Any sort of "glorious future" for bitcoin with
hundreds of millions of users will also see this problem for future
developers, even if only 0.1% of that population are money-interested
programmers then that's 100,000 programmers to work with. I would never
want to turn off this raw feed. Having said that, I am somewhat surprise
that nobody has taken to weekly summaries of research and development
activity. Summarizing recent work is a valuable task that others can engage
in just by reading the mailing list and aggregating multiple thoughts
together, similar to release notes. I was also expecting to see something
like "individual developer's summaries of things they have found
interesting over the past 30-90 days or past year" digging up arcane
details from the mailing list archives, or more infrequent summaries of the
other smaller batched review emails. Digest mode mailing list consumption
is often recommended to those who are uninterested in dealing with low
signal-to-noise, but I suspect that summarizing activity would be more
valuable for this community, especially for the different cognitive niches
that have developed.

- Bryan
http://heybryan.org/
1 512 203 0507

--001a1141a5109d8638051db320dc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Aug 19, 2015 at 3:59 AM, Jorge Tim=C3=B3n <span dir=3D"ltr">&lt;<a href=
=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin=
-dev@lists.linuxfoundation.org</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div id=3D":3sw" class=3D"a3s" style=3D"overflow:hidden">Appa=
rently that existed already: <a href=3D"http://sourceforge.net/p/bitcoin/ma=
ilman/" rel=3D"noreferrer" target=3D"_blank">http://sourceforge.net/p/bitco=
in/mailman/</a><br>
But technical people run away from noise while non-technical people<br>
chase them wherever their voices sounds more loud.<br></div></blockquote></=
div><br>FWIW, and I mentioned this opinion in #bitcoin-dev on IRC, but I am=
 perfectly fine with receiving everything through a single mailing list. I =
used to read the Wikipedia firehose of recent edits because I thought that&=
#39;s how you were supposed to use the site. Edits per second eventually re=
ached beyond any reasonable estimate of human capacity and then I realized =
what was going on. Any sort of &quot;glorious future&quot; for bitcoin with=
 hundreds of millions of users will also see this problem for future develo=
pers, even if only 0.1% of that population are money-interested programmers=
 then that&#39;s 100,000 programmers to work with. I would never want to tu=
rn off this raw feed. Having said that, I am somewhat surprise that nobody =
has taken to weekly summaries of research and development activity. Summari=
zing recent work is a valuable task that others can engage in just by readi=
ng the mailing list and aggregating multiple thoughts together, similar to =
release notes. I was also expecting to see something like &quot;individual =
developer&#39;s summaries of things they have found interesting over the pa=
st 30-90 days or past year&quot; digging up arcane details from the mailing=
 list archives, or more infrequent summaries of the other smaller batched r=
eview emails. Digest mode mailing list consumption is often recommended to =
those who are uninterested in dealing with low signal-to-noise, but I suspe=
ct that summarizing activity would be more valuable for this community, esp=
ecially for the different cognitive niches that have developed.<br><div><br=
></div><div class=3D"gmail_signature">- Bryan<br><a href=3D"http://heybryan=
.org/" target=3D"_blank">http://heybryan.org/</a><br>1 512 203 0507</div>
</div></div>

--001a1141a5109d8638051db320dc--