From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z2lEE-0000qm-FX for bitcoin-development@lists.sourceforge.net; Wed, 10 Jun 2015 18:59:58 +0000 X-ACL-Warn: Received: from uschroder.com ([74.142.93.202]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Z2lEC-0001eb-MD for bitcoin-development@lists.sourceforge.net; Wed, 10 Jun 2015 18:59:58 +0000 Received: from [192.168.253.4] (cpe-74-132-161-228.kya.res.rr.com [74.132.161.228]) by uschroder.com (Postfix) with ESMTPSA id A291222DF1C7C; Wed, 10 Jun 2015 14:59:51 -0400 (EDT) Message-ID: <55788924.6090008@AndySchroder.com> Date: Wed, 10 Jun 2015 14:59:48 -0400 From: Andy Schroder User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: s7r@sky-ip.org, "Wladimir J. van der Laan" , xor References: <1943127.DBnVxmfOIh@1337h4x0r> <20150610093556.GA11409@amethyst.visucore.com> <557869F9.8030109@AndySchroder.com> <557883A7.7030906@sky-ip.org> In-Reply-To: <557883A7.7030906@sky-ip.org> X-Enigmail-Version: 1.6 OpenPGP: id=2D44186B; url=http://andyschroder.com/static/AndySchroder.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6A5wgJXk94plCuANwogg5TA1kKuEVVSD7" X-Spam-Score: 0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message -0.5 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1Z2lEC-0001eb-MD Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 18:59:58 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --6A5wgJXk94plCuANwogg5TA1kKuEVVSD7 Content-Type: multipart/alternative; boundary="------------040408070902080305050706" This is a multi-part message in MIME format. --------------040408070902080305050706 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Hello, A couple of motivations for a mailing list switch: 1. Sometimes the mailing list delays delivery for 10 minutes to several days. 2. There are usually lots of ads at the footer of the messages. Really confuses new readers (for me at least), and seems like it really pollutes such a historical dialog that may be referenced long into the future. How would it be if the 10 Commandments, Magna Carta, Bill of Rights, The Sermon on the Mount, or The Gettysburg Address had ads intertwined within them? 3. Don't think HTML messages are allowed. 4. Seems like digital signatures are always broken on messages because the list server slightly modifies them (?), so my e-mail client doesn't verify them all. Andy Schroder On 06/10/2015 02:36 PM, s7r wrote: > The mail list is public, so it's not like the data on it is somehow > sensitive. Sourcefoge is fine, it has a nice web UI where you can brows= e > the message and sort/order them as you want, etc. > > Why would you want to move to a paid solution? And why would you want > users to have to pay per message? This is the worst idea ever from my > point of view. We want to encourage people to join the community, run > full nodes, ask questions, come with solutions, ideas for improvements > and so on. Everyone should read and write and contribute as much as > possible with ideas in debates. You never know who can have bright idea= s > in some contexts. > > Bottom line is so far sourceforge handles the mail lists just fine. I > don't see a single advantage another mail list provider / system could > offer, except some headache and extra work for migration. The software > distribution via sourcefoge was cancelled for obvious reasons which I > fully understand and agree to, but it has nothing to do with the mail > lists. We have way more important things to brainstorm about. > > On 6/10/2015 7:46 PM, Andy Schroder wrote: >> Regarding changing the e-mail list provider. Is anyone interested in >> sponsoring it? There are non-free options, but it may be difficult to >> always ensure the fee is being paid to the provider. I think finding a= n >> agreeable free solution may have been the issue before? I've also >> thought of trying to make a pay per message or byte solution (and this= >> cost could be dynamic based upon the number of current mailing list >> subscribers). This could solve the who pays problem (the sender pays),= >> as well as motivate people to be more concise and clear with their >> messages, and at the same time limit spam. >> >> >> >> Any thoughts? >> >> Andy Schroder >> >> On 06/10/2015 05:35 AM, Wladimir J. van der Laan wrote: >>> On Wed, Jun 10, 2015 at 10:25:12AM +0200, xor wrote: >>>> http://www.howtogeek.com/218764/warning-don%E2%80%99t-download-softw= are-from-sourceforge-if-you-can-help-it/ >>> All our downloads (even old ones) have recently been deleted from sou= rceforge, for this reason. They haven't been mentioned in Bitcon Core rel= ease announcements for a long time. >>> >>> No opinion on the mailing list. Though I think it's less urgent. The = issue of moving the mailinglist has come up before a few times and people= can't agree where to move to. >>> >>> Wladimir >>> >>> >>> ---------------------------------------------------------------------= --------- >> >> ----------------------------------------------------------------------= -------- >> _______________________________________________ >> Bitcoin-development mailing list >> Bitcoin-development@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bitcoin-development >> > > --------------040408070902080305050706 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello,

A couple of motivations for a mailing list switch:
  1. Sometimes the mailing list delays delivery for 10 minutes to several days.
  2. There are usually lots of ads at the footer of the messages. Really confuses new readers (for me at least), and seems like it really pollutes such a historical dialog that may be referenced long into the future. How would it be if the 10 Commandments, Magna Carta, Bill of Rights, The Sermon on the Mount, or The Gettysburg Address had ads intertwined within them?
  3. Don't think HTML messages are allowed.
  4. Seems like digital signatures are always broken on messages because the list server slightly modifies them (?), so my e-mail client doesn't verify them all.


Andy Schroder
On 06/10/2015 02:36 PM, s7r wrote:
The mail list is public, so it's not like the data o=
n it is somehow
sensitive. Sourcefoge is fine, it has a nice web UI where you can browse
the message and sort/order them as you want, etc.

Why would you want to move to a paid solution? And why would you want
users to have to pay per message? This is the worst idea ever from my
point of view. We want to encourage people to join the community, run
full nodes, ask questions, come with solutions, ideas for improvements
and so on. Everyone should read and write and contribute as much as
possible with ideas in debates. You never know who can have bright ideas
in some contexts.

Bottom line is so far sourceforge handles the mail lists just fine. I
don't see a single advantage another mail list provider / system could
offer, except some headache and extra work for migration. The software
distribution via sourcefoge was cancelled for obvious reasons which I
fully understand and agree to, but it has nothing to do with the mail
lists. We have way more important things to brainstorm about.

On 6/10/2015 7:46 PM, Andy Schroder wrote:
Regarding changing the e-mail list provider. Is an=
yone interested in=20
sponsoring it? There are non-free options, but it may be difficult to=20
always ensure the fee is being paid to the provider. I think finding an=20
agreeable free solution may have been the issue before? I've also=20
thought of trying to make a pay per message or byte solution (and this=20
cost could be dynamic based upon the number of current mailing list=20
subscribers). This could solve the who pays problem (the sender pays),=20
as well as motivate people to be more concise and clear with their=20
messages, and at the same time limit spam.



Any thoughts?

Andy Schroder

On 06/10/2015 05:35 AM, Wladimir J. van der Laan wrote:
On Wed, Jun 10, 2015 at 10:25:12AM +0200, xor wr=
ote:
http://www.howtogeek.com/218764/warning=
-don%E2%80%99t-download-software-from-sourceforge-if-you-can-help-it/=

All our downloads (even old ones) have recently =
been deleted from sourceforge, for this reason. They haven't been mention=
ed in Bitcon Core release announcements for a long time.

No opinion on the mailing list. Though I think it's less urgent. The issu=
e of moving the mailinglist has come up before a few times and people can=
't agree where to move to.

Wladimir


-------------------------------------------------------------------------=
-----

-------------------------------------------------------------------------=
-----
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/l=
istinfo/bitcoin-development




--------------040408070902080305050706-- --6A5wgJXk94plCuANwogg5TA1kKuEVVSD7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJVeIkkAAoJEDT679stRBhrPfUH/i9ODu7K4+nLGCI5CH92DkKz FA1jfnQUOUs5RzIqeoq/bcbngYXSAawa5jfo8bhQSYVo9TCJYXXyM5QXCwpJgX7p FrpV00ysTbFWlkXHwfNRViCOK6NGux42EuXkKJDsSBoPJs9WyEQj15NIh4QSK+NL 8qcjIP8LwVNIgnk7gFAB4Mw+WqFxOzEPo5LqZbOP/WxIKj016kPD7icHV9xst05A znyui/lzFSLieuJNH91EUNMaIVUYI0KBdRO1379YMd28UK6YVfhZO5ERVIaPciPs nHH13jANXMZcpBG5MbpC45+BkONDmFfSrqNPR9SwJPelCsCGpwhIHCkoef5NOIk= =r4IP -----END PGP SIGNATURE----- --6A5wgJXk94plCuANwogg5TA1kKuEVVSD7--