From: Matt Corallo <bitcoin-list@bluematt•me>
To: bitcoin-development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Useful bitcoin patches...
Date: Mon, 11 Jul 2011 00:58:30 +0200 [thread overview]
Message-ID: <1310338710.2230.30.camel@Desktop666> (raw)
In-Reply-To: <201107101846.09997.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
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 trouble
> > > from users who feel they're being forced to pay more than they have to.
> > > 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.
> >
> > 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 needs
> > carefully thought out and implemented, not just keep lowering the fees.
>
> The point is that we are already accepting lower fees. People (probably) want
> to pay those lower fees. Yet there's developers writing their software to get
> in the way between the user and pool willing to do business.
Read what I wrote again, and don't reply off-list.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-07-10 22:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 3:23 Jeff Garzik
2011-07-01 16:03 ` Christian Decker
2011-07-01 16:23 ` Gregory Maxwell
2011-07-01 16:25 ` Matt Corallo
2011-07-01 18:59 ` Luke-Jr
2011-07-10 18:42 ` Luke-Jr
2011-07-10 19:12 ` Matt Corallo
2011-07-10 20:30 ` Luke-Jr
[not found] ` <1310335963.2230.29.camel@Desktop666>
[not found] ` <201107101846.09997.luke@dashjr.org>
2011-07-10 22:58 ` Matt Corallo [this message]
2011-08-04 20:29 ` Luke-Jr
2011-08-04 20:42 ` Luke-Jr
2011-08-04 23:43 ` Jeff Garzik
2011-08-05 3:01 ` Luke-Jr
2011-09-03 15:27 ` [Bitcoin-development] Last try: Fixes for 0.4 Luke-Jr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1310338710.2230.30.camel@Desktop666 \
--to=bitcoin-list@bluematt$(echo .)me \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox