summaryrefslogtreecommitdiff
path: root/cd/cfcab0ca51a124af7986c407ce4f78fc525a4f
blob: ff86f4b56bde50a33469857d61443393bbe01393 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
Return-Path: <bedriguler@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id DF3E4D6D
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 13 Feb 2018 15:47:52 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DCE7218A
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 13 Feb 2018 15:47:51 +0000 (UTC)
Received: by mail-wm0-f54.google.com with SMTP id r78so16873624wme.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 13 Feb 2018 07:47:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to; 
	bh=R42Ml7zXd/YHyknw69zKm1pra2Fiany4WT+67Dt9yeA=;
	b=H+UnuXb4C2U4W5k59GLNESKpLBhrThcQPAThgWI2G99UeRYH97W489cJ7GVcJM9T/G
	6h7dZ0DyqnpcCCQ42ERb46ula2Oy5dWe+WwVymWm+02hF6r6d/ZIrkqpVQmEudX8BvkJ
	53mv7Sp9Td6WG/y/aGG098wkRpxZ+Rae+7s8a0+9d/+L3JlCkygrzhSVnRCO1SZMAP7O
	VGT0rluiw5sosqfWX9XSPybnEnBDwGxgLTFv/+R2VJPQ43AOUrL5KQ++sgVKDqhEPPPQ
	36nrdnOzrf+1vqbL60lL9KQ+sxkTN9gH7qR66gIfETgZFLYFKXd7NDuqc537D9ECOdGu
	zRjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to;
	bh=R42Ml7zXd/YHyknw69zKm1pra2Fiany4WT+67Dt9yeA=;
	b=camT16SognJ3rk0FFXWLDiQnkzf6Zx5x1UVuwzLUCmjlYarLDpd2MKpfXx5gBtjYKg
	/Ru2eWT8MhD4sGzncdU206UcUUX9XXYvJh6NMyjb2l+64eZx+WgI2XvlC7oK1+YGi2Bn
	bAU6ODycaJB2TSmS9bafwg/6i5zOEiyRdoXjBaorJAkF8KCNiy30zjM0AKbue/0GJ1pU
	aTJ/OPCJtDNk4MtCypJGkxQf+CpoPYsIXbZADUnBk8MV2DBy+Lda3czkh/z8XjqVYHYP
	yZQXeG/w7MT9saBSFAHnk4NcO+em8vQWcsByK39VckqI/175bnRVhemTKVpHpWpCN132
	B89w==
X-Gm-Message-State: APf1xPAXV9A67YiaT1pfDBJWJXDHf9GlMf1CzEoCgzKd/n1vCr/jV9qa
	5reMC1Q6TIEcF5VoSJ+wuoUIN8MfO02hQFO5TSc=
X-Google-Smtp-Source: AH8x224YD0j3ik+7n9QweU8GQcIs0Qt8XLCGQDDaYW6vJr87vYf7ITOQ59TEjER1GxWy1OTHMxUXItPGxda1hjfccCA=
X-Received: by 10.80.195.18 with SMTP id a18mr2753486edb.178.1518536870429;
	Tue, 13 Feb 2018 07:47:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.134.189 with HTTP; Tue, 13 Feb 2018 07:47:09 -0800 (PST)
In-Reply-To: <CADL_X_cNdhydrn0D0vXSXK1s42dC7-n_7oW2TQJcpvkG6Oa0ow@mail.gmail.com>
References: <65F92B37-48C1-4CD5-8F17-47BF9BD231A9@gmail.com>
	<CAAt2M1-fEnQxjX40c-sjUYpfLpJtS-fy5t244vUOZSb8Pm=MrQ@mail.gmail.com>
	<CADL_X_cNdhydrn0D0vXSXK1s42dC7-n_7oW2TQJcpvkG6Oa0ow@mail.gmail.com>
From: Bedri Ozgur Guler <bedriguler@gmail.com>
Date: Tue, 13 Feb 2018 18:47:09 +0300
Message-ID: <CAAVrV-xFtTZMjrBa_zvgDjwAJV7gz-6Y8usyE8oM_EMDvHRiYg@mail.gmail.com>
To: Jameson Lopp <jameson.lopp@gmail.com>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="94eb2c1cd364bda21a056519eaaf"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Tue, 13 Feb 2018 16:22:18 +0000
Subject: Re: [bitcoin-dev] Possible change to the MIT license
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Feb 2018 15:47:53 -0000

--94eb2c1cd364bda21a056519eaaf
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello,
The use of name Bitcoin cannot be avoided due to it's nature of being a
Protocol. Prohibition of usage of it as a "brand name" is just like
prohibiting the word "Linux", which is the name of the kernel, being used
as a brand name or part of a brand name. If that had happened, systems
based on Linux kernel couldn't have used Linux word in their brands. The
licence in the Linux example is GPL but it does not really differ so much.
Making a protocol name a Trademark(TM) name and prohibiting it's use may
solve some confusions and bad reputation causing actions but it also
prohibits the protocol to be used widely so damages the credibility of the
protocol itself which was born to be an independent, freedom-based,
government-free, boundaries-free etc. approach to the current corrupted
monetary system.

If precautions should be taken to control the usage of Bitcoin word in
various positions and cases, it should be done in such a way that it should
not contradict with the philosophy of the Bitcoin itself. Social
/marketing-based approaches proposed by Jameson Lopp will be more logical
and freedom based. Trademarking and in some sense Cartel-ing the Bitcoin
Protocol who arose against trademarks and cartels on "money" will destroy
it's own roots and birth-right of existence in my opinion.

Bedri =C3=96zg=C3=BCr G=C3=BCler

On Tue, Feb 13, 2018 at 6:24 PM, 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 shoul=
d
> 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=C3=91UELO 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 UNLES=
S
>> THE SOFTWARE PRODUCED BY THAT PROJECT IS FULLY COMPATIBLE WITH THE BITCO=
IN
>> (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
>
>

--94eb2c1cd364bda21a056519eaaf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div>The use of name Bitcoin cannot be avoided due t=
o it&#39;s nature of being a Protocol. Prohibition of usage of it as a &quo=
t;brand name&quot; is just like prohibiting the word &quot;Linux&quot;, whi=
ch is the name of the kernel, being used as a brand name or part of a brand=
 name. If that had happened, systems based on Linux kernel couldn&#39;t hav=
e used Linux word in their brands. The licence in the Linux example is GPL =
but it does not really differ so much.</div><div>Making a protocol name a T=
rademark(TM) name and prohibiting it&#39;s use may solve some confusions an=
d bad reputation causing actions but it also prohibits the protocol to be u=
sed widely so damages the credibility of the protocol itself which was born=
 to be an independent, freedom-based, government-free, boundaries-free etc.=
 approach to the current corrupted monetary system.</div><div><br></div><di=
v>If precautions should be taken to control the usage of Bitcoin word in va=
rious positions and cases, it should be done in such a way that it should n=
ot contradict with the philosophy of the Bitcoin itself. Social /marketing-=
based approaches proposed by=C2=A0<span style=3D"color:rgb(34,34,34);font-f=
amily:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-liga=
tures:normal;font-variant-caps:normal;letter-spacing:normal;text-align:left=
;text-indent:0px;text-transform:none;white-space:nowrap;word-spacing:0px;ba=
ckground-color:rgb(255,255,255);text-decoration-style:initial;text-decorati=
on-color:initial;float:none;display:inline">Jameson Lopp</span> will be mor=
e logical and freedom based. Trademarking and in some sense Cartel-ing the =
Bitcoin Protocol who arose against trademarks and cartels on &quot;money&qu=
ot; will destroy it&#39;s own roots and birth-right of=C2=A0existence in my=
 opinion.</div><div><br></div><div>Bedri =C3=96zg=C3=BCr G=C3=BCler</div></=
div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Feb 1=
3, 2018 at 6:24 PM, Jameson Lopp via bitcoin-dev <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitc=
oin-dev@lists.linuxfoundation.org</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><div dir=3D"ltr">If I&#39;m understanding the problem being =
stated correctly:<br><br>&quot;Bitcoin is under a branding attack by fork c=
oins.&quot;<div><br></div><div>The proposed solution is to disincentivize f=
ork coins from using the word Bitcoin by altering the license terms. I&#39;=
m not a lawyer, but it seems to me that the words of the license are basica=
lly useless unless there is an entity that intends to make use of court sys=
tems to threaten noncompliant projects into submission.</div><div><br></div=
><div>In my opinion, the perceived attack on Bitcoin here is social / marke=
ting-based, thus it makes sense that any defense against said attack should=
 also be social / marketing-based. I don&#39;t think that Bitcoin should be=
 reliant upon courts or governments to defend itself against attacks of any=
 form.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"=
><div><div class=3D"h5">On Tue, Feb 13, 2018 at 9:25 AM, Natanael via bitco=
in-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfound=
ation.org" target=3D"_blank">bitcoin-dev@lists.<wbr>linuxfoundation.org</a>=
&gt;</span> wrote:<br></div></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><di=
v class=3D"h5"><div dir=3D"auto"><span><div><br><div class=3D"gmail_extra">=
<br><div class=3D"gmail_quote">Den 13 feb. 2018 15:07 skrev &quot;JOSE FEME=
NIAS CA=C3=91UELO via bitcoin-dev&quot; &lt;<a href=3D"mailto:bitcoin-dev@l=
ists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfounda<w=
br>tion.org</a>&gt;:<blockquote class=3D"m_-4780499977721016034m_4333531158=
757201305quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;paddi=
ng-left:1ex">
***<br>
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 (COR=
E) BLOCKCHAIN<br>
***<br></blockquote></div></div></div><div dir=3D"auto"><br></div></span><d=
iv dir=3D"auto">That&#39;s better solved with trademarks. (whoever would be=
 the trademark holder - Satoshi?)=C2=A0=C2=A0</div><div dir=3D"auto"><br></=
div><div dir=3D"auto">This would also prohibit any reimplementation that&#3=
9;s not formally verified to be perfectly compatible from using the name.=
=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">It also adds lega=
l uncertainty.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">Ano=
ther major problem is that it neither affects anybody forking older version=
s of Bitcoin, not people using existing independent blockchain implementati=
ons and renaming them Bitcoin-Whatsoever.=C2=A0</div><div dir=3D"auto"><br>=
</div><div dir=3D"auto">And what happens when an old version is technically=
 incompatible with a future version by the Core team due to not understandi=
ng various new softforks? Which version wins the right to the name?=C2=A0</=
div><div dir=3D"auto"><br></div><div dir=3D"auto">Also, being unable to eve=
n mention Bitcoin is overkill.=C2=A0</div><div dir=3D"auto"><br></div><div =
dir=3D"auto">The software license also don&#39;t affect the blockchain data=
.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gm=
ail_extra"><div class=3D"gmail_quote"><blockquote class=3D"m_-4780499977721=
016034m_4333531158757201305quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"></blockquote></div></div></div></div>
<br></div></div><span class=3D"">______________________________<wbr>_______=
__________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundat<wbr>ion.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-d<wbr>ev</a><br>
<br></span></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
<br></blockquote></div><br></div>

--94eb2c1cd364bda21a056519eaaf--