summaryrefslogtreecommitdiff
path: root/87/e2cb0d9adf25612c1e10d2c1630cb247d311b1
blob: de931d7b070ac2fcaff314ac712a4541c9ff9eff (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
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <slashdevnull@hotmail.com>) id 1YqQjP-0004K2-3N
	for bitcoin-development@lists.sourceforge.net;
	Thu, 07 May 2015 18:41:11 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of hotmail.com
	designates 65.55.111.163 as permitted sender)
	client-ip=65.55.111.163; envelope-from=slashdevnull@hotmail.com;
	helo=BLU004-OMC4S24.hotmail.com; 
Received: from blu004-omc4s24.hotmail.com ([65.55.111.163])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1YqQjN-00017j-EW
	for bitcoin-development@lists.sourceforge.net;
	Thu, 07 May 2015 18:41:11 +0000
Received: from BLU436-SMTP31 ([65.55.111.135]) by BLU004-OMC4S24.hotmail.com
	over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751);
	Thu, 7 May 2015 11:41:04 -0700
X-TMN: [LIVcuDf4Jmq2f8hcc6XBneVW3QVXMqVD]
X-Originating-Email: [slashdevnull@hotmail.com]
Message-ID: <BLU436-SMTP318E346839A76DB15D7DC5C6DF0@phx.gbl>
User-Agent: Microsoft-MacOutlook/14.4.9.150325
Date: Fri, 8 May 2015 02:40:50 +0800
From: Gavin Costin <slashdevnull@hotmail.com>
To: Mike Hearn <mike@plan99.net>,
	Btc Drak <btcdrak@gmail.com>
Thread-Topic: [Bitcoin-development] Block Size Increase
References: <554A91BE.6060105@bluematt.me>
	<CANEZrP3wGWHdz+ut6pvke5TJJsc1rTFt8sn2KziX35oL5LAsyg@mail.gmail.com>
	<CABm2gDpDvk2VsQ+mJ-BoeBKmvu9jBXNujZEFKuCStRNjFL6VOA@mail.gmail.com>
	<CANEZrP2zAGCCBhNa4=9yw+A_Dn5o4SQXoPTE_qcJzZ1dFuF2tw@mail.gmail.com>
	<CABm2gDqd6iHRUDKZWWTudcC1QkYa+rCuHjz7pMC2K1Db8wpgfA@mail.gmail.com>
	<CANEZrP1CU0kB0vXeXUX1L8byaT-Zf2xg+3N+GeNthi_i6bn1qw@mail.gmail.com>
	<CABsx9T2Nxvr4fqREMw3_LXftzsxrUAR1+9sVMa8_EpTnH1nN1Q@mail.gmail.com>
	<554BA032.4040405@bluematt.me>
	<CANEZrP3yM9wsSPNgpOsXDk-DjUy5PW2XuRTvK2AyCNbVJ5hZHw@mail.gmail.com>
	<CADJgMzti7ROH90APiwg4NOAT5+Av=4i295b8VN0sbSLr4+WWRw@mail.gmail.com>
	<CANEZrP39jWHLF02z-81Z4+9X1vH5+hMuS=-3ED81=Q1o9U=DKw@mail.gmail.com>
In-Reply-To: <CANEZrP39jWHLF02z-81Z4+9X1vH5+hMuS=-3ED81=Q1o9U=DKw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="B_3513897662_15840326"
X-OriginalArrivalTime: 07 May 2015 18:41:03.0663 (UTC)
	FILETIME=[5F0A73F0:01D088F5]
X-Spam-Score: -0.5 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(slashdevnull[at]hotmail.com)
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [65.55.111.163 listed in list.dnswl.org]
	-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars
X-Headers-End: 1YqQjN-00017j-EW
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Block Size Increase
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: Thu, 07 May 2015 18:41:11 -0000

--B_3513897662_15840326
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Can anyone opposed to this proposal articulate in plain english the worst
case scenario(s) if it goes ahead?

Some people in the conversation appear to be uncomfortable, perturbed,
defensive etc about the proposal =8A. But I am not seeing specifics on why it
is not a feasible plan.

From:  Mike Hearn <mike@plan99.net>
Date:  Friday, 8 May, 2015 2:06 am
To:  Btc Drak <btcdrak@gmail.com>
Cc:  Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject:  Re: [Bitcoin-development] Block Size Increase

> I think you are rubbing against your own presupposition that people must =
find
> and alternative right now. Quite a lot here do not believe there is any
> urgency, nor that there is an immanent problem that has to be solved befo=
re
> the sky falls in.

I have explained why I believe there is some urgency, whereby "some urgency=
"
I mean, assuming it takes months to implement, merge, test, release and for
people to upgrade.

But if it makes you happy, imagine that this discussion happens all over
again next year and I ask the same question.

---------------------------------------------------------------------------=
-
-- One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications Performance
metrics, stats and reports that give you Actionable Insights Deep dive
visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y____________________=
_
__________________________ Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


--B_3513897662_15840326
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif;"><div>Can anyone opposed to this pr=
oposal articulate in plain english the worst case scenario(s) if it goes ahe=
ad?</div><div><br></div><div>Some people in the conversation appear to be un=
comfortable, perturbed, defensive etc about the proposal &#8230;. But I am n=
ot seeing specifics on why it is not a feasible plan. &nbsp;</div><div><br><=
/div><div><span style=3D"font-family: Calibri; font-size: 11pt; font-weight: b=
old;">From: </span><span style=3D"font-family: Calibri; font-size: 11pt;"> Mik=
e Hearn &lt;</span><a href=3D"mailto:mike@plan99.net" style=3D"font-family: Cali=
bri; font-size: 11pt;">mike@plan99.net</a><span style=3D"font-family: Calibri;=
 font-size: 11pt;">&gt;</span></div><span id=3D"OLK_SRC_BODY_SECTION"><div sty=
le=3D"font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDE=
R-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDIN=
G-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT=
: medium none; PADDING-TOP: 3pt"><span style=3D"font-weight:bold">Date: </span=
> Friday, 8 May, 2015 2:06 am<br><span style=3D"font-weight:bold">To: </span> =
Btc Drak &lt;<a href=3D"mailto:btcdrak@gmail.com">btcdrak@gmail.com</a>&gt;<br=
><span style=3D"font-weight:bold">Cc: </span> Bitcoin Dev &lt;<a href=3D"mailto:=
bitcoin-development@lists.sourceforge.net">bitcoin-development@lists.sourcef=
orge.net</a>&gt;<br><span style=3D"font-weight:bold">Subject: </span> Re: [Bit=
coin-development] Block Size Increase<br></div><div><br></div><div dir=3D"ltr"=
><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div>I thi=
nk you are rubbing against your own presupposition that people must find and=
 alternative right now. Quite a lot here do not believe there is any urgency=
, nor that there is an immanent problem that has to be solved before the sky=
 falls in.</div></div></div></div></blockquote><div><br></div><div>I have ex=
plained why I believe there is some urgency, whereby "some urgency" I mean, =
assuming it takes months to implement, merge, test, release and for people t=
o upgrade.</div><div><br></div><div>But if it makes you happy, imagine that =
this discussion happens all over again next year and I ask the same question=
.</div></div><br></div></div>
---------------------------------------------------------------------------=
---
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
<a href=3D"http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___________=
____________________________________">http://ad.doubleclick.net/ddm/clk/2904=
20510;117567292;y_______________________________________________</a>
Bitcoin-development mailing list
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-developm=
ent@lists.sourceforge.net</a>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development">=
https://lists.sourceforge.net/lists/listinfo/bitcoin-development</a>
</span></body></html>

--B_3513897662_15840326--