Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RciHo-0008J5-Ed for bitcoin-development@lists.sourceforge.net; Mon, 19 Dec 2011 18:50:08 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.53 as permitted sender) client-ip=74.125.82.53; envelope-from=timon.elviejo@gmail.com; helo=mail-ww0-f53.google.com; Received: from mail-ww0-f53.google.com ([74.125.82.53]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1RciHn-0002VJ-QP for bitcoin-development@lists.sourceforge.net; Mon, 19 Dec 2011 18:50:08 +0000 Received: by wgbds1 with SMTP id ds1so10100678wgb.10 for ; Mon, 19 Dec 2011 10:50:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.227.60.4 with SMTP id n4mr13051915wbh.9.1324320601679; Mon, 19 Dec 2011 10:50:01 -0800 (PST) Received: by 10.223.81.79 with HTTP; Mon, 19 Dec 2011 10:50:01 -0800 (PST) In-Reply-To: References: <1323728469.78044.YahooMailNeo@web121012.mail.ne1.yahoo.com> <201112191130.43721.luke@dashjr.org> <4EEF6EA2.4060709@parhelic.com> <4EEF7EB4.6070800@parhelic.com> Date: Mon, 19 Dec 2011 19:50:01 +0100 Message-ID: From: =?ISO-8859-1?Q?Jorge_Tim=F3n?= Cc: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (timon.elviejo[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.2 MISSING_HEADERS Missing To: header -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RciHn-0002VJ-QP Subject: Re: [Bitcoin-development] [BIP 15] Aliases X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2011 18:50:08 -0000 I don't have a strong position for or against JSON but...What about protocol buffers? Would it be too much too? Would it be simple enough for developers?