public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Ahmed Zsales <ahmedzsales18@gmail.com>
To: Elliot Olds <elliot.olds@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A summary list of all concerns related to not rising the block size
Date: Thu, 20 Aug 2015 22:29:30 +0100	[thread overview]
Message-ID: <CADr=VrSZc6WsLKaz-_pbiwx9Fo5PmxJwCbxe59mNuq+0EnoYxA@mail.gmail.com> (raw)
In-Reply-To: <CA+BnGuH8V7B+R4PONemjdjhmEpQB_yaNouGFMyAgauBFre8F7g@mail.gmail.com>

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

Add:

For - If everyone agrees an increase is required at some point, The longer
you leave it the greater the numbers who have to upgrade

Against - Insufficient testing before moving to production ready releases
sets a bad precedent

On Thu, Aug 20, 2015 at 10:11 PM, Elliot Olds via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> On Fri, Aug 14, 2015 at 4:57 PM, Jorge Timón <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> To be clear, these two are just my personal lists of arguments on
>> "each side" to clear my mind and try to be perfectly objective.
>> [...]
>> Here's the updated both-thread lists:
>>
>>
>> http://0bin.net/paste/igHZMgeoIbYjCJd9#ovaOUlSAKvQYT2p3VXuIuUmNk2XyLH-GnjR5NZMZgFb
>
>
> I thought this was a good idea, so I turned my personal notes into a site
> attempting to list all the strongest arguments and counterarguments on the
> block size debate. I made mine a bit more detailed.
>
> Here's the site: https://sites.google.com/site/bitcoinblocksizedebate/
>
> Feedback welcome.
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

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

  reply	other threads:[~2015-08-20 21:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12  9:59 [bitcoin-dev] A summary list of all concerns related to not rising the block size Jorge Timón
2015-08-12 11:21 ` Venzen Khaosan
2015-08-14 22:35   ` Jorge Timón
2015-08-14 23:12     ` Jorge Timón
2015-08-14 23:57       ` Jorge Timón
2015-08-20 21:11         ` Elliot Olds
2015-08-20 21:29           ` Ahmed Zsales [this message]
2015-08-12 19:52 ` Elliot Olds
2015-08-14 22:55   ` Jorge Timón
2015-08-15 20:36     ` Elliot Olds
2015-08-13  9:52 ` Ashley Holman
2015-08-13 16:36   ` Jean-Paul Kogelman
2015-08-14 22:57   ` Jorge Timón
2015-08-13 22:01 ` Geir Harald Hansen
2015-08-14  2:26   ` Venzen Khaosan
2015-08-14 11:35     ` Marcel Jamin
2015-08-14 13:48     ` Thomas Zander
2015-08-14 22:59   ` Jorge Timón

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='CADr=VrSZc6WsLKaz-_pbiwx9Fo5PmxJwCbxe59mNuq+0EnoYxA@mail.gmail.com' \
    --to=ahmedzsales18@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=elliot.olds@gmail.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