📅 Original date posted:2013-11-15
📝 Original message: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"?
> 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.
Luke
Luke-Jr [ARCHIVE] /
npub1dt…u7wrs
2023-06-07 15:09:36
in reply to nevent1q…fg27
Author Public Key
npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrsPublished at
2023-06-07 15:09:36Event JSON
{
"id": "c2747e1cb6a5e7695774f82e43e00062ab66909869da8db42d4fd36746ffcedf",
"pubkey": "6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1",
"created_at": 1686150576,
"kind": 1,
"tags": [
[
"e",
"f949fa80b2178db0fa7c7377159ffdf8cd87cc4a75383c5243367fef9a888c57",
"",
"root"
],
[
"e",
"82b4ce86b0df7f216f4ebd3b0733033242ec4bde5f749230c83da5f9f7a581f5",
"",
"reply"
],
[
"p",
"1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069"
]
],
"content": "📅 Original date posted:2013-11-15\n📝 Original message:On Saturday, November 16, 2013 12:41:56 AM Drak wrote:\n\u003e So \"a payment clears after one confirmation, but you might want to wait\n\u003e until the payment has been confirmed n times\".\n\u003e Then at least you are not using the same word for two different meanings\n\u003e and you're using stuff more familiar in popular lexicon.\n\u003e I dont think it's helpful for users if we use the word \"blocks\".\n\n\"Confirmations\" in a numeric context isn't correct, though. We're using to it \nbecause we've been using Bitcoin so long, but to the average person they would \nexpect it to mean something more than it is. If not referring to blocks, then \nperhaps \"witnessed N times\"?\n\n\u003e For years, people had a problem with \"email address\", instead using \"email\n\u003e number\" but they got there eventually. Most people nowadays use \"email\n\u003e address\"\n\u003e So \"payment address\" or \"bitcoin address\" make better sense here when\n\u003e qualified as a \"\u003cfoo\u003e address\" and not just an \"address\"\n\u003e \n\u003e You could also call it \"payment id\", but I dont think \"invoice id\" since\n\u003e no-one pays to an invoice id that's just a reference for a payment, not the\n\u003e destination.\n\u003e \n\u003e People are very familiar with Paypal these days, and are familiar with\n\u003e \"paypal address\" or their \"paypal id\" so again I think valid contenders are\n\u003e \"bitcoin address\" or \"bitcoin id\".\n\nI think you might be demonstrating my point with regard to user confusion \nhere. Bitcoin addresses are *not* like email addresses, paypal ids, etc. \nBitcoin addresses aren't the destination - they're point to a destination (an \naccount in a wallet), but they also represent information such as who is \npaying and what for - in other words, a specific invoice.\n\nLuke",
"sig": "42889af3a13ef207e4296bd735e856b3ff71eea220607deb86ae655749e3a48a15548de89d4413ad4fdcc98a8d2b72bb2772130de42a7f8092f822d2d9316913"
}