summaryrefslogtreecommitdiff
path: root/2f/5af4f73dfa4f438f0840a4a0b19cb925886b2b
blob: d4d34f2b736f0166ce07907b9bdb8bc79c889c90 (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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <thyshizzle@outlook.com>) id 1YzNeS-0006b9-1Y
	for bitcoin-development@lists.sourceforge.net;
	Mon, 01 Jun 2015 11:13:04 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of outlook.com
	designates 65.54.190.215 as permitted sender)
	client-ip=65.54.190.215; envelope-from=thyshizzle@outlook.com;
	helo=BAY004-OMC4S13.hotmail.com; 
Received: from bay004-omc4s13.hotmail.com ([65.54.190.215])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
	(Exim 4.76) id 1YzNeQ-0007DP-TD
	for bitcoin-development@lists.sourceforge.net;
	Mon, 01 Jun 2015 11:13:04 +0000
Received: from BAY403-EAS101 ([65.54.190.200]) by BAY004-OMC4S13.hotmail.com
	over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751);
	Mon, 1 Jun 2015 04:12:57 -0700
X-TMN: [pVYd7r/d3FLtJKFC6Jy1QlhVXfbQ6JNk]
X-Originating-Email: [thyshizzle@outlook.com]
Message-ID: <BAY403-EAS10178999B08666884BFEDD1C2B60@phx.gbl>
Content-Type: multipart/related;
	boundary="_e8615478-356b-424a-bc04-874f011bf32b_"
MIME-Version: 1.0
To: Mike Hearn <mike@plan99.net>, Alex Mizrahi <alex.mizrahi@gmail.com>
From: Thy Shizzle <thyshizzle@outlook.com>
Date: Mon, 1 Jun 2015 21:12:34 +1000
X-OriginalArrivalTime: 01 Jun 2015 11:12:57.0403 (UTC)
	FILETIME=[E9E880B0:01D09C5B]
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
	(thyshizzle[at]outlook.com)
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [65.54.190.215 listed in list.dnswl.org]
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.0 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YzNeQ-0007DP-TD
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: Block Size Increase Requirements
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: Mon, 01 Jun 2015 11:13:04 -0000

--_e8615478-356b-424a-bc04-874f011bf32b_
Content-Type: multipart/alternative;
	boundary="_aef2923c-99c8-45eb-8cc8-1cf19556041d_"

--_aef2923c-99c8-45eb-8cc8-1cf19556041d_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

WOW!!!! Way to burn your biggest adopters who put your transactions into th=
e chain.......what a douche.
________________________________
From: Mike Hearn<mailto:mike@plan99.net>
Sent: =E2=80=8E1/=E2=80=8E06/=E2=80=8E2015 8:15 PM
To: Alex Mizrahi<mailto:alex.mizrahi@gmail.com>
Cc: Bitcoin Dev<mailto:bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Fwd: Block Size Increase Requirements

Whilst it would be nice if miners in China can carry on forever regardless
of their internet situation=2C nobody has any inherent "right" to mine if
they can't do the job - if miners in China can't get the trivial amounts of
bandwidth required through their firewall and end up being outcompeted then
OK=2C too bad=2C we'll have to carry on without them.

But I'm not sure why it should be a big deal. They can always run a node on
a server in Taiwan and connect the hardware to it via a VPN or so.

--_aef2923c-99c8-45eb-8cc8-1cf19556041d_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html=3B charset=3Dutf-8">
</head>
<body>
<div>
<div style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=3B">WOW!=
!!! Way to burn your biggest adopters who put your transactions into the ch=
ain.......what a douche.</div>
</div>
<div dir=3D"ltr">
<hr>
<span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=3B font=
-weight: bold=3B">From:
</span><span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=
=3B"><a href=3D"mailto:mike@plan99.net">Mike Hearn</a></span><br>
<span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=3B font=
-weight: bold=3B">Sent:
</span><span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=
=3B">=E2=80=8E1/=E2=80=8E06/=E2=80=8E2015 8:15 PM</span><br>
<span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=3B font=
-weight: bold=3B">To:
</span><span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=
=3B"><a href=3D"mailto:alex.mizrahi@gmail.com">Alex Mizrahi</a></span><br>
<span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=3B font=
-weight: bold=3B">Cc:
</span><span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=
=3B"><a href=3D"mailto:bitcoin-development@lists.sourceforge.net">Bitcoin D=
ev</a></span><br>
<span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=3B font=
-weight: bold=3B">Subject:
</span><span style=3D"font-family: Calibri=2Csans-serif=3B font-size: 11pt=
=3B">Re: [Bitcoin-development] Fwd: Block Size Increase Requirements</span>=
<br>
<br>
</div>
<div>
<div dir=3D"ltr">
<div class=3D"x_gmail_extra">Whilst it would be nice if miners in China can=
 carry on forever regardless of their internet situation=2C nobody has any =
inherent &quot=3Bright&quot=3B to mine if they can't do the job - if miners=
 in China can't get the trivial amounts of bandwidth
 required through their firewall and end up being outcompeted then OK=2C to=
o bad=2C we'll have to carry on without them.</div>
<div class=3D"x_gmail_extra"><br>
</div>
<div class=3D"x_gmail_extra">But I'm not sure why it should be a big deal. =
They can always run a node on a server in Taiwan and connect the hardware t=
o it via a VPN or so.</div>
</div>
</div>
</body>
</html>

--_aef2923c-99c8-45eb-8cc8-1cf19556041d_--

--_e8615478-356b-424a-bc04-874f011bf32b_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------

--_e8615478-356b-424a-bc04-874f011bf32b_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development

--_e8615478-356b-424a-bc04-874f011bf32b_--