public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@exmulti.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] On-going data spam
Date: Tue, 9 Apr 2013 16:53:47 +0200	[thread overview]
Message-ID: <CANEZrP2B4CGwGp1BsPScyC_+DndLDMnHTzWhmhfUxQnE3bVuSA@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpdBDDxD46f9ugn-ueZGwMU6fnF4BheUGiiz1otOTdffEw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 546 bytes --]

> However, there should be some metrics and heuristics that take care of
> this problem.  Notably the dev consensus (sans you, Mike :)) seems to
> be that uneconomical outputs should be made non-standard.


I think that patch is ok as it doesn't really have any fixed concept of
what is uneconomical. But I haven't thought about it much. As Gavin says,
there's an obvious backwards compatibility problem there. It should
probably wait until the payment protocol work is done, so the major user of
micropayments-as-messages  can migrate off them.

[-- Attachment #2: Type: text/html, Size: 800 bytes --]

  reply	other threads:[~2013-04-09 14:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09  1:22 [Bitcoin-development] On-going data spam Jeff Garzik
2013-04-09  9:28 ` Peter Todd
2013-04-09 10:42 ` Mike Hearn
2013-04-09 11:09   ` Peter Todd
2013-04-09 11:17     ` Jay F
2013-04-09 11:34       ` Robert Backhaus
2013-04-09 14:14     ` Mike Hearn
2013-04-09 14:39   ` Caleb James DeLisle
2013-04-09 18:56     ` steve
2013-04-09 19:25     ` Gregory Maxwell
2013-04-09 19:43       ` Mike Hearn
2013-04-09 14:50   ` Jeff Garzik
2013-04-09 14:53     ` Mike Hearn [this message]
2013-04-09 15:01       ` Jeff Garzik
2013-04-09 17:58       ` Peter Todd

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=CANEZrP2B4CGwGp1BsPScyC_+DndLDMnHTzWhmhfUxQnE3bVuSA@mail.gmail.com \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jgarzik@exmulti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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