public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] Lying about User Agent (was: BIP language on normative behavior)
Date: Mon, 19 Dec 2011 17:36:44 -0500	[thread overview]
Message-ID: <201112191736.45948.luke@dashjr.org> (raw)
In-Reply-To: <CAAS2fgQpMWYLoT_1Za5AxvgNaXvEuJOZ2BjE94o09=t+LyfM5A@mail.gmail.com>

On Monday, December 19, 2011 5:29:34 PM Gregory Maxwell wrote:
> I've been arguing with Luke-JR on IRC about the interpenetration of
> BIP_0014—  Gavin's recent commit uses the same version string for the
> GUI interface and the daemon mode.
> 
> Luke believes this is a _violation_ of BIP_0014 and an error in
> judgement on Gavin's part, and a failure to conform to the community
> adopted standard. 

To clarify, I believe LYING about the client is a violation. Specifically, 
Gavin's commit intentionally reports "bitcoin-qt" for bitcoind. A common name 
for the codebase is compliant, and I don't see anything that says a version 
*must* be reported at all, let alone for a specific component, so it *could* 
comply by leaving that part off. But if there is a common part, it certainly 
isn't Bitcoin-Qt.

https://github.com/bitcoin/bitcoin/pull/715 contains a fix that should fulfil 
everyone's desires (Gavin wants security by obscurity by making bitcoind and 
Bitcoin-Qt indistinguishable; this is the default with pull #715).



  reply	other threads:[~2011-12-19 22:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19 22:29 [Bitcoin-development] BIP language on normative behavior Gregory Maxwell
2011-12-19 22:36 ` Luke-Jr [this message]
2011-12-21  0:59 ` Amir Taaki
     [not found]   ` <201112202007.49399.luke@dashjr.org>
2011-12-21  1:14     ` Amir Taaki
2011-12-21  9:27   ` Andy Parkins

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=201112191736.45948.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