From: Bernd Jendrissek <bitcoin@bpj-code•co.za>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] patents...
Date: Tue, 20 May 2014 00:15:01 +0200 [thread overview]
Message-ID: <CAF7PVPrw76Gzspo3i1pU75CV9LUite46K7yrUJMmjoHLKOdhZg@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP3sDh3Q9T0xFi7maNQR9Z6R7gQ6vT5kjchcMkD0hMHOdw@mail.gmail.com>
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.)
next prev parent reply other threads:[~2014-05-19 22:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 15:31 [Bitcoin-development] Paper Currency Jerry Felix
2014-05-17 15:45 ` Matt Whitlock
2014-05-17 16:07 ` Chris Pacia
2014-05-17 16:40 ` Gregory Maxwell
2014-05-18 11:47 ` Alex Kotenko
2014-05-18 12:14 ` Andreas Schildbach
2014-05-18 12:51 ` Alex Kotenko
2014-05-19 13:06 ` Brooks Boyd
2014-05-19 13:50 ` Alex Kotenko
2014-05-18 13:50 ` Natanael
2014-05-18 18:47 ` Alex Kotenko
2014-05-18 20:10 ` Natanael
2014-05-19 10:26 ` Alex Kotenko
2014-05-19 12:55 ` Sergio Lerner
2014-05-19 13:34 ` Martin Sip
2014-05-19 13:53 ` Alex Kotenko
2014-05-19 14:47 ` [Bitcoin-development] patents Adam Back
2014-05-19 15:09 ` Mike Hearn
2014-05-19 18:27 ` Peter Todd
2014-05-19 18:40 ` Mike Hearn
2014-05-19 18:43 ` Gregory Maxwell
2014-05-19 18:46 ` Peter Todd
2014-05-19 18:49 ` Mike Hearn
2014-05-19 22:15 ` Bernd Jendrissek [this message]
2014-05-20 10:30 ` Jeff Garzik
2014-05-18 13:50 ` [Bitcoin-development] Paper Currency Andreas Schildbach
2014-05-19 12:21 ` Mike Hearn
2014-05-19 18:20 ` Justus Ranvier
2014-05-19 18:39 ` Peter Todd
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=CAF7PVPrw76Gzspo3i1pU75CV9LUite46K7yrUJMmjoHLKOdhZg@mail.gmail.com \
--to=bitcoin@bpj-code$(echo .)co.za \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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