From: Stefan Thomas <moon@justmoon•de>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Random order for clients page
Date: Mon, 09 Jul 2012 18:39:24 +0200 [thread overview]
Message-ID: <4FFB093C.9090109@justmoon.de> (raw)
In-Reply-To: <1341850157.18601.YahooMailNeo@web121006.mail.ne1.yahoo.com>
> 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 <gmaxwell@gmail•com>
> To: Amir Taaki <zgenjix@yahoo•com>
> Cc: "bitcoin-development@lists•sourceforge.net" <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 <zgenjix@yahoo•com> 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
>
next prev parent reply other threads:[~2012-07-09 16:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 15:54 Amir Taaki
2012-07-09 16:04 ` Gregory Maxwell
2012-07-09 16:09 ` Amir Taaki
2012-07-09 16:39 ` Stefan Thomas [this message]
2012-07-09 16:55 ` Harald Schilly
2012-07-09 17:21 ` Luke-Jr
2012-07-09 17:46 ` Gregory Maxwell
2012-07-09 18:03 ` Alan Reiner
2012-07-09 18:29 ` thomasV1
2012-07-09 18:18 ` Amir Taaki
2012-07-09 18:30 ` Mike Hearn
2012-07-09 22:26 ` Stefan Thomas
2012-07-09 22:37 ` Mike Hearn
2012-07-10 2:36 ` Stefan Thomas
2012-07-10 2:44 ` Alan Reiner
2012-07-10 3:05 ` Gregory Maxwell
2012-07-10 7:12 ` Wladimir
2012-07-10 9:11 ` Stefan Thomas
2012-07-13 15:20 ` Daniel F
2012-07-09 23:07 ` [Bitcoin-development] Wiki client list (was: Random order for clients page) Luke-Jr
2012-07-09 18:48 ` [Bitcoin-development] Random order for clients page Gregory Maxwell
2012-07-09 20:44 ` Jeff Garzik
2012-07-09 17:33 ` Nils Schneider
2012-07-09 18:24 ` Amir Taaki
2012-07-09 18:54 Jim
2012-07-09 18:57 ` Gregory Maxwell
2012-07-09 19:14 ` Alan Reiner
2012-07-09 20:13 ` Gary Rowe
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=4FFB093C.9090109@justmoon.de \
--to=moon@justmoon$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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