public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Milly Bitcoin <milly@bitcoins.info>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Open Block Chain Licence, BIP[xxxx] Draft
Date: Wed, 2 Sep 2015 16:58:38 -0400	[thread overview]
Message-ID: <55E762FE.9060904@bitcoins.info> (raw)
In-Reply-To: <CADr=VrRhCeVidt_M2y8JpTHj++jZqpqjg_4f1K1rgm9FMxjhnA@mail.gmail.com>

>We don't want to play at being
> lawyer, but our review does point towards this being something worth
> coming back to.
>
> In terms of citation, we did reference a case called /Feist/.

I don't see how you can possibly conclude this effort is worth any 
additional time.  The legal reference is:  Feist Publications, Inc., v. 
Rural Telephone Service Co., 499 U.S. 340 (1991).  The court ruled that 
Rural's directory was nothing more than an alphabetic list of all 
subscribers to its service, which it was required to compile under law, 
and that no creative expression was involved. The fact that Rural spent 
considerable time and money collecting the data was irrelevant to 
copyright law, and Rural's copyright claim was dismissed.

If some entity puts a copyright notice, demands a license, signs 
software with a certificate, claims developers or miners are some legal 
entity, etc. then those entities are setting themselves up to be sued or 
prosecuted (whether legitimately or not).  There is no benefit to 
claiming such ownership or authority or issuing any license because 
nobody is going to enforce anything and they don't even have that 
authority anyway.  A 5-minute talk with an IP lawyer should confirm that 
... but you sound like you are not going to do that.  Bitcoin certainly 
attracts quite a number of completely irrational people.

Russ





      reply	other threads:[~2015-09-02 20:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 13:30 [bitcoin-dev] Open Block Chain Licence, BIP[xxxx] Draft Ahmed Zsales
2015-09-01 13:43 ` Milly Bitcoin
2015-09-01 13:50 ` Bryan Bishop
2015-09-01 15:11   ` Ahmed Zsales
2015-09-01 16:05 ` Natanael
2015-09-01 17:39 ` Luke Dashjr
2015-09-01 18:12 ` Btc Drak
2015-09-01 19:36   ` Ahmed Zsales
2015-09-01 21:36     ` Milly Bitcoin
2015-09-01 22:02       ` Ahmed Zsales
2015-09-01 22:42         ` Milly Bitcoin
2015-09-01 23:21           ` Ahmed Zsales
2015-09-01 23:40             ` Milly Bitcoin
2015-09-01 22:02     ` Btc Drak
2015-09-01 22:11       ` Ahmed Zsales
2015-09-01 22:47         ` Btc Drak
2015-09-01 22:20       ` Natanael
2015-09-01 22:28         ` Ahmed Zsales
2015-09-01 21:51 ` Wladimir J. van der Laan
2015-09-01 23:39 ` hurricanewarn1
2015-09-02  8:56 ` Warren Togami Jr.
2015-09-02 20:28   ` Ahmed Zsales
2015-09-02 20:58     ` Milly Bitcoin [this message]

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=55E762FE.9060904@bitcoins.info \
    --to=milly@bitcoins.info \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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