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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bernd.jendrissek@gmail.com>) id 1WmVpu-0002tx-2U
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 22:15:10 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.217.171 as permitted sender)
client-ip=209.85.217.171;
envelope-from=bernd.jendrissek@gmail.com;
helo=mail-lb0-f171.google.com;
Received: from mail-lb0-f171.google.com ([209.85.217.171])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WmVps-0007ry-Ih
for bitcoin-development@lists.sourceforge.net;
Mon, 19 May 2014 22:15:10 +0000
Received: by mail-lb0-f171.google.com with SMTP id 10so4556683lbg.16
for <bitcoin-development@lists.sourceforge.net>;
Mon, 19 May 2014 15:15:02 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.153.5.37 with SMTP id cj5mr9044311lad.48.1400537701952; Mon,
19 May 2014 15:15:01 -0700 (PDT)
Sender: bernd.jendrissek@gmail.com
Received: by 10.112.94.228 with HTTP; Mon, 19 May 2014 15:15:01 -0700 (PDT)
In-Reply-To: <CANEZrP3sDh3Q9T0xFi7maNQR9Z6R7gQ6vT5kjchcMkD0hMHOdw@mail.gmail.com>
References: <BAY173-W1475F72C70BC089A82C20FCC300@phx.gbl>
<5377892C.8080402@gmail.com>
<CAAS2fgS-Ewj3T0-d=h7ET9dCz3+NPPYVOLDWd7T7oYY95x-sUA@mail.gmail.com>
<CALDj+Bbsb6JiLabTBx21k02dDvnmZZDCXmJ2mnh7DngBon202w@mail.gmail.com>
<5379FF38.4050909@certimix.com>
<20140519144709.GA29574@netbook.cypherspace.org>
<CANEZrP3sDh3Q9T0xFi7maNQR9Z6R7gQ6vT5kjchcMkD0hMHOdw@mail.gmail.com>
Date: Tue, 20 May 2014 00:15:01 +0200
X-Google-Sender-Auth: HJfLxM4FyqrGcE7jE7pKTeQCuCY
Message-ID: <CAF7PVPrw76Gzspo3i1pU75CV9LUite46K7yrUJMmjoHLKOdhZg@mail.gmail.com>
From: Bernd Jendrissek <bitcoin@bpj-code.co.za>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.5 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(bernd.jendrissek[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WmVps-0007ry-Ih
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] patents...
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 19 May 2014 22:15:10 -0000
On Mon, May 19, 2014 at 5:09 PM, Mike Hearn <mike@plan99.net> wrote:
> Most companies (Google certainly included) have therefore banned their staff
> from reading patents,
Bitcoin is not Google though, and applying the same patent protocols
to Bitcoin as in Google is drawing a false equivalence between the
two. Google can survive single or triple damages, so it makes sense to
hope that of those patents you necessarily violate due to the size of
your operations, they attract only single damages. Google has so many
fingers in so many pies that violating some patents is a question of
when, not if. Bitcoin has a far narrower scope than trying to take
over the world (and moon).
Happy reading: http://endsoftpatents.org/2010/03/transcript-tridgell-patents/
TL;DR: If even single damages result in commercial death, you better
pay attention to patents, to reduce the chances of accidentally
running into one.
(But Bitcoin is not ccache either - it's all about money and it isn't
inconceivable that a patent infringement suit might not result in
commercial death. The right answer here isn't as obvious as you make
it out to be.)
|
