summaryrefslogtreecommitdiff
path: root/36/89c7c836acef93300567802bcc58ed5a30397f
blob: 1eff369e004c868ec4f6a8bf077e525f7f1c0874 (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
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
Return-Path: <grarpamp@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 54879B19
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 27 Jun 2015 22:21:43 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com
	[209.85.213.182])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 014281CC
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 27 Jun 2015 22:21:34 +0000 (UTC)
Received: by igcur8 with SMTP id ur8so12210390igc.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 27 Jun 2015 15:21:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=72ua7Aj2/6Q5t00CYM1dr6+isgITRl0a/9zDt9i7PSI=;
	b=SMOgCjtZuWcby0Gz/gRahBsFUq5V4sC+UwWQ5+cx+s3K5g+2ZYhaSPvRf2e/KisHXO
	5fvWMbJvSBKsP+UIMDP6FwxVzBf8d9++SsaSoUZLu3eB3RleVRI1W8twyQzNaTUqV9LK
	fh5L1PHNj/uQLBicGXIC2aocPF/bAZeleNDKu7PJB6sjSGayLqSN1qQIfccqKUEmo9sj
	Ho/XVcE9BfbX7kNmEiM1fXJy3zP5YyRbSe/hRxW1aEKJUqCJLiYLo3RI+mgV9vg4Kjb1
	QoGnbuXP0gaMS8CpvAg39Nsve/NjkCieFt8g2fnwA6WVOkovQtLhs47je2sR+K5KI8KP
	OjnQ==
MIME-Version: 1.0
X-Received: by 10.50.64.147 with SMTP id o19mr5892052igs.15.1435443694389;
	Sat, 27 Jun 2015 15:21:34 -0700 (PDT)
Received: by 10.36.107.140 with HTTP; Sat, 27 Jun 2015 15:21:34 -0700 (PDT)
Date: Sat, 27 Jun 2015 18:21:34 -0400
Message-ID: <CAD2Ti2-QChRZYZDSH1avit3snCLMws2UNmHQ_aY5O4txCS3AGg@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,URIBL_BLACK
	autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: [bitcoin-dev] Mailing List Administrivia - GPG, Archives, Breakage,
	TODO, mirrors, etc
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jun 2015 22:21:43 -0000

On Sun, Jun 21, 2015 at 9:14 PM, Frank Flores <frankf44@gmail.com> wrote:
> If you're going to go through the trouble of signing your public emails ...

... then you should also demand that the official archives of your
favorite lists preserve them and their verifiability in the supposedly
canonical reference "mbox" format that they distribute.

On Wed, Jun 24, 2015 at 7:47 AM, Wladimir J. van der Laan
<laanwj@gmail.com> wrote:
> Subject: [bitcoin-dev] New GPG signing key for Bitcoin Core binary releases

http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-June/009045.html
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-June.txt.gz

As you can clearly see, both the HTML archives and the "mbox"
archives have corrupted this message, it will not verify. Do not
try to say this case is trivial, the problem itself is not trivial,
it's gratuitous, and it applies to all matching messages... text,
code, binary inline... that's dangerous.

Do not try to say this corruption prevents spam, it does not.
Spammers simply subscribe to the list and harvest everything
efficiently in realtime... no webcrawling overhead, no stale
addresses. Obfuscation is futile.

This misfeature needs to be disabled.



On Fri, Jun 19, 2015 at 12:57 AM, Warren Togami Jr. <wtogami@gmail.com> wrote:
> archives will be exported
> and imported into the new list server

On Tue, Jun 23, 2015 at 2:45 PM, Andy Schroder <info@andyschroder.com> wrote:
> I'm not sure if anyone has submitted a request for gmane

On Sun, Jun 21, 2015 at 5:35 PM, s7r <s7r@sky-ip.org> wrote:
> Do we have all the archives imported? I run several full nodes and
> mirrors for open source projects, if you think it's useful, I can
> provide a mirror for the mail list archives.

Yes... these other mirrors, archives, analysis, journalism, and
interfaces are useful. However, as it is now, there are no useful
authoritative sources for them to seed from... they're all corrupt.
And any subscribed realtime sources, though nice, are subject to
downtime, administrative and other unrecoverable gaps. Your mirror
project is a fine idea, you should demand that the pristine historical
sources be made publicly available. Not just for you, but for everyone.



On Wed, Jun 17, 2015, grarpamp wrote:
> ...

As before, the current "mbox" archives are broken and not useful...

a) They corrupt message data, messages are unverifiable, another example...
   http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-June/009132.html
   http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-June.txt.gz
b) They are missing the minimum set of original headers necessary
   for fully replyable, threadable, sortable, searchable, context
   preserving and direct use by users MUA's in their local environment:
   (Date, From, To, Cc, Subject, Message-ID, In-Reply-To, References)
c) They do not include attachments (patches, signatures, images, crypto,
   data) that are absolutely necessary to the context and archives
   of all lists. Instead they stupidly throw them away to "web links"
   which results not only in uselessness of the so called "mbox"
   version, but in many thousands of needless fetches by archive
   users and indexers. And hours of wasted work attempting to
   postprocess them into usable form.
   Valuable content lost from the "mbox" files this June alone:
    418 attachment.html
    106 attachment.sig
      6 attachment.jpe
      4 attachment.png
      2 attachment.bin
d) There appear to be at least 15 instances of unescaped '^From '
   in the "mbox". Regeneration with current mailman may fix. One such
   case is here:
   http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2014-January/004245.html
   http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2014-January.txt.gz



Please fix all the above mentioned issues by providing the full raw
archives in regularly updated [gzip/7z] mbox format. The internet
thanks you :)

Example, compare the "Downloadable version"s here:
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/
https://cpunks.org/pipermail/cypherpunks/
https://cpunks.org/pipermail/cypherpunks/2015-February/006820.html



On Tue, Jun 23, 2015 at 2:45 PM, Andy Schroder <info@andyschroder.com> wrote:
> Regarding message footers and the subject prefix

Yes, they're also corruptive and space wasting clutter, for and by
the clueless :( Both of them should be turned off.