summaryrefslogtreecommitdiff
path: root/14/c82a465fa3cefe4eeec274441ae038ff3afed1
blob: 82fd07726ea282c81cbe73fa7a6828db611138e0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <grarpamp@gmail.com>) id 1Z5Y7z-0000qR-NM
	for bitcoin-development@lists.sourceforge.net;
	Thu, 18 Jun 2015 11:37:03 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.179 as permitted sender)
	client-ip=209.85.213.179; envelope-from=grarpamp@gmail.com;
	helo=mail-ig0-f179.google.com; 
Received: from mail-ig0-f179.google.com ([209.85.213.179])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Z5Y7y-0001KN-PD
	for bitcoin-development@lists.sourceforge.net;
	Thu, 18 Jun 2015 11:37:03 +0000
Received: by igbqq3 with SMTP id qq3so12813033igb.0
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 18 Jun 2015 04:36:57 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.4.204 with SMTP id 195mr14662490ioe.40.1434627417399;
	Thu, 18 Jun 2015 04:36:57 -0700 (PDT)
Received: by 10.36.51.76 with HTTP; Thu, 18 Jun 2015 04:36:57 -0700 (PDT)
Date: Thu, 18 Jun 2015 07:36:57 -0400
Message-ID: <CAD2Ti29KNZO8tJwDbBZrXmYAv6nArd1OxKnNiHaWC_UG4e3Rdg@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(grarpamp[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1Z5Y7y-0001KN-PD
Subject: [Bitcoin-development] Video summarizations of blocksize issues?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 18 Jun 2015 11:37:03 -0000

On Thu, Jun 18, 2015 at 4:54 AM, odinn <odinn.cyberguerrilla@riseup.net> wrote:
> Recently I saw the following video:
> https://www.youtube.com/watch?v=8JmvkyQyD8w&t=47m58s

For those loosely following the technical issues from outside development
circles, but who may be pressed into a voting/adoption type position (miners,
users, investors)... is there a parallel presentation of the concepts and
arguments from the other side (both, or the various, sides) that they
can refer to?
Someplace where they are collated and presented? A wiki perhaps?
Are these even valid or necessary questions?