MIME-Version: 1.0
Sender: marek@palatinus.cz
In-Reply-To: <CANEZrP0ce4MMX2hOhcGVWt23L_CMn6Cmj9_Okqd0BR9seQXJew@mail.gmail.com>
References: <CANEZrP3iyQ9zQ+hDnooxrjdBO+_Fj+nAkK1Skgk+Gb4gkidPhQ@mail.gmail.com>
	<CAJHLa0Omiz+UhGjSKgYU7+b2YY7aN23w7o8CQntqMePFs7LkjA@mail.gmail.com>
	<CANEZrP06gk-JhKaNpvYUTfjFq9AGnCay9=pjUGpVMjMSuX3_ew@mail.gmail.com>
	<CAJna-HhX8HOci0KMe4ZScr4QW792S3n5twvU0QhbQe1N_3q7_w@mail.gmail.com>
	<6E6F88E9-5698-419B-927C-F65A5FCABBE9@gmail.com>
	<CAJHLa0PYfuJg3daPvzPFZpFz7ezH2RHpJ8zyz2g1NDKppM7rWA@mail.gmail.com>
	<BBF86C9B-6B3D-4A03-AC7B-35619C47091F@gmail.com>
	<CABsx9T13yksenx5aYd4HVqTyVjARx9aTHy=Neu64p6k9FnRRVw@mail.gmail.com>
	<C95DB811-9E6A-4EA2-AE8F-83595C3AC817@gmail.com>
	<CANEZrP0ce4MMX2hOhcGVWt23L_CMn6Cmj9_Okqd0BR9seQXJew@mail.gmail.com>
From: slush <slush@centrum.cz>
Date: Wed, 25 Jun 2014 16:15:01 +0200
Message-ID: <CAJna-HiRChr4M9QL_7ZeKQeV7m5M4-ysnERB1DmK1itJMaGucQ@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=20cf3071c6c684741704fca9b566
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed BIP 70 extension
Precedence: list

--20cf3071c6c684741704fca9b566
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jun 25, 2014 at 10:25 AM, Mike Hearn <mike@plan99.net> wrote:
>
> The protocol is there to contain features! There is zero benefit to
> slavishly following some religious notion of purity or minimalism here.
>

Good standard must be explicit as much as possible. Having million optional
fields with ambiguous meaning is even worse than not having these fields.

HTTP status codes are good example. There are hundreds of them, still
applications understands just few of them, because other have ambiguous
meaning and software don't know how to handle them.

Good example of such over-engineering is also XMPP. XMPP has milions
extensions and features, but look at Jabber clients; call yourself lucky
when you can send messages and files, although there're various extensions
like searching for contacts (something which has be working in ICQ decade
ago), voice support, end to end encryption or alerting users. These
features are defined, but not widely implemented, because its definition is
vague or the feature is abused because of poor design.

Please don't over-engineer payment protocol.

Thank you for your attention.

slush

--20cf3071c6c684741704fca9b566
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Jun 25, 2014 at 10:25 AM, Mike Hearn <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>&gt;</span> wro=
te:<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
>The protocol is there to contain features! There is zero benefit to slavis=
hly following some religious notion of purity or minimalism here.</div></di=
v>

</div></div></blockquote><div><br></div><div>Good standard must be explicit=
 as much as possible. Having million optional fields with ambiguous meaning=
 is even worse than not having these fields.</div><div><br></div><div>
HTTP status codes are good example. There are hundreds of them, still appli=
cations understands just few of them, because other have ambiguous meaning =
and software don&#39;t know how to handle them.</div>
<div><br></div><div>Good example of such over-engineering is also XMPP. XMP=
P has milions extensions and features, but look at Jabber clients; call you=
rself lucky when you can send messages and files, although there&#39;re var=
ious extensions like searching for contacts (something which has be working=
 in ICQ decade ago), voice support, end to end encryption or alerting users=
. These features are defined, but not widely implemented, because its defin=
ition is vague or the feature is abused because of poor design.</div>

<div><br></div><div>Please don&#39;t over-engineer payment protocol.</div><=
div><br></div><div>Thank you for your attention.</div><div><br></div><div>s=
lush</div><div><br></div><div><br></div></div></div></div>

--20cf3071c6c684741704fca9b566--