Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Multiple client options for bitcoin.org #32

Merged
merged 7 commits into from May 9, 2012

Conversation

Projects
None yet
5 participants
Contributor

luke-jr commented Apr 11, 2012

This seems like a reasonable "first step" toward a more client-agnostic bitcoin.org website. Bitcoin-Qt is given preference, and its downloads kept on the front page, but there are links to a new page with a full index of working clients, designed similar to the download page for Pidgin.

Contributor

luke-jr commented Apr 11, 2012

Screenshot of Clients page; ignore the broken icon for Linux: my webserver hates symlinks

Contributor

tcatm commented Apr 11, 2012

Looks good! Can you try to avoid creating HTML within the plugin and use templates instead?

Contributor

luke-jr commented Apr 11, 2012

That was what I tried first, but the internal markup just didn't seem to have any way to do much useful. :/

Contributor

mikehearn commented Apr 11, 2012

Here are some comments based on the screenshot:

  • Overall format: a grid is quite imposing and scary looking! Rather than compare against various axes that a new user may or may not understand (maturity?) why not let client developers submit an image and some blurb as you might find in a mobile app store/market. It can be up to client developers to explain the merits of their software and why users should pick that over some other option. We can fact check it and not allow misleading statements.

If sticking with the grid:

  • License: only relevant for developers who can easily find it out if they want to. I'd suggest removing.
  • Network security: this is a really hard concept to explain to non-Bitcoin experts. I'd suggest removing. We should be seeing this as an aspect of target audience. If you are a merchant, a miner or just love Bitcoin and want to help out the project by running a node, run Bitcoin-Qt. If you want to get started quickly and will only use your wallet occasionally, run a lightweight client like MultiBit or use a web wallet.
  • For MultiBit: setup time is way too high. It's a few minutes at most with the latest versions of MultiBit (or should be, given that this is how long bitcoinj takes). I think it'll go ever lower in future.
  • For MultiBit: backups = no? You can back up your wallet as easily as you can with Bitcoin-Qt. It's just a file.
  • "My Wallet". Audience = everyone? Developers and merchants included? I haven't seen My Wallet before.
  • For eWallets things like reputation / longevity of the owner probably have more weight than the date of creation. Eg, an eWallet run by MtGox should be more strongly recommended than an eWallet set up by me.

Could you upload it publicly so I can take a look at the other pages?

Contributor

luke-jr commented Apr 11, 2012

Network security is IMO an important metric to convey in some way.

Bitcoin-Qt at least has an easy to use option on the File menu to make backups.

Based on playing with "My Wallet", I felt it was suitable for use by everyone.

Regarding uploading... the site is full of absolute paths, so there's really no simple way to do this :(

jim618 commented Apr 11, 2012

Hi luke-jr,

Thanks for putting together a summary of all the (growing!) number of bitcoin clients in existence.

I had a point of information on the MultiBit start up time, Mike noticed that I had missed a speed up technique that he had put into the bitcoinj codebase. This has now gone into the MultiBit codebase with the following results:

https://bitcointalk.org/index.php?topic=43616.msg847114#msg847114

That would make the overall time to :

  1. Download the installer
  2. Install it
  3. Run it to sync the blockchain

say 5 minutes tops.

This speedup will go into the next release (0.3.3) which will probably be next week.

Jim

Contributor

genjix commented Apr 25, 2012

waw, very nice :)

As a first step, this should probably be pulled right away and then any improvements can be made after. Lets get the ball rolling rather than debating the colour of the bike-shed!
http://hackerspaces.org/wiki/The_Bikeshed_Anti-Pattern

Although I agree with Mike Hearn - far better would be a grid of 4 columns and X rows. Each box has a linkable title, a picture and then 850 word blurb from the project. I mean where would libbitcoin fit in here? I'd want to say the design philosophy behind it and that there's Python bindings - a circular peg that doesn't fit in the square boxes of this table. Although whatever, that's not important. I'm just happy to see MultiBit, Electrum and Armory get exposure.

@genjix genjix merged commit cd31123 into bitcoin-dot-org:master May 9, 2012

@jl2012 jl2012 pushed a commit to jl2012/bitcoin.org that referenced this pull request Apr 5, 2016

@btcdrak btcdrak Merge pull request #32 from btcdrak/supported_bips
Add supported BIPs page
f81ad71
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment