From: Troy Benjegerdes <hozer@hozed•org>
To: "Patrick Mccorry (PGR)" <patrick.mccorry@newcastle•ac.uk>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
Date: Wed, 10 Jun 2015 20:46:47 -0500 [thread overview]
Message-ID: <20150611014647.GS27932@nl.grid.coop> (raw)
In-Reply-To: <DB5PR07MB091974E06974EA88136F60C2B5BD0@DB5PR07MB0919.eurprd07.prod.outlook.com>
And just like I did here, if I were a list member with good reputation,
and felt like reposting something that did not make it to the list by
accident or ommission, or a hashcash posting fee that was too high, it
would end up on the list if enough people bothered to read it and
either repost, or post the bond to pass the filter.
On Wed, Jun 10, 2015 at 07:04:41PM +0000, Patrick Mccorry (PGR) wrote:
> Yeah post back to list - its an interesting response. So members with a good reputation could vote to say if the bond should be returned to the new member. I just wanted to highlight that people who do not commit a lot of code contribute in other, arguably equal ways.
>
> ________________________________________
> From: Troy Benjegerdes <hozer@hozed•org>
> Sent: 10 June 2015 19:58
> To: Patrick Mccorry (PGR)
> Subject: Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
>
> Did you want responses sent back to the list?
>
> I think, if I had a revenue stream from a pay-to-post list in place,
> the first thing I'd do is spend some time on a reputation/'post bond'
> interface in which known users with a good reputation could post for
> no charge, while if you were unknown or new to the list, you would
> need to post a bond.
>
> If the consensus of the list was that your message was valuable, it
> would be broadcast and archived no charge.
>
> If enough readers thought the message was spam, those readers could
> collect the posted bond, thus compensating them for the time wasted
> reading said spam.
>
> I would hope that in such an environment would still work for researchers.
> Does this answer your concerns? Should I repost to the list, because
> I do think your concern is worth sharing?
>
> On Wed, Jun 10, 2015 at 06:48:29PM +0000, Patrick Mccorry (PGR) wrote:
> > What about researchers who do not commit code but help find problems in this space. I don't think a mailing should be a paid for service - as it's difficult to determine who should and should not pay.
> >
> > Sent from my iPhone
> >
> > > On 10 Jun 2015, at 19:45, Troy Benjegerdes <hozer@hozed•org> 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
> > >
> > > --
> > > ----------------------------------------------------------------------------
> > > Troy Benjegerdes 'da hozer' hozer@hozed•org
> > > 7 elements earth::water::air::fire::mind::spirit::soul grid.coop
> > >
> > > Never pick a fight with someone who buys ink by the barrel,
> > > nor try buy a hacker who makes money by the megahash
> > >
> > >
> > > ------------------------------------------------------------------------------
> > > _______________________________________________
> > > Bitcoin-development mailing list
> > > Bitcoin-development@lists•sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
> --
> ----------------------------------------------------------------------------
> Troy Benjegerdes 'da hozer' hozer@hozed•org
> 7 elements earth::water::air::fire::mind::spirit::soul grid.coop
>
> Never pick a fight with someone who buys ink by the barrel,
> nor try buy a hacker who makes money by the megahash
--
----------------------------------------------------------------------------
Troy Benjegerdes 'da hozer' hozer@hozed•org
7 elements earth::water::air::fire::mind::spirit::soul grid.coop
Never pick a fight with someone who buys ink by the barrel,
nor try buy a hacker who makes money by the megahash
next prev parent reply other threads:[~2015-06-11 1:49 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
[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 [this message]
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=20150611014647.GS27932@nl.grid.coop \
--to=hozer@hozed$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=patrick.mccorry@newcastle$(echo .)ac.uk \
/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