Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1SfoP3-0007z8-Cr
	for bitcoin-development@lists.sourceforge.net;
	Sat, 16 Jun 2012 08:30:41 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.181 as permitted sender)
	client-ip=209.85.212.181; envelope-from=mh.in.england@gmail.com;
	helo=mail-wi0-f181.google.com; 
Received: from mail-wi0-f181.google.com ([209.85.212.181])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1SfoOz-0007XH-1p
	for bitcoin-development@lists.sourceforge.net;
	Sat, 16 Jun 2012 08:30:41 +0000
Received: by wibhn14 with SMTP id hn14so194808wib.10
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 16 Jun 2012 01:30:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.143.213 with SMTP id l63mr4857332wej.117.1339835430797;
	Sat, 16 Jun 2012 01:30:30 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.216.254.232 with HTTP; Sat, 16 Jun 2012 01:30:30 -0700 (PDT)
In-Reply-To: <1339821211.57245.YahooMailNeo@web121006.mail.ne1.yahoo.com>
References: <CA+8xBpde=y213zFeVjYoZgBstZ6GTnk84ADD8twaDJy2D6CHyw@mail.gmail.com>
	<007701cd4b68$a88e6a40$f9ab3ec0$@bitcoinstats.org>
	<1339821211.57245.YahooMailNeo@web121006.mail.ne1.yahoo.com>
Date: Sat, 16 Jun 2012 10:30:30 +0200
X-Google-Sender-Auth: NPI4zm3B2pBPEZRjqZh8T6NVDm0
Message-ID: <CANEZrP2n0a37vRiyn3nMY92QaUYkmycVV59OObze3xF39u-mGg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Amir Taaki <zgenjix@yahoo.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.4 (-)
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
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	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
	0.1 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1SfoOz-0007XH-1p
Cc: "bitcoin-development@lists.sourceforge.net"
	<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] SatoshiDice and Near-term scalability
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: Sat, 16 Jun 2012 08:30:41 -0000

Joseph is quite accommodating and doesn't want to hurt the network.
That said "asking him to stop" seems like the worst possible solution
possible. His site is quite reasonable.

I think if I fix bitcoinj to have smarter fee code he might stop
attaching a small fee to every TX, but I'm not sure.

On Sat, Jun 16, 2012 at 6:33 AM, Amir Taaki <zgenjix@yahoo.com> wrote:
> Did anyone try sending them an email asking them to stop or offering help=
 to fix their site? What did they say? I'm sure they would try to be accomo=
dating.
>
>
>
> ----- Original Message -----
> From: Jonathan Warren <jonathan@bitcoinstats.org>
> To: bitcoin-development@lists.sourceforge.net
> Cc:
> Sent: Saturday, June 16, 2012 4:35 AM
> Subject: Re: [Bitcoin-development] SatoshiDice and Near-term scalability
>
> Yes, I measure mainnet confirmation times on a regular basis.
> http://bitcoinstats.org/post/tx-confirmation-times-June2012.png
>
> Before fairly recently, fee-paying transactions never took anywhere close=
 to
> this long to be confirmed.
>
> Jonathan Warren
> (Bitcointalk: Atheros)
>
> -----Original Message-----
> From: Jeff Garzik [mailto:jgarzik@exmulti.com]
> Sent: Friday, June 15, 2012 1:17 PM
> To: bitcoin-development@lists.sourceforge.net
> Subject: [Bitcoin-development] SatoshiDice and Near-term scalability
>
> Hard-fork requires a very high level of community buy-in, because it shut=
s
> out older clients who will simply refuse to consider >1MB blocks valid.
>
> Anything approaching that level of change would need some good, hard data
> indicating that SatoshiDice was shutting out the majority of other traffi=
c.
> Does anyone measure mainnet "normal tx" confirmation times on a regular
> basis?=C2=A0 Any other hard data?
>
>
>
> -------------------------------------------------------------------------=
-----
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
> -------------------------------------------------------------------------=
-----
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development