From: grarpamp <grarpamp@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] new bitcoin.org clients page
Date: Wed, 2 May 2012 12:53:07 -0400 [thread overview]
Message-ID: <CAD2Ti29mFcGJsojsuSWzC0XxnRWPYAryZU3T3-URiP+1owdO0w@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP17H-E0mWGGjNS2i0079LuRJ9MnVHSPjR_ots2LR7j9bA@mail.gmail.com>
> it's unclear how best to run this page. It's clear we need one though.
> the right path is probably the middle one - have some descriptions that try to be neutral
Do it in two parts...
- overview, history, architecture model, 'whys'.
- agnostic table of features, platforms, stats, protocols, etc
Last, resolve whether or not bitcoin.org is independant.
It cannot be if it does not accept all lib/client under it's umbrella
or has a lib/client project of it's own. You will hit up against this,
just saying.
> Bitcoin-Qt
> This application is a peer-to-peer client that builds the backbone of the Bitcoin network.
No, they all do this and build it, subject to their feature set.
> It is suited for enthusiasts, merchants, miners, developers
No, all implementations are suited for whoever, subject to their feature set.
> and people who want to help support the project.
Which project, the given client or the bitcoin meme.
> People who run Bitcoin-Qt are first class network citizens and have the highest levels of security, privacy and stability.
Right, anyone who doesn't is unwashed rebel scum, running default
installs of xp, on systems with bad ram, who post their home address,
transaction logs, and pink bits on facebook.
> leave it running in the background so other computers can connect to yours.
Again, a feature set / usage model thing.
> MultiBit
> fast and easy to use, even for people with no technical knowledge.
Hey, we're fast, easy and for noobs, me too.
> It has a...
But at least the backing specifics to that claim are stated.
> Armory
> Armory was partly funded by a community donation drive which raised over $4000.
Yeah, every lib/client will have a donation thing on their own site,
and the developers own real world wallet.
> Electrum
> the privacy level is lower than for other clients.
Not sure of this claim. It's all in the usage. Run your own remote,
use anonymizers, etc. Right?
next prev parent reply other threads:[~2012-05-02 16:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 17:50 Amir Taaki
2012-04-30 18:23 ` Alan Reiner
2012-04-30 18:31 ` Amir Taaki
2012-04-30 19:51 ` Alan Reiner
2012-05-02 13:22 ` Mike Hearn
2012-05-02 13:30 ` Gregory Maxwell
2012-05-02 13:32 ` Mike Hearn
2012-05-02 13:31 ` Luke-Jr
2012-05-02 16:21 ` grarpamp
2012-05-02 16:30 ` Luke-Jr
2012-05-02 16:58 ` grarpamp
2012-05-02 18:29 ` Jeff Garzik
2012-05-02 19:25 ` Amir Taaki
2012-05-02 19:34 ` Gary Rowe
2012-05-02 19:40 ` Raphael NICOLLE
2012-05-02 19:42 ` Gary Rowe
2012-05-02 19:43 ` Alan Reiner
2012-05-02 19:43 ` Amir Taaki
2012-05-02 19:46 ` Gary Rowe
2012-05-02 19:56 ` Alan Reiner
2012-05-02 20:25 ` Luke-Jr
2012-05-02 20:39 ` Gary Rowe
2012-05-02 19:35 ` Alan Reiner
2012-05-03 9:06 ` grarpamp
2012-05-02 13:38 ` Gregory Maxwell
2012-05-02 13:42 ` Mike Hearn
2012-05-02 15:01 ` Alan Reiner
2012-05-02 16:53 ` grarpamp [this message]
2012-05-03 7:28 ` Andreas Schildbach
2012-05-03 9:24 ` Jorge Timón
2012-05-03 9:53 ` Andreas Schildbach
2012-05-03 10:25 ` Jorge Timón
2012-05-02 23:04 ` Jeff Garzik
2012-05-02 20:41 Jim
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=CAD2Ti29mFcGJsojsuSWzC0XxnRWPYAryZU3T3-URiP+1owdO0w@mail.gmail.com \
--to=grarpamp@gmail$(echo .)com \
--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