Post
📅 Original date posted:2013-11-15 📝 Original message:On 16 November 2013 01:10, Luke-Jr <luke at dashjr.org> wrote: > On Saturday, November 16, 2013 12:41:56 AM Drak wrote: > > So "a payment clears after one confirmation, but you might want to wait > > until the payment has been confirmed n times". > > Then at least you are not using the same word for two different meanings > > and you're using stuff more familiar in popular lexicon. > > I dont think it's helpful for users if we use the word "blocks". > > "Confirmations" in a numeric context isn't correct, though. We're using to > it > because we've been using Bitcoin so long, but to the average person they > would > expect it to mean something more than it is. If not referring to blocks, > then > perhaps "witnessed N times"? If you are talking about user interface, I don't think you have to be technically correct. It must make sense to the user. A user cares about his balance, and did a payment "go through", and "did my payment arrive/clear". The UI is for their benefit. > > For years, people had a problem with "email address", instead using > "email > > number" but they got there eventually. Most people nowadays use "email > > address" > > So "payment address" or "bitcoin address" make better sense here when > > qualified as a "<foo> address" and not just an "address" > > > > You could also call it "payment id", but I dont think "invoice id" since > > no-one pays to an invoice id that's just a reference for a payment, not > the > > destination. > > > > People are very familiar with Paypal these days, and are familiar with > > "paypal address" or their "paypal id" so again I think valid contenders > are > > "bitcoin address" or "bitcoin id". > > I think you might be demonstrating my point with regard to user confusion > here. Bitcoin addresses are *not* like email addresses, paypal ids, etc. > Bitcoin addresses aren't the destination - they're point to a destination > (an > account in a wallet), but they also represent information such as who is > paying and what for - in other words, a specific invoice. Maybe, but again from the user's perspective they pay someone, and they receive money - just like you do with paypal using an email address. The technical bits in the middle dont matter to the user and trying to crap stuff in to be technically correct is just confusing to them. The UI needs to be about the user and fit with his experience of the world. Drak -------------- next part -------------- An HTML attachment was scrubbed... URL: <lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131116/49a7ee31/attachment.html>
0
📅 Original date posted:2013-11-15 📝 Original message:-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/15/13 5:19 PM, Drak wrote: > Maybe, but again from the user's perspective they pay someone, and > they receive money - just like you do with paypal using an email > address. The technical bits in the middle dont matter to the user > and trying to crap stuff in to be technically correct is just > confusing to them. > > The UI needs to be about the user and fit with his experience of > the world. It's not about being technically correct. It is about protecting the user from grave breaches of privacy. It is for their own benefit that they should not be reusing addresses, and if they understood why they wouldn't. Unfortunately calling it a "bitcoin address" and including an "address book" in the reference client has had the effect of making people think that these objects are like paypal address, or email addresses, but they are not and they should not be treated the same. Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - gpgtools.org Comment: Using GnuPG with Thunderbird - www.enigmail.net iQIcBAEBAgAGBQJShsr4AAoJEAdzVfsmodw46nIP/AlDcJh2ET9qYT2ZvddciTk3 dtQDArCkwCW3kYbVjIFT8YtNFftEfkq/qBNnILipLJNN49QduAIlt3aetEE6eJBZ oqYOV2R7GW2yhLDv/GrT6GnB1C9nQ4OuKC6RNpXX4bMpZSrbP9yfyyLqecF1tMBV i8De4XLz1uUvZOo/jwHNeYy/BAZktwdk5hWlgG2yKebRbqVX1Xv70Qb1cPpBgCWm uRDL3bqdZuh6i8NNDQpBqMJ/MP4ZWpIgdHkfO6a3QCq3H0JXyug4t5lkNngCrAI3 KGlSOuYK4Fsfw97xQUBFIaSYFOU+yPDRQK4UGcTqWPLt5YHzUxBFNkOXSnVReudq Em/wlbDkPqm7R6by54fVkG85snJrwmTbD7uxGz2fe1LyzB3HhdOTZyZ1KiyDHqGA zDUFxmH0XNhvVcJvcSFlc38A54oOHTJmfJ3rxJU/q0/5N3ZIBdF8fQ4xIvXXDeeA dO+tul5q78tbO6xyTrbsHO8JRYt4Un8Hjc5mkdqp9gzA8beJFm5+jMZlGBfdl5jR lS9sW7QBxr6m+n2PJ97i+1CgoxTfzOh3jyj93G6Hqx3reTfCu5fSWUhwRnFzJXav qqPBP4Cl+6ocK7+4V1lyfAzMqpYx+GCJ1JZhD0hhwrGglgVPfE0bz7BUGea8U3+T 0pCTlkhWzEbzDp7NtFdY =ShxL -----END PGP SIGNATURE-----
0