public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: John Smith <witchspace81@gmail.com>
To: Chris Acheson <chris_acheson@lavabit.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] The forums...
Date: Tue, 19 Jul 2011 06:54:45 +0000	[thread overview]
Message-ID: <CAJNQ0ssiZ9ubShGe4wCSOAbj_D4PbmP1C6g6VmBbRw1GaTwA3g@mail.gmail.com> (raw)
In-Reply-To: <4E2492CE.9040500@lavabit.com>

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

Ah, right, I think stackexchange is pretty good for that. I committed.

JS

On Mon, Jul 18, 2011 at 8:08 PM, Chris Acheson <chris_acheson@lavabit.com>wrote:

> I've been pushing for the Bitcoin Stack-Exchange as our main
> user/merchant support site:
>
> <http://area51.stackexchange.com/proposals/30763/bitcoin-crypto-currency>
>
> I think the Stack Exchange format is ideal, since the
> acceptable/unacceptable topics are defined in advance, and it has a good
> user moderation/reputation system.  The site will be for technical and
> conceptual questions only, no politics or philosophy, and obviously no
> buying and selling.  This makes it unattractive to the kooks and
> hucksters, and therefore unattractive to the trolls as well.
>
> At the time of this writing, we still need 64 more people to commit to
> using the site before it will launch, 48 of which need to be established
> Stack Exchange users.  At the rate we've been going, the site should be
> up around the end of August.  I'd like to make it happen before then, so
> please join up!
>
>
>
> ------------------------------------------------------------------------------
> Storage Efficiency Calculator
> This modeling tool is based on patent-pending intellectual property that
> has been used successfully in hundreds of IBM storage optimization engage-
> ments, worldwide.  Store less, Store more with what you own, Move data to
> the right place. Try It Now!
> http://www.accelacomm.com/jaw/sfnl/114/51427378/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>

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

  reply	other threads:[~2011-07-19  6:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 20:08 [Bitcoin-development] The forums Chris Acheson
2011-07-19  6:54 ` John Smith [this message]
2011-07-19 17:07 ` Chris Acheson
2011-08-12 17:32   ` Vladimir Marchenko
  -- strict thread matches above, loose matches on Subject: below --
2011-07-16  9:34 John Smith
2011-07-16 10:54 ` Matt Corallo
2011-07-16 11:07   ` John Smith
2011-07-16 11:20     ` John Smith
2011-07-16 23:35       ` Jeff Garzik
2011-07-17  1:16         ` Douglas Huff
2011-07-17  2:00           ` Jeff Garzik
2011-07-17  2:12             ` Robert McKay
2011-07-17 10:46               ` Matt Corallo
2011-07-17 17:12                 ` Douglas Huff
2011-07-18  4:36                   ` John Smith
     [not found]               ` <CAJNQ0suMJAApg-fK70BBAHRT_41jc4-HMwxaHHccg0O+MOvV0A@mail.gmail.com>
2011-07-17 10:59                 ` John Smith
2011-07-17 12:30                   ` Luke-Jr

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=CAJNQ0ssiZ9ubShGe4wCSOAbj_D4PbmP1C6g6VmBbRw1GaTwA3g@mail.gmail.com \
    --to=witchspace81@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=chris_acheson@lavabit.com \
    /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