From: Amir Taaki <zgenjix@yahoo•com>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Lock protocol version numbers
Date: Sat, 5 Nov 2011 09:40:12 -0700 (PDT) [thread overview]
Message-ID: <1320511212.70648.YahooMailNeo@web121017.mail.ne1.yahoo.com> (raw)
In-Reply-To: <201111051229.16790.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
On Saturday, November 05, 2011 12:17:58 PM Christian Decker wrote:
>> Sorry for shooting this approach down, but I'm against it. User-agent
>> strings are an extremely bad idea as it would lead developers to start
>> making communication choices depending on the client type.
> This can be necessary in some cases. What happens when some popular client is
> found with a subtle bug, and cannot otherwise be differentiated from other
> similar-functionality clients? I have found User-Agent very valuable when
> dealing with the wide variety of miner bugs when I have enabled new
> functionality/behaviour on Eligius.
I can agree with this point though. If clients break the network protocol/do not comply properly with it, they should be disconnected and shunned. Hard love. We don't want any ambiguity in the protocol.
Fail hard and fast.
However my feeling about the user-agent string is that it is a vanity item, but here we'd be enforcing a format that everybody can understand and read. Lets say with libbitcoin- I'm sure that users of libbitcoin would like to have their client name in the string somehow. This was we can quickly understand which code-bases are being used and all the variants that exist build on those code-bases.
Together with system information (how many Linux users are there?) and various system settings (how many 32bit users are there), and so on.
[-- Attachment #2: Type: text/html, Size: 1803 bytes --]
next prev parent reply other threads:[~2011-11-05 16:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 21:23 Amir Taaki
2011-11-02 21:32 ` Christian Decker
[not found] ` <CABsx9T0zUCu2RFC0Nc4URMtu060wyHMaebEM87in=NSiNbp=rw@mail.gmail.com>
2011-11-02 22:33 ` Amir Taaki
2011-11-02 22:42 ` Christian Decker
2011-11-02 22:58 ` Amir Taaki
2011-11-02 22:46 ` Luke-Jr
2011-11-02 22:55 ` Amir Taaki
2011-11-02 23:07 ` Luke-Jr
2011-11-02 23:22 ` Christian Decker
2011-11-03 4:46 ` Jeff Garzik
2011-11-05 14:32 ` Mike Hearn
2011-11-05 14:45 ` Christian Decker
[not found] ` <1320507570.40074.YahooMailNeo@web121017.mail.ne1.yahoo.com>
2011-11-05 15:39 ` Amir Taaki
2011-11-05 16:17 ` Christian Decker
2011-11-05 16:29 ` Luke-Jr
2011-11-05 16:40 ` Amir Taaki [this message]
2011-11-05 17:30 ` Jordan Mack
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=1320511212.70648.YahooMailNeo@web121017.mail.ne1.yahoo.com \
--to=zgenjix@yahoo$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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