From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <bitcoin-list@bluematt.me>) id 1Qg2xX-0004QS-Jp for bitcoin-development@lists.sourceforge.net; Sun, 10 Jul 2011 22:58:43 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bluematt.me designates 208.79.240.5 as permitted sender) client-ip=208.79.240.5; envelope-from=bitcoin-list@bluematt.me; helo=smtpauth.rollernet.us; Received: from smtpauth.rollernet.us ([208.79.240.5]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Qg2xW-0008LI-J4 for bitcoin-development@lists.sourceforge.net; Sun, 10 Jul 2011 22:58:43 +0000 Received: from smtpauth.rollernet.us (localhost [127.0.0.1]) by smtpauth.rollernet.us (Postfix) with ESMTP id 0442F59400A for <bitcoin-development@lists.sourceforge.net>; Sun, 10 Jul 2011 15:58:22 -0700 (PDT) Received: from mail.bluematt.me (unknown [IPv6:2001:470:9ff2:2:20c:29ff:fe16:f239]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: @bluematt.me) by smtpauth.rollernet.us (Postfix) with ESMTPSA for <bitcoin-development@lists.sourceforge.net>; Sun, 10 Jul 2011 15:58:21 -0700 (PDT) Received: from [IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b] (unknown [IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b]) by mail.bluematt.me (Postfix) with ESMTPSA id E3B38B3CC for <bitcoin-development@lists.sourceforge.net>; Mon, 11 Jul 2011 00:58:31 +0200 (CEST) From: Matt Corallo <bitcoin-list@bluematt.me> To: bitcoin-development <bitcoin-development@lists.sourceforge.net> In-Reply-To: <201107101846.09997.luke@dashjr.org> References: <BANLkTinus7PWNLJi9rEvTtSB93hjLKhFpg@mail.gmail.com> <201107101630.55518.luke@dashjr.org> <1310335963.2230.29.camel@Desktop666> <201107101846.09997.luke@dashjr.org> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-wWlcFU2NYBiQ6YVrY4E0" Date: Mon, 11 Jul 2011 00:58:30 +0200 Message-ID: <1310338710.2230.30.camel@Desktop666> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 X-Rollernet-Abuse: Processed by Roller Network Mail Services. Contact abuse@rollernet.us to report violations. Abuse policy: http://rollernet.us/abuse.php X-Rollernet-Submit: Submit ID 1f66.4e1a2e8d.61415.0 X-Spam-Score: -1.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 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1Qg2xW-0008LI-J4 Subject: Re: [Bitcoin-development] Useful bitcoin patches... 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: Sun, 10 Jul 2011 22:58:43 -0000 --=-wWlcFU2NYBiQ6YVrY4E0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, 2011-07-10 at 18:46 -0400, Luke-Jr wrote: > On Sunday, July 10, 2011 6:12:43 PM Matt Corallo wrote: > > On Sun, 2011-07-10 at 16:30 -0400, Luke-Jr wrote: > > > Again, take it or leave it, but in the meantime you're asking for tro= uble > > > from users who feel they're being forced to pay more than they have t= o. > > > Or perhaps rather than trouble, that decision will increase awareness= of > > > other clients that don't try to control the users. That could be good > > > too. > >=20 > > Its not a question of forcing users to pay anything, its a question of > > how best to solve the "Im just gonna throw random crap in the chain for > > the lulz" problem without causing too many side effects. As with many > > things Bitcoin, the temporary solution was something that was fairly > > quickly hacked together to solve the problem without causing too many > > problems. What needs to happen is an actual solution, Bitcoin, in > > theory, allows for all kinds of cool things, but the solution here need= s > > carefully thought out and implemented, not just keep lowering the fees. >=20 > The point is that we are already accepting lower fees. People (probably) = want=20 > to pay those lower fees. Yet there's developers writing their software to= get=20 > in the way between the user and pool willing to do business. Read what I wrote again, and don't reply off-list. --=-wWlcFU2NYBiQ6YVrY4E0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAABAgAGBQJOGi6QAAoJEBrh01BD4I5UiXgQAJHn1nW4FLF10D9f+SRdp07M BFQTl0ejjUVve+hNmvgdDL+2hCyCtXPsPnwULgDaH7VP5bBR4oDZ3G/FIZL3Xf5b jRl+VpItUb6JoZAonxoZDoXNtM+Q6L/r7mq9PV0p9rv9S2VphQvLAvclGhBeEE7G HHoNnw7JC3pT1D+bWX8CwsG4mIQa9iQ404044csJLTQl2d5OCShH38aIVr2jRboN Di79Krato7DHxjdSTkOCWiCykyzEOJL7DF/phw27ybua06VdaH3yzSitACXInTXq n0rof7h+VLfi6vmhAGuEL9Vdyg8MDcwBmYFL+GAYKnM3g0TYXLWOWLGpOMAvquYL st3jPInXyuIxZ+az/XxqyUlOQTTpmOkJ2Ly7Ze9VmbRlYdYs1yG4PESqF/xhl3On RWa+CKs4WTeQBBvYP0mROsljYU/bH541NJKOlTZG6OBaDs4qcuB5M+BHLGkyGVGU mKMg6PVAuP6LMIQDQDKC5hxXY3MEWdhZEISVg/tPrxu24ClHNPIminaH/fYzyIFf J0iPKDPfoUtu1hl/nV6BwZfQWmxO+5J8lWsy7Tc4N/vPG8sXj6S983kgxxgqfxLz qyK1RGANctyOQx1Qj3C6TbxX4aKC7B61dpVwoighAZ5gjFjvF1TGE+BylSDRhVB9 Hah57PJlarsCXiB5nVAS =KRzQ -----END PGP SIGNATURE----- --=-wWlcFU2NYBiQ6YVrY4E0--