Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SoGWe-0002kf-O9 for bitcoin-development@lists.sourceforge.net; Mon, 09 Jul 2012 16:09:28 +0000 X-ACL-Warn: Received: from nm15.bullet.mail.ne1.yahoo.com ([98.138.90.78]) by sog-mx-2.v43.ch3.sourceforge.com with smtp (Exim 4.76) id 1SoGWY-0002on-Uk for bitcoin-development@lists.sourceforge.net; Mon, 09 Jul 2012 16:09:28 +0000 Received: from [98.138.90.48] by nm15.bullet.mail.ne1.yahoo.com with NNFMP; 09 Jul 2012 16:09:17 -0000 Received: from [98.138.87.8] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 09 Jul 2012 16:09:17 -0000 Received: from [127.0.0.1] by omp1008.mail.ne1.yahoo.com with NNFMP; 09 Jul 2012 16:09:17 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 406079.64201.bm@omp1008.mail.ne1.yahoo.com Received: (qmail 75216 invoked by uid 60001); 9 Jul 2012 16:09:17 -0000 X-YMail-OSG: W.nUNAMVM1kr28Ab_JOr7v78.E9jHAT.7E9WJJGj1oox_W9 REbP1ee1AXZRt357DYafsPhp_QyC9QQA58SwObEKXn3I5.JWtT5vWytBpNdg GvIH561jMC7_SfBRdMnHIS25wPpupkDF98oOIvWUaHofbmxeT_xwLn.zOnJY U51z.G4GXeWwOs0TK4llBV4U746Y_KQKyU7EY1QOgdHJMqUoDxUoWG3u4Lfz T.XSUiht66uEl0iVXzsWiiKQLAIVl5xM4XqmOEfcZjcv6D3HKta7S.ODFTLt eVPXpQHLoRwjY9w_K0dJoIdQT5IMzNj6wGOnwQQ0ns.WCkln.aWHjvjmGoig .ulO3HBoKaWBKB4mHOlLy0yDVFKfSVSCxUg4_8BU7zkZXJJhZz0Bob1ubzKZ _obLkGkKyJd8XHEqLmCT2cNwq2kukbeEezzq9DUQboQwuEGog5kPvZcQMsf0 DbMIFQCMS1U1AL25ZU..RPrsSDC6qFb26jp.Ml.TMx.XBLk4GVzWxOATXIMk TKKOTEVl5trJbhsrHY54qxDz6sxIRngtsRWAyJqLwdd7pnElMifP8NTlK7dK EzGNaRy1MQcX54Oy6ulY_iLAMQK2LWQhqVcE- Received: from [178.5.23.109] by web121006.mail.ne1.yahoo.com via HTTP; Mon, 09 Jul 2012 09:09:17 PDT X-Mailer: YahooMailWebService/0.8.120.356233 References: <1341849295.94710.YahooMailNeo@web121003.mail.ne1.yahoo.com> Message-ID: <1341850157.18601.YahooMailNeo@web121006.mail.ne1.yahoo.com> Date: Mon, 9 Jul 2012 09:09:17 -0700 (PDT) From: Amir Taaki To: "bitcoin-development@lists.sourceforge.net" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.1 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [98.138.90.78 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (zgenjix[at]yahoo.com) -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.0 FSL_FREEMAIL_2 FSL_FREEMAIL_2 0.0 FSL_FREEMAIL_1 FSL_FREEMAIL_1 X-Headers-End: 1SoGWY-0002on-Uk Subject: Re: [Bitcoin-development] Random order for clients page X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Amir Taaki List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2012 16:09:28 -0000 JS randomisation is bad. People shouldn't need JS to view a webpage.=0A=0AO= nly you have a problem with this page. I don't see why Bitcoin-Qt needs to = be first either when it dominates the front page. It is perfectly fine as i= t is.=0A=0AYou are not a developer of any alternative clients, and this is = a webpage for Bitcoin clients. I have made a change to remove a source of d= isputes, and make the process more fair and equal. Your suggestion to remov= e the clients page is your bias towards thinking that there should be only = one Bitcoin client that everyone uses (the one which you contribute towards= ).=0A=0AIf you want to suggest removing the clients page, then fine, lets a= lso remove all reference to Bitcoin-Qt from the front-page and turn it into= a http://bittorrent.org/ style website.=0A=0AFact is that the other client= s are rapidly becoming stable and mature, and the ecosystem is diversifying= . The argument that the other clients were not up to scratch held maybe a f= ew months ago, but not now.=0A=0A=0A=0A----- Original Message -----=0AFrom:= Gregory Maxwell =0ATo: Amir Taaki = =0ACc: "bitcoin-development@lists.sourceforge.net" =0ASent: Monday, July 9, 2012 5:04 PM=0ASubject: Re: [Bi= tcoin-development] Random order for clients page=0A=0AOn Mon, Jul 9, 2012 a= t 11:54 AM, Amir Taaki wrote:=0A> Took me a while, but = finally got it working.=0A> Entries on the clients page are randomly ordere= d when the page is generated.=0A> https://github.com/bitcoin/bitcoin.org/co= mmit/6850fc8c83494d6ec415ea9d36fb98366373cc03=0A> We should regenerate the = page every 2 days. This gives fair exposure to all the clients listed.=0A= =0AIf you had authored this as a pull request rather than making the=0Achan= ge unilaterally I would have recommended leaving it so the=0Areference clie= nt was always first. I also would have suggested that it=0Ause JS randomiza= tion instead of jekyll in order to get more even=0Acoverage, though I think= thats a more minor point.=0A=0ASome people were concerned when this page w= as created that it would=0Ajust be a source of useless disputes.=A0 I think= its becoming clear that=0Athis is the case. I think the cost of dealing wi= th this page is=0Astarting to exceed the benefit it provides and we should = probably=0Aconsider removing it.=0A