From: gabe appleton <gappleto97@gmail•com>
To: Pindar Wong <pindar.wong@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Meta suggestions for this block size debate
Date: Sat, 6 Jun 2015 02:41:40 -0400 [thread overview]
Message-ID: <CANJO25KvK9imRngtHTZdFMFHY8Ua-+D6gj+nfgXebBVBKVud4A@mail.gmail.com> (raw)
In-Reply-To: <CAM7BtUr7XXT4vctroxcb7kqGu7faWx-KY-fK=KKac1d0bkcXYw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4391 bytes --]
Nothing to apologize for. And yes, that's the correct one.
On Jun 6, 2015 2:39 AM, "Pindar Wong" <pindar.wong@gmail•com> wrote:
> OK... sorry for my confusion.
>
> https://github.com/EthanHeilman/BlockSizeDebate
>
> it is.
>
> p.
>
>
> On Sat, Jun 6, 2015 at 2:37 PM, gabe appleton <gappleto97@gmail•com>
> wrote:
>
>> Please use the one it's originally forked from that Ethan made. I don't
>> want to be the one who sorts through what's valid and what isn't, as I
>> don't have as low-level an understanding as I'd like. I don't feel
>> qualified.
>> On Jun 6, 2015 2:34 AM, "Pindar Wong" <pindar.wong@gmail•com> wrote:
>>
>>> Thanks Gabe.
>>>
>>> https://github.com/gappleto97/BlockSizeDebate
>>>
>>> github's reachable via vpn.
>>>
>>> p.
>>>
>>>
>>> On Sat, Jun 6, 2015 at 2:28 PM, gabe appleton <gappleto97@gmail•com>
>>> wrote:
>>>
>>>> Yeah. We made a git repo instead, so we don't have to bother with the
>>>> exclusive-by-default wiki policies. It's linked in this email chain.
>>>>
>>>> I'll be getting home tomorrow, so I should be able to start back up on
>>>> this. A few days from now we should throw this on /r/Bitcoin so we can get
>>>> some more public comment on it. They already gave me a few leads to chase.
>>>> On Jun 5, 2015 11:34 PM, "Pindar Wong" <pindar.wong@gmail•com> wrote:
>>>>
>>>>> Gabe,
>>>>>
>>>>> Did you ever get an answer to this?
>>>>>
>>>>> I"ll have some time tomorrow to be able to help with some work on this
>>>>> and will need to do it myself anyways since I'm not sure I understand the
>>>>> nuances, where bitcoin XT fits into the scheme of things (or not) etc.
>>>>>
>>>>> I would have thought that there would be a testnet4 by now using 8mb
>>>>> blocks... but hey that's just me.
>>>>>
>>>>> p.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Jun 2, 2015 at 11:52 AM, gabe appleton <gappleto97@gmail•com>
>>>>> wrote:
>>>>>
>>>>>> I don't have permission to create a page. If someone else does, I'll
>>>>>> happily get a framework started.
>>>>>>
>>>>>> On Mon, Jun 1, 2015 at 11:32 PM, Ethan Heilman <eth3rs@gmail•com>
>>>>>> wrote:
>>>>>>
>>>>>>> I second this, I don't have time to read the large number of emails
>>>>>>> generated every day from the block size debate. A summary of the various
>>>>>>> positions and arguments would be extremely helpful.
>>>>>>>
>>>>>>> On Mon, Jun 1, 2015 at 11:02 PM, gabe appleton <gappleto97@gmail•com
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Also, can we try to get a wiki page for the debate? That way we
>>>>>>>> could condense the information as much as possible. I'll be willing to
>>>>>>>> assist if the page gets approval.
>>>>>>>> On Jun 1, 2015 6:41 PM, "Mats Henricson" <mats@henricson•se> wrote:
>>>>>>>>
>>>>>>>>> Hi!
>>>>>>>>>
>>>>>>>>> My fingers have been itching many times now, this debate
>>>>>>>>> drives me nuts.
>>>>>>>>>
>>>>>>>>> I just wish all posters could follow two simple principles:
>>>>>>>>>
>>>>>>>>> 1. Read up. Yes. All of what has been written. Yes, it will
>>>>>>>>> take many hours. But if you're rehashing what other
>>>>>>>>> smarter people have said over and over before, you're
>>>>>>>>> wasting hundreds of peoples time. Please don't.
>>>>>>>>>
>>>>>>>>> 2. Be helpful. Suggest alternatives. Just cristizising is
>>>>>>>>> just destructive. If you want no change, then say so.
>>>>>>>>>
>>>>>>>>> Mats
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>> _______________________________________________
>>>>>>>>> Bitcoin-development mailing list
>>>>>>>>> Bitcoin-development@lists•sourceforge.net
>>>>>>>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------------
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Bitcoin-development mailing list
>>>>>>>> Bitcoin-development@lists•sourceforge.net
>>>>>>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>>
>>>>>> _______________________________________________
>>>>>> Bitcoin-development mailing list
>>>>>> Bitcoin-development@lists•sourceforge.net
>>>>>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>>>>>
>>>>>>
>>>>>
>>>
>
[-- Attachment #2: Type: text/html, Size: 7405 bytes --]
next prev parent reply other threads:[~2015-06-06 6:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 22:22 Mats Henricson
2015-06-02 3:02 ` gabe appleton
2015-06-02 3:32 ` Ethan Heilman
2015-06-02 3:52 ` gabe appleton
2015-06-06 3:34 ` Pindar Wong
2015-06-06 6:28 ` gabe appleton
2015-06-06 6:34 ` Pindar Wong
2015-06-06 6:37 ` gabe appleton
2015-06-06 6:39 ` Pindar Wong
2015-06-06 6:41 ` gabe appleton [this message]
2015-06-08 0:55 ` gabe appleton
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=CANJO25KvK9imRngtHTZdFMFHY8Ua-+D6gj+nfgXebBVBKVud4A@mail.gmail.com \
--to=gappleto97@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=pindar.wong@gmail$(echo .)com \
/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