public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Adam Back <adam@cypherspace.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP process
Date: Wed, 15 Oct 2014 20:13:11 +0200	[thread overview]
Message-ID: <CANEZrP0-Rnoe2GzvTs4nztbTMWKVxxuW=qMMwtcgoQJCvRkosA@mail.gmail.com> (raw)
In-Reply-To: <CALqxMTErVtN2bj7s=DiX4ajzMtQ=M+_DCFQ0=jT6QWUVaXwY_w@mail.gmail.com>

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

I don't care much what exact list software/service is used, but lists.sf.net
hasn't changed in years and is basically dying. Trashing all @yahoo
accounts because ancient mailman does a MITM attack on people's email is no
good, it's not any better than a web proxy that breaks every SSL
connection. For a project that is based on digital signatures, it's really
bad that the mailing list is incompatible with Yahoo's "mail signatures
must be valid" policy.

Plus its moderation features suck, its mail archiving features suck, etc.
It essentially has no redeeming features at all.

mail-archive.com can be easily used with any mailing list, so not sure why
that's brought up. You just add it as a member, as documented here:
http://www.mail-archive.com/faq.html#newlist

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

  parent reply	other threads:[~2014-10-15 18:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15  8:29 [Bitcoin-development] BIP process Wladimir
2014-10-15  9:22 ` Gregory Maxwell
2014-10-15  9:36   ` Wladimir
2014-10-15 18:58     ` Cory Fields
2014-10-16  7:50     ` Thomas Zander
2014-10-15 15:37 ` Gavin Andresen
2014-10-15 15:46   ` Mike Hearn
2014-10-15 15:54     ` Adam Back
2014-10-15 16:47       ` Peter Todd
2014-10-15 18:13       ` Mike Hearn [this message]
2014-10-16  7:38         ` Thomas Zander
2014-10-16 14:19         ` Oliver Egginger
2014-10-15 19:00       ` Btc Drak
2014-10-15 19:40         ` Peter Todd
2014-10-16  4:41           ` Luke Dashjr
2014-10-19  7:17 ` xor
2014-10-19  9:42   ` Btc Drak
2014-10-19  9:49   ` Wladimir
2014-10-19 18:58   ` Thomas Zander
2014-10-20  0:33   ` odinn
  -- strict thread matches above, loose matches on Subject: below --
2011-10-18 19:17 Gavin Andresen
2011-10-18 21:26 ` Nils Schneider
2011-10-20  5:02 ` Alex Waters
2011-10-20 11:27   ` Christian Decker

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='CANEZrP0-Rnoe2GzvTs4nztbTMWKVxxuW=qMMwtcgoQJCvRkosA@mail.gmail.com' \
    --to=mike@plan99.net \
    --cc=adam@cypherspace.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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