📅 Original date posted:2014-06-24
📝 Original message:I somewhat agree with Will (but also with Mike, Jeff, and Charlie.) I
think the idea of letting consumers know advanced details about the
transaction is good and defining these with strong types is also good.
Maybe an arbitrary set of accounting line items would be more
palatable. You could have a line item for state sales tax for example,
or a cash back reward, or a merchant discount like the proposed,
whatever is applicable. It would be a list of amount / label tuples
maybe.
On Tue, Jun 24, 2014 at 12:00 PM, Gmail <will.yager at gmail.com> wrote:
> Ok, wanting structured data is a decent argument, but why this random
> arbitrary case in particular? There are hundreds of fields like this that
> people might want to use.
>
> If we're going to support one random cosmetic field, we might as well
> support them all with a generic structured data format.
>
> I'd rather we just didn't have this essentially pointless "feature" at all.
> Let's try and keep as much cruft as possible out of the payment protocol.
> The textual memo field is already more than sufficient.
>
> On Jun 24, 2014, at 11:48, Jeff Garzik <jgarzik at bitpay.com> wrote:
>
> I think there is nothing wrong with having a numeric memo field, which
> is effectively what this is. Structured rather than unstructured
> data.
>
>
> ------------------------------------------------------------------------------
> Open source business process management suite built on Java and Eclipse
> Turn processes into business applications with Bonita BPM Community Edition
> Quickly connect people, data, and systems into organized workflows
> Winner of BOSSIE, CODIE, OW2 and Gartner awards
> http://p.sf.net/sfu/Bonitasoft
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
Andy Alness
Software Engineer
Coinbase
San Francisco, CA
Andy Alness [ARCHIVE] /
npub1xl…kfzv5
2023-06-07 15:23:17
in reply to nevent1q…9p3q
Author Public Key
npub1xljjfnrwkp7tg7lyc2624rd2pt5cht3tna00wqad290wxkjw0t7qvkfzv5Seen on
wss://relay.noswhere.comPublished at
2023-06-07 15:23:17Event JSON
{
"id": "7128bcf47f99789776a2340d671d8493cfd8f667d9c2ddb4aed6fc431a7365e4",
"pubkey": "37e524cc6eb07cb47be4c2b4aa8daa0ae98bae2b9f5ef703ad515ee35a4e7afc",
"created_at": 1686151397,
"kind": 1,
"tags": [
[
"e",
"9815d098bc7f4989718551eb052a860bc92caef6ef36f2244b5fda76fe0b928a",
"",
"root"
],
[
"e",
"f1a76e5f411f26746464b16c7ed624c651d3a26f3581dfa9a6c27e28c4a3e969",
"",
"reply"
],
[
"p",
"5df7f6f5f6998cb4543e81f7c82eb7c60674e3fc4b9a3ef6e28a50e8e835de2d"
]
],
"content": "📅 Original date posted:2014-06-24\n📝 Original message:I somewhat agree with Will (but also with Mike, Jeff, and Charlie.) I\nthink the idea of letting consumers know advanced details about the\ntransaction is good and defining these with strong types is also good.\nMaybe an arbitrary set of accounting line items would be more\npalatable. You could have a line item for state sales tax for example,\nor a cash back reward, or a merchant discount like the proposed,\nwhatever is applicable. It would be a list of amount / label tuples\nmaybe.\n\nOn Tue, Jun 24, 2014 at 12:00 PM, Gmail \u003cwill.yager at gmail.com\u003e wrote:\n\u003e Ok, wanting structured data is a decent argument, but why this random\n\u003e arbitrary case in particular? There are hundreds of fields like this that\n\u003e people might want to use.\n\u003e\n\u003e If we're going to support one random cosmetic field, we might as well\n\u003e support them all with a generic structured data format.\n\u003e\n\u003e I'd rather we just didn't have this essentially pointless \"feature\" at all.\n\u003e Let's try and keep as much cruft as possible out of the payment protocol.\n\u003e The textual memo field is already more than sufficient.\n\u003e\n\u003e On Jun 24, 2014, at 11:48, Jeff Garzik \u003cjgarzik at bitpay.com\u003e wrote:\n\u003e\n\u003e I think there is nothing wrong with having a numeric memo field, which\n\u003e is effectively what this is. Structured rather than unstructured\n\u003e data.\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e Open source business process management suite built on Java and Eclipse\n\u003e Turn processes into business applications with Bonita BPM Community Edition\n\u003e Quickly connect people, data, and systems into organized workflows\n\u003e Winner of BOSSIE, CODIE, OW2 and Gartner awards\n\u003e http://p.sf.net/sfu/Bonitasoft\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\n\n\n-- \nAndy Alness\nSoftware Engineer\nCoinbase\nSan Francisco, CA",
"sig": "aa2cf1a3a2c3b79183852e58a387f0416c8afc8b98e9c8e0d472a1c95bafb3a3284733c94011ea76a62b5e1e339cb06c1cd46933c9c4c88f6828e1b5a9e52f99"
}