public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: grarpamp <grarpamp@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: Move Bitcoin Dev List to a Neutral Competent Entity
Date: Tue, 16 Jun 2015 21:59:47 -0400	[thread overview]
Message-ID: <CAD2Ti2_EO_K+829_jd5vkgTHxq6fJ47u_6st-pbKCZth=046ww@mail.gmail.com> (raw)
In-Reply-To: <CAEz79PphLdxOSVrL0r45mYF+XLFzWwB=-KAT-rb=GLb+tMp6+w@mail.gmail.com>

Please no GoogleGroups. Stick with mailman or some other open
source thing you can move around from place to place as needed.

Also, online third party archives die, their web interfaces suck
ass, they're bloated, don't export, aren't offline capable or
authoritative, etc.

You need to make the raw archives (past and future) downloadable
in mbox format and updated daily, with full unobfuscated headers
for threading and replying, with signatures and attachments.
Commonly for newcomers wishing to seed their own MUA's and archives,
mirrors, search, and so on.

One such breakage of archives by mailman defaults was discussed and
corrected here:
https://cpunks.org/pipermail/cypherpunks/

You also need to get rid of the tag in the subject, it wastes
valuable space and mail filters work just the same without it.

Please no "forums" (see suck above). Unless they have bidirectional
realtime message copying between list and forum. Or at least make
available exports of their message database.

Further, when will the crypto P2P communities develop and use
distributed messaging systems... bitmessage, blockchain, etc as
rough examples... to avoid old centralized issues. At some point you
have to start eating your own dog food and make people run the
clients and come to you instead. Disruptive tech is the new good.



  reply	other threads:[~2015-06-17  1:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 10:12 Warren Togami Jr.
2015-06-14 15:15 ` Jeff Garzik
2015-06-14 16:56   ` Peter Todd
2015-06-15  3:19   ` Warren Togami Jr.
2015-06-15  5:50     ` Andy Schroder
2015-06-15  9:13     ` odinn
2015-06-17  0:19     ` Warren Togami Jr.
2015-06-17  1:59       ` grarpamp [this message]
2015-06-14 20:55 ` Andy Schroder
2015-06-14 21:59   ` Adam Back
2015-06-14 22:14     ` Davide Cavion
2015-06-14 21:54 ` odinn
2015-06-14 22:38 ` Gregory Maxwell
2015-06-15 10:13 ` Mike Hearn
2015-06-15 19:45   ` Adam Weiss
2015-06-15 20:50     ` Pieter Wuille

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='CAD2Ti2_EO_K+829_jd5vkgTHxq6fJ47u_6st-pbKCZth=046ww@mail.gmail.com' \
    --to=grarpamp@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    /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