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
|
Return-Path: <ahmedzsales18@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 1C41E1478
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 22:28:30 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f51.google.com (mail-vk0-f51.google.com
[209.85.213.51])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 52F32EC
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 22:28:29 +0000 (UTC)
Received: by vkbf67 with SMTP id f67so60317424vkb.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 01 Sep 2015 15:28:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type; bh=BUkYn0j2O/zfC+FJ5RQU+ocILK1HrN/cAyAe26ZPgKU=;
b=0/ZKPoOWBqpGrq/ZwY6cevu1YqSk6tz/CLBwwdevMB0zbMRwG0ZBG9egivGuOiU8G7
c1D29JB/InnyiK94AlSJK/8cSwq9GYcbusWQMoMjY2pJh7Vgalj84Bg3C2QLrehbNqKG
1vNA4Dv2l8tzGPW/525gYrjCQMkA9T9T5mBCg4mkwD4PdwEHzpBnvzsbnQ8geBvFRsMX
2+mjgAyIv192aFAAuDh8xl4sL8MmriCj6pypYyb5UBx050CBNp24s3nx3LWcCrzdP3t9
iu0O1UQJK2XOCYdrYloNS3Mhq7EMyIxaDtLueXb4KPyqk70FkvHGnSAeypNKnsiPrHZa
yQ6w==
MIME-Version: 1.0
X-Received: by 10.52.163.50 with SMTP id yf18mr34149043vdb.93.1441146508668;
Tue, 01 Sep 2015 15:28:28 -0700 (PDT)
Received: by 10.31.109.134 with HTTP; Tue, 1 Sep 2015 15:28:28 -0700 (PDT)
In-Reply-To: <CAAt2M1_qSs9UJ+sqjnvvmx7X29THW1jOFF4DjDbfzLLb+zSRTg@mail.gmail.com>
References: <CADr=VrRT2tdN0jjkZ7HjjeyqonrHG=j+uh8m1L2nhew7c1gnng@mail.gmail.com>
<CADJgMztScEsDEy277Jksy2RckbpzeRw6RbQzyVrdkjJSS=hHPA@mail.gmail.com>
<CADr=VrQ42Gqv7fUFVpaburw0=08SNXb0TUCBWd3arREbpdfCkA@mail.gmail.com>
<CADJgMzvBCiHJo++zrZtA4XuMnNd8D8fHEiS4E2OfoKm4j8sY1w@mail.gmail.com>
<CAAt2M1_qSs9UJ+sqjnvvmx7X29THW1jOFF4DjDbfzLLb+zSRTg@mail.gmail.com>
Date: Tue, 1 Sep 2015 23:28:28 +0100
Message-ID: <CADr=VrRbZXJ=6Z4AKHzYiC4hv90z=Gb+HUgN-o1KhTGPegN2pw@mail.gmail.com>
From: Ahmed Zsales <ahmedzsales18@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11c2ce38b7f6fb051eb71139
X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,
HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Open Block Chain Licence, BIP[xxxx] Draft
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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, 01 Sep 2015 22:28:30 -0000
--001a11c2ce38b7f6fb051eb71139
Content-Type: text/plain; charset=UTF-8
Your points are interesting, but they are covered:
https://drive.google.com/file/d/0BwEbhrQ4ELzBMVFxajNZa2hzMTg/view?usp=sharing
Your general point: "Better just put everything in public domain" is the
reason why Bitcoin works, but taken to the extreme it is an argument
against attempts to obfuscate transaction ownership.
Regards,
Ahmed
On Tue, Sep 1, 2015 at 11:20 PM, Natanael <natanael.l@gmail.com> wrote:
>
> Den 2 sep 2015 00:03 skrev "Btc Drak via bitcoin-dev" <
> bitcoin-dev@lists.linuxfoundation.org>:
> >
> > I think it gets worse. Who are the copyright owners (if this actually
> > applies). You've got people publishing transaction messages, you've
> > got miners reproducing them and publishing blocks. Who are all the
> > parties involved? Then to take pedantry to the next level, does a
> > miner have permission to republish messages? How do you know? What if
> > the messages are reproducing others copyright/licensed material? It's
> > not possible to license someone else's work. There are plenty rabbit
> > holes to go down with this train of thought.
>
> Worse yet - transaction malleability creates derative works with multiple
> copyright holders (the original one, plus the author of the modification).
> Is that even legal to do? What to do if a miner unknowingly accepts an
> illegally modified transaction in a block? And can he who modified it ALSO
> sue anybody replicating the block for infringement?
>
> Better just put everything in public domain, or the closest thing to it
> you can get. Copyright in the blockchain is essentially the DVDCSS illegal
> prime mess all over again, but in a P2P network.
>
--001a11c2ce38b7f6fb051eb71139
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div style=3D"font-size:12.8000001907349px">Your points ar=
e interesting, but they are covered:=C2=A0</div><div style=3D"font-size:12.=
8000001907349px"><br></div><div style=3D"font-size:12.8000001907349px"><a h=
ref=3D"https://drive.google.com/file/d/0BwEbhrQ4ELzBMVFxajNZa2hzMTg/view?us=
p=3Dsharing" target=3D"_blank">https://drive.google.com/file/d/0BwEbhrQ4ELz=
BMVFxajNZa2hzMTg/view?usp=3Dsharing</a><br></div><div style=3D"font-size:12=
.8000001907349px"><br></div><div style=3D"font-size:12.8000001907349px">You=
r general point:=C2=A0<span style=3D"font-size:12.8000001907349px">"Be=
tter just put everything in public domain" is the reason why Bitcoin w=
orks, but taken to the extreme it is an argument against attempts to obfusc=
ate transaction ownership.</span></div><div style=3D"font-size:12.800000190=
7349px"><br></div><div style=3D"font-size:12.8000001907349px">Regards,</div=
><div style=3D"font-size:12.8000001907349px"><br></div><div style=3D"font-s=
ize:12.8000001907349px">Ahmed</div></div><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Tue, Sep 1, 2015 at 11:20 PM, Natanael <span dir=
=3D"ltr"><<a href=3D"mailto:natanael.l@gmail.com" target=3D"_blank">nata=
nael.l@gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote"=
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><s=
pan class=3D""><p dir=3D"ltr"><br>
Den 2 sep 2015 00:03 skrev "Btc Drak via bitcoin-dev" <<a href=
=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin=
-dev@lists.linuxfoundation.org</a>>:<br>
><br>
> I think it gets worse. Who are the copyright owners (if this actually<=
br>
> applies). You've got people publishing transaction messages, you&#=
39;ve<br>
> got miners reproducing them and publishing blocks. Who are all the<br>
> parties involved? Then to take pedantry to the next level, does a<br>
> miner have permission to republish messages? How do you know? What if<=
br>
> the messages are reproducing others copyright/licensed material? It=
9;s<br>
> not possible to license someone else's work. There are plenty rabb=
it<br>
> holes to go down with this train of thought.</p>
</span><p dir=3D"ltr">Worse yet - transaction malleability creates derative=
works with multiple copyright holders (the original one, plus the author o=
f the modification). Is that even legal to do? What to do if a miner unknow=
ingly accepts an illegally modified transaction in a block? And can he who =
modified it ALSO sue anybody replicating the block for infringement? </p>
<p dir=3D"ltr">Better just put everything in public domain, or the closest =
thing to it you can get. Copyright in the blockchain is essentially the DVD=
CSS illegal prime mess all over again, but in a P2P network. </p>
</blockquote></div><br></div>
--001a11c2ce38b7f6fb051eb71139--
|
