Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SoGzq-00054T-Nd for bitcoin-development@lists.sourceforge.net; Mon, 09 Jul 2012 16:39:38 +0000 X-ACL-Warn: Received: from wp303.webpack.hosteurope.de ([80.237.133.72]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1SoGzl-0004vZ-F6 for bitcoin-development@lists.sourceforge.net; Mon, 09 Jul 2012 16:39:38 +0000 Received: from 84-72-69-53.dclient.hispeed.ch ([84.72.69.53] helo=[192.168.0.21]); authenticated by wp303.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) id 1SoGzf-0001Fk-9M; Mon, 09 Jul 2012 18:39:27 +0200 Message-ID: <4FFB093C.9090109@justmoon.de> Date: Mon, 09 Jul 2012 18:39:24 +0200 From: Stefan Thomas User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <1341849295.94710.YahooMailNeo@web121003.mail.ne1.yahoo.com> <1341850157.18601.YahooMailNeo@web121006.mail.ne1.yahoo.com> In-Reply-To: <1341850157.18601.YahooMailNeo@web121006.mail.ne1.yahoo.com> X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;moon@justmoon.de;1341851973;8c4bdf17; X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1SoGzl-0004vZ-F6 Subject: Re: [Bitcoin-development] Random order for clients page X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2012 16:39:38 -0000 > You are not a developer of any alternative clients I am and I'm going to have to agree with Greg. Information about clients is bound to be transient and controversial. My relatively naive suggestion would be to move it to the Wiki. If it can handle the controversies involved with the Trade page, it should easily be able to handle the controversies involved with a Clients page like this one. A link to that page could be added under Bitcoin Wiki on Bitcoin.org. On the subject of randomization, I think that's a bad idea. Randomness does not equal fairness and more importantly it does not serve the users, which should be the overriding concern. As a user I don't want to be recommended a random client but the most sensible choice. As alternative client implementors we should not be overly concerned about Bitcoin.org recommending the wrong client, truly good clients will benefit from word-of-mouth and eventually rise to the top. If you want a "fair" ordering, then I'd order by number of downloads for downloadable clients and Alexa rank for any hosted / online services if it were decided that such should be listed at all. On 7/9/2012 6:09 PM, Amir Taaki wrote: > JS randomisation is bad. People shouldn't need JS to view a webpage. > > Only 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 it is. > > You 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 disputes, and make the process more fair and equal. Your suggestion to remove 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). > > If you want to suggest removing the clients page, then fine, lets also remove all reference to Bitcoin-Qt from the front-page and turn it into a http://bittorrent.org/ style website. > > Fact is that the other clients 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 few months ago, but not now. > > > > ----- Original Message ----- > From: Gregory Maxwell > To: Amir Taaki > Cc: "bitcoin-development@lists.sourceforge.net" > Sent: Monday, July 9, 2012 5:04 PM > Subject: Re: [Bitcoin-development] Random order for clients page > > On Mon, Jul 9, 2012 at 11:54 AM, Amir Taaki wrote: >> Took me a while, but finally got it working. >> Entries on the clients page are randomly ordered when the page is generated. >> https://github.com/bitcoin/bitcoin.org/commit/6850fc8c83494d6ec415ea9d36fb98366373cc03 >> We should regenerate the page every 2 days. This gives fair exposure to all the clients listed. > If you had authored this as a pull request rather than making the > change unilaterally I would have recommended leaving it so the > reference client was always first. I also would have suggested that it > use JS randomization instead of jekyll in order to get more even > coverage, though I think thats a more minor point. > > Some people were concerned when this page was created that it would > just be a source of useless disputes. I think its becoming clear that > this is the case. I think the cost of dealing with this page is > starting to exceed the benefit it provides and we should probably > consider removing it. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >