From: Andy Schroder <info@AndySchroder•com>
To: Troy Benjegerdes <hozer@hozed•org>
Cc: Eric Stetson <eric@grantcoin•org>,
bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
Date: Wed, 10 Jun 2015 14:41:32 -0400 [thread overview]
Message-ID: <557884DC.1020700@AndySchroder.com> (raw)
In-Reply-To: <20150610180256.GN27932@nl.grid.coop>
[-- Attachment #1: Type: text/plain, Size: 3766 bytes --]
Hello Troy,
I like the idea of the live mirrors. I'm personally just an amateur at
setting up e-mail servers, but the first concern I have is that everyone
hosting a mirror may not necessarily use the same SMTP MTA. I personally
use postfix, but I'm not sure what most people use.
Some other features I'd like to see required is PGP/MIME support and
ensuring that digital signatures are not broken by footers, etc.
appended to the bottom of the message by the list. It might be nice to
also allow for HTML messages?
Here is a link with some current statistics to get an idea what the load
may be. I've been told there are about 1,200 subscribers.
http://dir.gmane.org/gmane.comp.bitcoin.devel
Andy Schroder
On 06/10/2015 02:02 PM, Troy Benjegerdes wrote:
> I'll sponsor it, if we agree to implement a HashCash spam filter
> in the next 6 months. I've run mail servers for $DAYJOB for 5 or
> so years, and I've run my own personal server for the last 14.
>
> Since Bitcoin is a perfectly good HashCash system, I'm thinking a
> http://www.courier-mta.org/courierfilter.html filter plugin that
> checks to ensure that the required bitcoin fee has been paid, or
> better yet included in the message in some standard form.
>
> I'd like to have several other people with linux admin experience
> also agree to host live mirrors of the list, which could be switched
> over by whomever controls the relevant MX records for the mail list.
>
> What do you think a reasonable per-message fee should be, such that
> a couple of independent admins can reasonably expect to be able to
> pay $250/month each for their time and server hosting/bandwidth costs?
>
> I also think that anyone who's contributed more than say 10 or 15
> commits to https://github.com/bitcoin/bitcoin/graphs/contributors
> should be excluded from the pay-with-bitcoin filter, as they have
> paid with code. The rest of us should be paying to distribute and
> archive their efforts.
>
> On Wed, Jun 10, 2015 at 12:46:49PM -0400, 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 an
>> 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-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 mentioned in Bitcon Core release 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]
next prev parent reply other threads:[~2015-06-10 18:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 8:25 xor
2015-06-10 9:35 ` Wladimir J. van der Laan
2015-06-10 16:46 ` Andy Schroder
2015-06-10 18:02 ` Troy Benjegerdes
2015-06-10 18:41 ` Andy Schroder [this message]
[not found] ` <DB12E925-11C6-4A82-BC81-FB3DA26BC5B3@newcastle.ac.uk>
[not found] ` <20150610185810.GQ27932@nl.grid.coop>
[not found] ` <DB5PR07MB091974E06974EA88136F60C2B5BD0@DB5PR07MB0919.eurprd07.prod.outlook.com>
2015-06-11 1:46 ` Troy Benjegerdes
2015-06-10 18:28 ` Ivan Brightly
2015-06-10 18:47 ` Troy Benjegerdes
2015-06-10 19:13 ` Ivan Brightly
2015-06-10 18:36 ` s7r
2015-06-10 18:59 ` Andy Schroder
2015-06-10 19:03 ` Peter Todd
2015-06-10 19:12 ` Andy Schroder
2015-06-10 19:20 ` Peter Todd
2015-06-10 19:36 ` Andy Schroder
2015-06-10 19:43 ` Peter Todd
2015-06-10 20:03 ` Andy Schroder
2015-06-10 19:54 ` Jeff Garzik
2015-06-11 9:27 ` Wladimir J. van der Laan
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=557884DC.1020700@AndySchroder.com \
--to=info@andyschroder$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=eric@grantcoin$(echo .)org \
--cc=hozer@hozed$(echo .)org \
/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