Re: [bitcoin-dev] Mailing List Administrivia - GPG, Archives, Breakage, TODO, mirrors, etc

From: "Warren Togami Jr." <wtogami@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Mailing List Administrivia - GPG, Archives, Breakage, TODO, mirrors, etc
Date: Sun, 28 Jun 2015 19:27:06 -0700	[thread overview]
Message-ID: <CAEz79Pp7XyAjdN_e7BnwJfqp=ZaSk7hQSwMJiev-9R5orKyUew@mail.gmail.com> (raw)
In-Reply-To: <CADm_WcbjAmrBXJs6s9rvVKccgOA3sDut0o2ALTKqWQrjT=MyxQ@mail.gmail.com>

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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

June 28th, 2015
Mailman's obscure_addresses option is now disabled.  It has been pretty
useless
as a spam mitigation measure anyway.

This is a test message to see if mailman continues to break --clearsign GPG
signatures for messages that contain an e-mail address like test@example•com
.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQQcBAEBCAAGBQJVkKy7AAoJELEXnrc0fcENmiIf/1Qgb/XFDmGl5RsZnMWh+kCX
EBjT/ouufgURTrOt6XPhwnxJAYMKPtobg4MvjosqKFNKzyz3Io9TxkWXFXFLajLt
uZ/RPck0b6qYPXW02m6on1Zj8VIKrREtm4CEH/2q7iHkjsWIHULo+K6emrJQtIOs
DzhUEniPPVDJVIq2pZJGKHq87ydmnFMYhXjzCu2e0N7CBFw/uxtUEsvkd0uuognm
YVjnrCjS8CLzNgEkx8z6R1WWz7psDQeLr+d8BP/6TVrgEOaeX4pAy9mhqdPjGutV
C6X3SyMlSA/PDJFqzT5Upe4UKwKWGq7AOBz7OpzpYIqJ69NKsIjCgh+t6qCisDZO
O3XFUIidmKZsWE422InFLhUtqzwZHq56J/eKKiYz53BSYtTOPIs4+RPlm1Gzs7gP
cEqoDYobdlT2H1vCvNficcbH5nWmooErUxT06tXjGqfPHlm+OVuOyVTwuin+gD5H
winqtNlkSCbG1MjhUoLEJVxLHP7t6i5e6EKPQrvP0XycKuO2PMlVkYYFBGMKEFF/
sL68wyV/0PzGRA7ggcBmcOGHC7ys2sOroLZCWNDnOrQnRFHvQgDCQpj3uMFMO7yf
8E+0CIKO0vB/Ljxse51+s/NZTX8uTZu525+hSG8cuLY1FTl5Zk3oRH1HGUJ9wbWh
Hjx6827uh543+AHWgBwEpQ/8LkSlc0UN6txNmYn4DJgEksqP80iaPkvXAEesSUJ8
OtAPrWOMZXcSsp7HZkDXuJyMUerGvZcdIVvVNsLOWLWa2c0kyDdxubGflhGN/Hkq
67pJ5J/aeraw7BdfRi78CUWYXpVBlMaQ60jT2LV9XQxsqSnZb3+VgN9vyvQi/gih
enr+l8r4esM7TOsGYHMWbQkHgnm/wOMiMc56xlqeIi/+cRuJF3Mg5LnbqIUU1Ox0
S+luGASWg1R2yU4n0EWQ5sx1dmslgvJe6lDKlQXEX4e4d5F0vhnyFiDVhChMCpGv
ALK8MiUZGD2y9fIPB+Yypq7mH9NiQwQIJtpbVgVd2pBEl0XWkbs6F5GNq90ChE7x
hWiyu2N/iug2r7zKt5KtZob9hIljQ6N/HAk+O1lLPUktX5HBt8X+KHyX22GMLIAu
g4tWk2P7R0Sh2rYSd43S3CMF01eaGI2oWU0rj2KtG1HqQMVOIVjdxYR3tpmC69Tb
MyCq7xe+zOcAiWkAeb1cJjgahrnDBR663zSsqZVnAyG9GQVvPY6fZKxYoY2B+xgP
tEi8FTL3ag0PbdUJF8SQugx+R3HNBS+r1AGgOUEBtrrH9IqBAaOf3N+rMFLUl/HW
ypTs5fj6A49CkncmQQGcyj3BwlEjhr4wF59Bpxn/KTwT5H2Sdu1QEuB2G+gwqYs=
=bOwk
-----END PGP SIGNATURE-----

On Sat, Jun 27, 2015 at 4:54 PM, Jeff Garzik <jgarzik@gmail•com> wrote:

> Generally agreed w/ all this.
>
> To preserve digital signatures now and in the future, and make mbox
> archives actually useful, a minimum modification policy is needed.
>
>
>
> On Sat, Jun 27, 2015 at 3:21 PM, grarpamp <grarpamp@gmail•com> wrote:
>
>> 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.
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists•linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

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