From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WmOqc-0003ND-T3 for bitcoin-development@lists.sourceforge.net; Mon, 19 May 2014 14:47:26 +0000 X-ACL-Warn: Received: from mout.perfora.net ([74.208.4.195]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WmOqb-00019Y-KZ for bitcoin-development@lists.sourceforge.net; Mon, 19 May 2014 14:47:26 +0000 Received: from netbook ([37.75.37.226]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0M3htJ-1X4TlC29dx-00r8jD; Mon, 19 May 2014 10:47:18 -0400 Received: by netbook (Postfix, from userid 1000) id 2E6DD2E50EE; Mon, 19 May 2014 16:47:11 +0200 (CEST) Received: by flare (hashcash-sendmail, from uid 1000); Mon, 19 May 2014 16:47:10 +0200 Date: Mon, 19 May 2014 16:47:09 +0200 From: Adam Back To: bitcoin-development@lists.sourceforge.net Message-ID: <20140519144709.GA29574@netbook.cypherspace.org> References: <5377892C.8080402@gmail.com> <5379FF38.4050909@certimix.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <5379FF38.4050909@certimix.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Hashcash: 1:20:140519:bitcoin-development@lists.sourceforge.net::0hz/Fwv/G2hIl WAT:000000000000000000004NU6 X-Hashcash: 1:20:140519:adam@cypherspace.org::AAtfhENVT1TQ2/BD:00000000000000000 0000000000000000000000002gzl X-Provags-ID: V02:K0:/1vVKr77z1sJ7WAYFj8bkqwXqD68edLfJgn4AHBmibs iuJWzmgZRfIhnRudsn6IfsKHT/dgZT7xNzJn7eWmZHsO8zdhji p6JeSyWeAyfHjT+K2B6OQNFxTqdanQuc0+jo/54Ogs6kSiQ/oY opRujVLePiOLY2LbvHUtcBbdyeLnilq5jUP3hq2Y8Qk85jxFFD HrhxebtA/7IpOyc5aOla5Y7dZ3EuyTrZauoRUklgm8pIH9w7/w fBlrRkNp9ewmBJy8g76aM1FoBCT/sa4DEKvdnL56eU1OBIKI+B PkKYsBM9+Pdca6zyg6UxMGgjqwo0OgFb6mcCWUMEdPvTPu7GpG Pf1Qa51alIZdJValkwtDMZoT0TX+8ltVbCl272Mda X-Spam-Score: -0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [74.208.4.195 listed in list.dnswl.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record X-Headers-End: 1WmOqb-00019Y-KZ Subject: [Bitcoin-development] patents... X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2014 14:47:27 -0000 someone recently wrote (not pointing fingers, nor demanding a spirited defense from that person, its a generic comment): > PS: the device has patents pending btw about patents, I wonder if people who feel the need to do that, would you consider putting those patents into like a linux foundation defensive pool? I imagine a number of other bitcoin companies have patented things, but if you think ahead a little bit, or look at prior ecash history, patents held by individuals or companies can be outright dangerous. We saw this in the past eg the digicash patents after the company went bankrupt were sold by the investor to some random large company that parked it in its huge pile of patents, didnt use it, and prevented anyone else from using it - stalling Chaum dependent payment innovation for perhaps 5 years until the thing expired, and a Chaum patent expiry party was held. Just some food for thought. hmm Yes and this topic now is more than a bit non dev related. Sorry about that. There seems to be no convenient mailing list format for non-dev stuff or I would Cc and set Reply-To for example? (Web forums somewhat suck IMO). Adam