public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: hurricanewarn1@aol.com
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Open Block Chain Licence, BIP[xxxx] Draft
Date: Tue, 1 Sep 2015 19:39:43 -0400	[thread overview]
Message-ID: <14f8b47cd5b-1774-e482@webprd-a78.mail.aol.com> (raw)
In-Reply-To: <CADr=VrRT2tdN0jjkZ7HjjeyqonrHG=j+uh8m1L2nhew7c1gnng@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1820 bytes --]


 The only reason someone would want to make a license is so they can sue/threaten people for not following the license rules. At best this is pointless since Bitcoin cannot be controlled, and at worst it will result in a group of people using coercion against the community to gain profits. 
 
 There is no legal ground for anyone to make a Bitcoin license, it simply wouldn't stand in court. Not even the MIT license is valid or meaningful. But I wouldn't be surprised if people tried scaring people with a license even if they knew it was invalid.
    
    
    It's actually disgusting that you wrote what people are allowed and not allowed to do with Bitcoin. Pure centralization ideology. Maybe go work for the government and make regulations instead of trying to centralize one of the only de-centralized things left on the planet.
    
   
    

 

 

-----Original Message-----
From: Ahmed Zsales via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Sent: Tue, Sep 1, 2015 9:30 am
Subject: [bitcoin-dev]  Open Block Chain Licence, BIP[xxxx] Draft


 
Hello,  
   
  
  
We believe the network requires a block chain licence to supplement the existing MIT Licence which we believe only covers the core reference client software.  
  
   
  
  
Replacing or amending the existing MIT Licence is beyond the scope of this draft BIP.  
  
   
  
  
Rationale and details of our draft BIP for discussion and evaluation are here:  
  
   
  
  
   https://drive.google.com/file/d/0BwEbhrQ4ELzBMVFxajNZa2hzMTg/view?usp=sharing   
  
  
   
  
  
Regards,  
  
   
  
  
Ahmed  
 
 

_______________________________________________
bitcoin-dev mailing
list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

 

[-- Attachment #2: Type: text/html, Size: 3074 bytes --]

  parent reply	other threads:[~2015-09-01 23:39 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 [this message]
2015-09-02  8:56 ` Warren Togami Jr.
2015-09-02 20:28   ` Ahmed Zsales
2015-09-02 20:58     ` Milly Bitcoin

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=14f8b47cd5b-1774-e482@webprd-a78.mail.aol.com \
    --to=hurricanewarn1@aol.com \
    --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