From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id B7B319E7 for ; Thu, 20 Aug 2015 00:21:08 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-io0-f176.google.com (mail-io0-f176.google.com [209.85.223.176]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 91EA610D for ; Thu, 20 Aug 2015 00:21:07 +0000 (UTC) Received: by iods203 with SMTP id s203so28590188iod.0 for ; Wed, 19 Aug 2015 17:21:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yFUZBiePVG6N3dCDaXu71WbAbys1+ccn9OWgmFpAGQ0=; b=ZON9eY9WPD1+tDDaOsKPJT4jUQnyiZVCFqO5RpwwQBpfNPYIvxTIRu4B8W5jVXiX/R +6TZYzIGk/w5LXjD3w6UWzwUtfFUu5AqdOMR+S4zj/e7cISvyk2fdbO1KtMIrPMnfR4I hvmeqjwMKYKywZjZY/hyC68WWs06IzLG40VJhDGzs6aRXrQ0JK8pcC7Br2PNtSZbhnJn h/9OxUQOEmxcLuXMlzW5z1w55mIQhVWh6zFaTx5iaY76MzjVPKVyAoNCgPFlY7Hmxycg ny1+A5xcrPUZ7sxpkbDqLC2kcWutSRySXybSj94INaCzbJ81FbQKiYSd9cUmxHCOO6xb wHvA== MIME-Version: 1.0 X-Received: by 10.107.30.13 with SMTP id e13mr206297ioe.57.1440030067097; Wed, 19 Aug 2015 17:21:07 -0700 (PDT) Received: by 10.36.91.135 with HTTP; Wed, 19 Aug 2015 17:21:06 -0700 (PDT) In-Reply-To: References: Date: Wed, 19 Aug 2015 19:21:06 -0500 Message-ID: From: Bryan Bishop To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= , Bryan Bishop Content-Type: multipart/alternative; boundary=001a1141a5109d8638051db320dc X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] Separated bitcoin-consensus mailing list (was Re: Bitcoin XT Fork) X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2015 00:21:08 -0000 --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
On W= ed, Aug 19, 2015 at 3:59 AM, Jorge Tim=C3=B3n <bitcoin= -dev@lists.linuxfoundation.org> wrote:
Appa= rently that existed already: http://sourceforge.net/p/bitco= in/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&= #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 "glorious future" 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'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 "individual = developer's summaries of things they have found interesting over the pa= st 30-90 days or past year" 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.
- Bryan
http://heybryan.org/
1 512 203 0507
--001a1141a5109d8638051db320dc--