📅 Original date posted:2017-12-15
📝 Original message:
Jonathan Underwood <junderwood at bitcoinbank.co.jp> writes:
> Additional comment: we should make a requirement to hide text in the
> description under certain conditions.
>
> ie. "A reader MUST hide information surrounded by curly brackets {}
> including
> the brackets themselves from the UI, and only make the information avaiable
> internally."
>
> I think a lot of people will want to include extra data in their payment
> requests' description.
>
> I think HTLC.ME uses it and maybe bitrefill? (correct me if I'm wrong.)
OK, HTLC.ME (cool site!) uses a description of:
{"generic_id":"ada00363-50b6-4281-82dd-d274393439f1"}
Which I really don't understand. This field is literally only to
display to the user, for them to validate it's what they wanted. The
recipient never gets it back.
If I knew who ran HTLC.ME, I'd ask them to fix it: they should have a
description entry field in their "Request Payment" form. It could
default to "Test payment ada00363-50b6-4281-82dd-d274393439f1", but
they're in spec violation at the moment.
> Perhaps adding an "extra data" tag?
Easy to do, if I knew why they wanted it.
Thanks!
Rusty.
Rusty Russell [ARCHIVE] /
npub1zw…hkhpx
2023-06-09 12:47:58
in reply to nevent1q…a2sa
Author Public Key
npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpxPublished at
2023-06-09 12:47:58Event JSON
{
"id": "2a22b0bd67034a468d9de659633cea0fad036e714be2e1009e9a2c3bde5877ca",
"pubkey": "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425",
"created_at": 1686314878,
"kind": 1,
"tags": [
[
"e",
"3116f5c29c5dc34156cc0d7b8c18c7f0b4f198b1f29affc604211c8c32af34de",
"",
"root"
],
[
"e",
"4c64986fea4621fbac0bd1caefed67664e4a533b2744a43f586f9062d0dfa0cc",
"",
"reply"
],
[
"p",
"e999edd1a420e7d5e19be7870cbcfa798bb98cb408e5929a2a18181c8c6f1dee"
]
],
"content": "📅 Original date posted:2017-12-15\n📝 Original message:\nJonathan Underwood \u003cjunderwood at bitcoinbank.co.jp\u003e writes:\n\u003e Additional comment: we should make a requirement to hide text in the\n\u003e description under certain conditions.\n\u003e\n\u003e ie. \"A reader MUST hide information surrounded by curly brackets {}\n\u003e including\n\u003e the brackets themselves from the UI, and only make the information avaiable\n\u003e internally.\"\n\u003e\n\u003e I think a lot of people will want to include extra data in their payment\n\u003e requests' description.\n\u003e\n\u003e I think HTLC.ME uses it and maybe bitrefill? (correct me if I'm wrong.)\n\nOK, HTLC.ME (cool site!) uses a description of:\n\n {\"generic_id\":\"ada00363-50b6-4281-82dd-d274393439f1\"}\n\nWhich I really don't understand. This field is literally only to\ndisplay to the user, for them to validate it's what they wanted. The\nrecipient never gets it back.\n\nIf I knew who ran HTLC.ME, I'd ask them to fix it: they should have a\ndescription entry field in their \"Request Payment\" form. It could\ndefault to \"Test payment ada00363-50b6-4281-82dd-d274393439f1\", but\nthey're in spec violation at the moment.\n\n\u003e Perhaps adding an \"extra data\" tag?\n\nEasy to do, if I knew why they wanted it.\n\nThanks!\nRusty.",
"sig": "55f301d1e5e42989dc4c3552d9c69512ba890083a3f17efeca38399c668d40ed278f8d73dd444576f170267237fc4704786640afdf65105a2cc19e2d2c3814a0"
}