summaryrefslogtreecommitdiff
path: root/ac/79d0a4cbdc15a9837fec34d144d0c1b0c2f809
blob: 25250d45e08ceaddbb16cb92c98c28588b6a4856 (plain)
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
91
92
93
94
95
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@bitpay.com>) id 1WmhK9-0006e3-CE
	for bitcoin-development@lists.sourceforge.net;
	Tue, 20 May 2014 10:31:09 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 74.125.82.172 as permitted sender)
	client-ip=74.125.82.172; envelope-from=jgarzik@bitpay.com;
	helo=mail-we0-f172.google.com; 
Received: from mail-we0-f172.google.com ([74.125.82.172])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WmhK3-0002WX-Sm
	for bitcoin-development@lists.sourceforge.net;
	Tue, 20 May 2014 10:31:09 +0000
Received: by mail-we0-f172.google.com with SMTP id k48so293135wev.3
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 20 May 2014 03:30:57 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type;
	bh=perztZTALhiDjVtDOBXtpS1bd2hCnWr7lcDW9qRah+U=;
	b=G0Yp33Eo+CcXJ4Gtb3pMikMhppGvfJgm+6TFK74r1wjTHk93PtNiI4j/+GXZUUBZ3z
	TESzALnlQS6cNv5hLdw6SzDp+B7G0Uq/d7UgTvY/MUKS2LxVV36Nh+hQpegipdEG+Mn5
	UpzT0tkheJFS96t69ZfClABCgFxvvcYWk4+wX9i4NzrSPryO+8Z07wmGonRhotbhk6Fy
	ugPD7ndB6OYNojz/+k1zu055jRTHPQ5wyjGt0SPVG9+tP6SYFa5mXOqhXHMjCVI2Ygjn
	wk2C7sm2CJk9XFFtX/EqOAZCx4Q0rBv+Etz63WkjbBNGzHKuPzPF+5s0yct1e4LVCitj
	0RjQ==
X-Gm-Message-State: ALoCoQkmYWVhxsAVX2K0tohzukNxaGC++xAMVSfqaMq58g8Q4qhAjzi8mfPt/y9dnO3hFIcFKS56
X-Received: by 10.180.93.101 with SMTP id ct5mr3158502wib.23.1400581857563;
	Tue, 20 May 2014 03:30:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.240.166 with HTTP; Tue, 20 May 2014 03:30:37 -0700 (PDT)
In-Reply-To: <20140519144709.GA29574@netbook.cypherspace.org>
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>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Tue, 20 May 2014 06:30:37 -0400
Message-ID: <CAJHLa0P8iuh3atbh8hwGaW24qb3JhGBBRyHZObuU0bGGWLVVXg@mail.gmail.com>
To: Adam Back <adam@cypherspace.org>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
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 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	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: 1WmhK3-0002WX-Sm
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: Tue, 20 May 2014 10:31:09 -0000

On Mon, May 19, 2014 at 10:47 AM, Adam Back <adam@cypherspace.org> wrote:
> 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).

There is the little-used "bitcoin-list" on SourceForge that claims a
rubric of "general discussion":
https://sourceforge.net/p/bitcoin/mailman/?source=navbar

I just subscribed there.

We can "reboot" that list with a couple new rules such as
a) be good to each other.  consistent rude behavior gets the boot.
b) anything related to decentralization, consensus, proven data
structures or crypto is on-topic

-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/