From: Jeff Garzik <jgarzik@bitpay•com>
To: Gmail <will.yager@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed BIP 70 extension
Date: Tue, 24 Jun 2014 11:48:15 -0400 [thread overview]
Message-ID: <CAJHLa0PYfuJg3daPvzPFZpFz7ezH2RHpJ8zyz2g1NDKppM7rWA@mail.gmail.com> (raw)
In-Reply-To: <6E6F88E9-5698-419B-927C-F65A5FCABBE9@gmail.com>
I think there is nothing wrong with having a numeric memo field, which
is effectively what this is. Structured rather than unstructured
data.
On Tue, Jun 24, 2014 at 11:15 AM, Gmail <will.yager@gmail•com> wrote:
>
>
>> On Jun 24, 2014, at 10:32, slush <slush@centrum•cz> wrote:
>>
>> Sounds like marketing bullshit to me. It does not have even statistical meaning; well, you can "save" a lot of satoshis, but nobody tell you that the merchant cut you on BTC/USD exchange rate in tens of %.
>
> People would also abuse this feature in the same way amazon (and other sales sites) abuse the definition of "save". For example, Amazon will indicate that you're getting x% off by shopping at amazon, but all that number really means is x% off MSRP. In reality, every website has the same price. I have no doubt that merchants would put similarly meaningless and/or misleading data in this field.
>
> I agree, the memo field is appropriate for this 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@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2014-06-24 15:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 13:27 Mike Hearn
2014-06-24 14:21 ` Jeff Garzik
2014-06-24 14:24 ` Mike Hearn
2014-06-24 14:32 ` slush
2014-06-24 15:06 ` Mike Hearn
2014-06-24 15:15 ` Gmail
2014-06-24 15:48 ` Jeff Garzik [this message]
2014-06-24 19:00 ` Gmail
2014-06-24 19:34 ` Andy Alness
2014-06-24 20:12 ` Gavin Andresen
2014-06-24 20:28 ` Gmail
2014-06-25 8:25 ` Mike Hearn
2014-06-25 13:33 ` Jorge Timón
2014-06-25 18:10 ` Jeff Garzik
2014-06-25 14:15 ` slush
2014-06-25 16:03 ` Gmail
2014-06-24 18:34 ` Roy Badami
2014-06-24 15:43 ` Andreas Schildbach
2014-06-24 15:59 ` Mike Hearn
2014-06-24 17:37 ` Drak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJHLa0PYfuJg3daPvzPFZpFz7ezH2RHpJ8zyz2g1NDKppM7rWA@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=will.yager@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox