From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Lock protocol version numbers
Date: Sat, 5 Nov 2011 12:29:15 -0400 [thread overview]
Message-ID: <201111051229.16790.luke@dashjr.org> (raw)
In-Reply-To: <CALxbBHWYdt_LRQE5K=36fXNNSqyGVSyYwxi2-p8mxQaei5LCZg@mail.gmail.com>
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.
next prev parent reply other threads:[~2011-11-05 16:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 21:23 [Bitcoin-development] Lock protocol version numbers 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 [this message]
2011-11-05 16:40 ` Amir Taaki
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=201111051229.16790.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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