{"type":"rich","version":"1.0","author_name":"npub12rkw0jajmsck4uwdtksdvtswrlkypusfryjzera7m4fhqta6jhdsz3aqxc","author_url":"https://nostr.ae/npub12rkw0jajmsck4uwdtksdvtswrlkypusfryjzera7m4fhqta6jhdsz3aqxc","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-11-15\n📝 Original message:On 16 November 2013 01:10, Luke-Jr \u003cluke at dashjr.org\u003e wrote:\n\n\u003e On Saturday, November 16, 2013 12:41:56 AM Drak wrote:\n\u003e \u003e So \"a payment clears after one confirmation, but you might want to wait\n\u003e \u003e until the payment has been confirmed n times\".\n\u003e \u003e Then at least you are not using the same word for two different meanings\n\u003e \u003e and you're using stuff more familiar in popular lexicon.\n\u003e \u003e I dont think it's helpful for users if we use the word \"blocks\".\n\u003e\n\u003e \"Confirmations\" in a numeric context isn't correct, though. We're using to\n\u003e it\n\u003e because we've been using Bitcoin so long, but to the average person they\n\u003e would\n\u003e expect it to mean something more than it is. If not referring to blocks,\n\u003e then\n\u003e perhaps \"witnessed N times\"?\n\n\nIf you are talking about user interface, I don't think you have to be\ntechnically correct. It must make sense to the user.\nA user cares about his balance, and did a payment \"go through\", and \"did my\npayment arrive/clear\".\n\nThe UI is for their benefit.\n\n\n\u003e \u003e For years, people had a problem with  \"email address\", instead using\n\u003e \"email\n\u003e \u003e number\" but they got there eventually. Most people nowadays use \"email\n\u003e \u003e address\"\n\u003e \u003e So \"payment address\" or \"bitcoin address\" make better sense here when\n\u003e \u003e qualified as a \"\u003cfoo\u003e address\" and not just an \"address\"\n\u003e \u003e\n\u003e \u003e You could also call it \"payment id\", but I dont think \"invoice id\" since\n\u003e \u003e no-one pays to an invoice id that's just a reference for a payment, not\n\u003e the\n\u003e \u003e destination.\n\u003e \u003e\n\u003e \u003e People are very familiar with Paypal these days, and are familiar with\n\u003e \u003e \"paypal address\" or their \"paypal id\" so again I think valid contenders\n\u003e are\n\u003e \u003e \"bitcoin address\" or \"bitcoin id\".\n\u003e\n\u003e I think you might be demonstrating my point with regard to user confusion\n\u003e here. Bitcoin addresses are *not* like email addresses, paypal ids, etc.\n\u003e Bitcoin addresses aren't the destination - they're point to a destination\n\u003e (an\n\u003e account in a wallet), but they also represent information such as who is\n\u003e paying and what for - in other words, a specific invoice.\n\n\nMaybe, but again from the user's perspective they pay someone, and they\nreceive money - just like you do with paypal using an email address.\nThe technical bits in the middle dont matter to the user and trying to crap\nstuff in to be technically correct is just confusing to them.\n\nThe UI needs to be about the user and fit with his experience of the world.\n\nDrak\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131116/49a7ee31/attachment.html\u003e"}