I generally agree with Greg. I don't see anything he's said or done as anti-alt-client.<div><br></div><div>As an alt-client developer, I'm happy to see my client on the main page, but I'm also happy if that "clients" page is simply an acknowledgement that there's more to the Bitcoin world than just the Bitcoin-Qt client, and a link of where to find more information (i.e. the wiki). I would still <i>prefer</i> to have the page the way it is, because I think alt clients should be more accessible and word will spread better where it is now -- but I also recognize the inherent difficulty of gaining any kind of consensus of how it should be organized, what goes on the list, etc, and no matter how you do it, someone will complain about it being unfair or not right.</div>
<div><br></div><div>We either have to have a "czar" who is trusted to make responsible decisions, and complaints of being unfair or recommendations for improvements can go through that person, but ultimately it is that person who makes the call. Or we just move it to another page that is less strictly controlled and where these things matter less. Trying to gain consensus among an amalgamation of developers all with competing priorities and "products" is a terrible way to try to agree on stuff.</div>
<div><br></div><div>-Alan<br><div><div><br></div><div><br><div><br><br><div class="gmail_quote">On Mon, Jul 9, 2012 at 1:46 PM, Gregory Maxwell <span dir="ltr"><<a href="mailto:gmaxwell@gmail.com" target="_blank">gmaxwell@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Mon, Jul 9, 2012 at 12:09 PM, Amir Taaki <<a href="mailto:zgenjix@yahoo.com">zgenjix@yahoo.com</a>> wrote:<br>
> JS randomisation is bad. People shouldn't need JS to view a webpage.<br>
<br>
</div>JS randomization doesn't imply needing JS to view the page. It implies<br>
needing JS to see it in random order. You could also combine it with<br>
the server-side randomization if you care about non-js being non<br>
random, though I don't think it matters.<br>
<br>
As others have pointed out I don't generally think the randomization<br>
is good in principle, but if its done it should at least achieve its<br>
goals.<br>
<div class="im"><br>
> 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.<br>
<br>
</div>I'll let other people speak for themselves, but I did consult others<br>
before reverting your last batch of changes.<br>
<br>
More generally, we have pull requests in order to get some peer review<br>
of changes. Everyone should use them except for changes which are<br>
urgent or trivially safe. (Presumably everyone with access knows how<br>
to tell if their changes are likely to be risky or controversial)<br>
<div class="im"><br>
> 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).<br>
<br>
</div>I'm strongly supportive diversity in the Bitcoin network, and some alt<br>
client developers can speak to the positive prodding I've given them<br>
towards becoming more complete software. If I've said anything that<br>
suggests otherwise I'd love to be pointed to it in order to clarify my<br>
position.<br>
<br>
Unfortunately none of the primary alternatives are yet complete, the<br>
network would be non-function if it consisted entirely of multibit or<br>
electrum nodes (and as you've noted armory uses a local reference<br>
client as its 'server'). The distinction between multiple kinds of<br>
clients in terms of security and network health are subtle and can be<br>
difficult to explain even to technical users and so until something<br>
changes there the reference client needs to be the option we lead<br>
with. People should us it unless their use-case doesn't match. When it<br>
does they'll know it and they'll be looking. We don't need to make one<br>
of those recommendations a primary option.<br>
<br>
I like the proposals of moving this stuff to the Wiki as the wiki<br>
already contains tons of questionable (and sometimes contradictory)<br>
advice and so there is less expectation that placement there implies<br>
any vetting.<br>
<div class="HOEnZb"><div class="h5"><br>
------------------------------------------------------------------------------<br>
Live Security Virtual Conference<br>
Exclusive live event will cover all the ways today's security and<br>
threat landscape has changed and how IT managers can respond. Discussions<br>
will include endpoint security, mobile security and the latest in malware<br>
threats. <a href="http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/" target="_blank">http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href="mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/bitcoin-development" target="_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a><br>
</div></div></blockquote></div><br></div></div></div></div>