public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Milly Bitcoin <milly@bitcoins.info>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin mining idea
Date: Tue, 29 Sep 2015 02:13:18 -0400	[thread overview]
Message-ID: <560A2BFE.3080104@bitcoins.info> (raw)
In-Reply-To: <CALd2G5fUHbjrVAiOpLb=KwkQ4_Z-BoOsg6RNARexddaUZkvPmQ@mail.gmail.com>

> This is quite off topic,

I see a number of people claiming they know what should be posted to 
this list but those claims appear to be without merit.

The list states the subject is "Development discussion list for Bitcoin 
protocol and its implementation."  That is a pretty broad description 
that appears to encompass a number of topics that are claimed to be 
"off-topic" by people who seem to be making up their own rules.  One guy 
even contacts people and threatens to have the list moderated if you 
don't follow his rules even though it appears he has no such authority 
and there are no official rules he can reference.

Maybe there should be a more precise description if the discussion is to 
be limited in some way beyond the "official" description.

Russ




  reply	other threads:[~2015-09-29  6:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-27 17:53 [bitcoin-dev] Bitcoin mining idea Neil Haran
2015-09-28 13:33 ` Lauri Love
2015-09-29  5:47   ` Neil Haran
2015-09-29  5:56     ` Trevin Hofmann
2015-09-29  6:13       ` Milly Bitcoin [this message]
2015-09-29 21:07 ` Jeff Garzik
2015-09-29 22:58   ` Milly Bitcoin
2015-09-29 23:02     ` Jonathan Toomim (Toomim Bros)
2015-09-29 23:16       ` Milly Bitcoin
2015-09-29 23:54         ` Jeff Garzik
2015-09-30  0:07           ` Milly Bitcoin
2015-09-30  0:10             ` Jeff Garzik

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=560A2BFE.3080104@bitcoins.info \
    --to=milly@bitcoins.info \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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