From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 975AF8A5 for ; Wed, 12 Aug 2015 09:23:17 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from pmx.vmail.no (pmx.vmail.no [193.75.16.11]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 6442489 for ; Wed, 12 Aug 2015 09:23:16 +0000 (UTC) Received: from pmx.vmail.no (localhost [127.0.0.1]) by localhost (pmx.isp.as2116.net) with SMTP id 480A1404AC for ; Wed, 12 Aug 2015 11:23:15 +0200 (CEST) Received: from smtp.bluecom.no (smtp.bluecom.no [193.75.75.28]) by pmx.vmail.no (pmx.isp.as2116.net) with ESMTP id 16EDD4049A for ; Wed, 12 Aug 2015 11:23:15 +0200 (CEST) Received: from pluto.localnet (unknown [81.191.183.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.bluecom.no (Postfix) with ESMTPS id 067D8C2 for ; Wed, 12 Aug 2015 11:23:14 +0200 (CEST) From: Thomas Zander To: Bitcoin Dev Date: Wed, 12 Aug 2015 11:23:13 +0200 Message-ID: <1963286.x5NhlJ5RfS@pluto> User-Agent: KMail/4.14.1 (Linux/3.16.0-4-amd64; KDE/4.14.2; x86_64; ; ) In-Reply-To: References: <1679272.aDpruqxXDP@coldstorage> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] Fees and the block-finding process X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Aug 2015 09:23:17 -0000 On Wednesday 12. August 2015 10.51.57 Jorge Tim=F3n wrote: > > Personally I think its a bad idea to do write the way you do, which= is=20 that > > some people have to prove that bad things will happen if we don't m= ake a > > certain change. It polarizes the discussion and puts people into ca= mps. > > Peoplehave to choose sides. >=20 > Whatever, No, please don't just say "whatever". Show some respect, please. If you have the courage to say people are spreading FUD you really shou= ld=20 have already exhausted all possible avenues of cooperation. Now you look like you give up and blame others. > I just give up trying that people worried about a non-increase in the= short > term answer to me that question. I will internally think that they ju= st > want to spread fud, but not vey vocal about it. Again, I've been trying really hard to give you answers, straight answe= rs. It saddens me if you really are giving up trying to understand what peo= ple=20 equally enthusiastic about this technology may see that you don't see. > It's just seems strange to me that you don't want to prove to me that= 's not > the case when it is so easy to do so: just answer the d@#/&m question= . In the evolution of Bitcoin over the next couple of years we need bigge= r=20 blocks for a lot of different reasons. One of them is that LN isn't her= e. The other is that we have known bugs that we have to fix, and that will= take=20 time. Time we are running out of. To buy more time, get bigger blocks now. Anyway, I dislike your approach, as I said in the previous mail. Its not about people spreading FUD or sidestepping the question, it is = about=20 keeping the discussion civilised. You are essentially the one that ask= s; "if you are not beating your wife, please prove it to me". And the you get upset when I try to steer the conversation into less=20= black/white situations... And, yes, that analogy is apt because you can't prove either. --=20 Thomas Zander