public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Chris Acheson <chris_acheson@lavabit.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] The forums...
Date: Tue, 19 Jul 2011 13:07:53 -0400	[thread overview]
Message-ID: <4E25B9E9.5020906@lavabit.com> (raw)
In-Reply-To: <4E2492CE.9040500@lavabit.com>

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

Could we just get the forum link removed entirely?  The current Google
search link does very little to disassociate the forum from the Bitcoin
project.  There's no need to have a forum link anyway, as there's
already a link to the wiki, which links to the forum, and can be edited
to link to other unofficial forums as well.

I just came across a thread by someone offering to sell a bitcoin mining
virus:

<http://forum.bitcoin.org/index.php?topic=21524.0>

I know there'd been complaints about illegal activity, but this is a
whole new level of bad PR compared to people just offering to sell
drugs.  Especially when there are responses like:

"Excuse me while I put this on every computer at my school."

"This would be so awesome if I could install it at every computer in my
college lab. So many bitcoins for me."

It doesn't just look like some one-off cybercriminal spam, it looks like
forum members in general support this kind of thing.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  parent reply	other threads:[~2011-07-19 17:07 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
2011-07-19 17:07 ` Chris Acheson [this message]
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=4E25B9E9.5020906@lavabit.com \
    --to=chris_acheson@lavabit.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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