public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jameson Lopp <jameson.lopp@gmail.com>
To: Brian Lockhart <brianlockhart@gmail.com>
Cc: "Bitcoin Protocol Discussion"
	<bitcoin-dev@lists.linuxfoundation.org>,
	"JOSE FEMENIAS CAÑUELO" <jose.femenias@gmail.com>
Subject: Re: [bitcoin-dev] Possible change to the MIT license
Date: Tue, 13 Feb 2018 10:45:55 -0500	[thread overview]
Message-ID: <CADL_X_c=+YtLfyOn3fucyQEc5wtpmpXMNaJzvCPOc+cw-POOkw@mail.gmail.com> (raw)
In-Reply-To: <CAJQ0i9vDWqryxni6sEx1NDHjLpUCCH=F=t0s2p-seYYtyhuosw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3731 bytes --]

Anyone who feels so inclined is free to "pick up the mantle" and defend
Bitcoin against perceived social attacks. I don't think that Bitcoin
protocol developers have any particular responsibility to do so, and as
such this particular discussion is likely going to quickly veer off-topic
for this mailing list.

On Tue, Feb 13, 2018 at 10:37 AM, Brian Lockhart <brianlockhart@gmail.com>
wrote:

> > I don't think that Bitcoin should be reliant upon courts or governments
> to defend itself against attacks of any form.
>
> Agree 100%. Plus yeah, lotsa luck getting any success via those channels...
>
> But assuming the answer to the perceived problem is to “fight fire with
> fire” (using social / marketing based efforts) who “should” pick up the
> mantle here? Without inciting riots by asking the question, wouldn’t that
> ostensibly be something the Bitcoin Foundation would lead on here? <ducks
> and runs for cover>
>
> In any case, it’s frustrating to watch the ongoing FUD and scammery going
> unanswered in any “official” capacity.
>
>
> On February 13, 2018 at 7:25:35 AM, Jameson Lopp via bitcoin-dev (
> bitcoin-dev@lists.linuxfoundation.org) wrote:
>
> If I'm understanding the problem being stated correctly:
>
> "Bitcoin is under a branding attack by fork coins."
>
> The proposed solution is to disincentivize fork coins from using the word
> Bitcoin by altering the license terms. I'm not a lawyer, but it seems to me
> that the words of the license are basically useless unless there is an
> entity that intends to make use of court systems to threaten noncompliant
> projects into submission.
>
> In my opinion, the perceived attack on Bitcoin here is social /
> marketing-based, thus it makes sense that any defense against said attack
> should also be social / marketing-based. I don't think that Bitcoin should
> be reliant upon courts or governments to defend itself against attacks of
> any form.
>
> On Tue, Feb 13, 2018 at 9:25 AM, Natanael via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>>
>>
>> Den 13 feb. 2018 15:07 skrev "JOSE FEMENIAS CAÑUELO via bitcoin-dev" <
>> bitcoin-dev@lists.linuxfoundation.org>:
>>
>> ***
>> NO PART OF THIS SOFTWARE CAN BE INCLUDED IN ANY OTHER PROJECT THAT USES
>> THE NAME BITCOIN AS PART OF ITS NAME AND/OR ITS MARKETING MATERIAL UNLESS
>> THE SOFTWARE PRODUCED BY THAT PROJECT IS FULLY COMPATIBLE WITH THE BITCOIN
>> (CORE) BLOCKCHAIN
>> ***
>>
>>
>> That's better solved with trademarks. (whoever would be the trademark
>> holder - Satoshi?)
>>
>> This would also prohibit any reimplementation that's not formally
>> verified to be perfectly compatible from using the name.
>>
>> It also adds legal uncertainty.
>>
>> Another major problem is that it neither affects anybody forking older
>> versions of Bitcoin, not people using existing independent blockchain
>> implementations and renaming them Bitcoin-Whatsoever.
>>
>> And what happens when an old version is technically incompatible with a
>> future version by the Core team due to not understanding various new
>> softforks? Which version wins the right to the name?
>>
>> Also, being unable to even mention Bitcoin is overkill.
>>
>> The software license also don't affect the blockchain data.
>>
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

[-- Attachment #2: Type: text/html, Size: 7353 bytes --]

  reply	other threads:[~2018-02-13 15:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 12:25 [bitcoin-dev] Possible change to the MIT license JOSE FEMENIAS CAÑUELO
2018-02-13 14:25 ` Natanael
2018-02-13 15:24   ` Jameson Lopp
2018-02-13 15:37     ` Brian Lockhart
2018-02-13 15:45       ` Jameson Lopp [this message]
2018-02-13 17:04       ` Patrick Murck
2018-02-13 15:45     ` Aymeric Vitte
2018-02-13 15:47     ` Bedri Ozgur Guler
2018-02-13 17:28       ` Felix Wolfsteller
2018-02-13 19:08         ` Cory Fields
2018-02-13 19:08         ` CryptAxe
2018-02-13 15:22 ` Aymeric Vitte
2018-02-13 17:53 ` Luke Dashjr
2018-02-13 17:25 Adam Ficsor
2018-02-13 17:46 ` Daniel Robinson
2018-02-14 10:09 Damian Williamson

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='CADL_X_c=+YtLfyOn3fucyQEc5wtpmpXMNaJzvCPOc+cw-POOkw@mail.gmail.com' \
    --to=jameson.lopp@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=brianlockhart@gmail.com \
    --cc=jose.femenias@gmail.com \
    /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