From: Mike Hearn <mike@plan99.net>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>,
electrum.desktop@gmail.com
Subject: Re: [Bitcoin-development] Electrum security model concerns
Date: Wed, 10 Oct 2012 17:55:44 +0200 [thread overview]
Message-ID: <CANEZrP3Ei8tU=r_gp5K1fPGFe4gvX02gp+yuQRi0cwHhLLTe8g@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgSkVRx3Tk-7ufMDb3a44eTK=6COOh_FBWqrmwH4ogFhgA@mail.gmail.com>
> I tried in IRC and got no response. These messages are copying the
> only contact email address I could find.
Forum private message may work better.
> I think this is very hard because this matter is rapidly politicized.
> There are some in the community who will instantly allege misconduct
> when there is a mis-agreement.
Yeah, but that's only an issue if it ends up being an intractable
disagreement between the people who are reviewing changes to the core
site. The clients page itself was contentious but we still arrived at
something reasonably professional looking and moved on.
> discussion here... instead of, e.g. starting the process to remove it
> from the bitcoin.org clients page.
I don't think it should be removed. At most the description should be
updated to point to a discussion of the tradeoffs of that class of
apps (same for BitcoinSpinner).
next prev parent reply other threads:[~2012-10-10 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 16:37 [Bitcoin-development] Electrum security model concerns Gregory Maxwell
2012-10-08 11:52 ` Mike Hearn
2012-10-09 3:22 ` Gregory Maxwell
2012-10-10 11:19 ` Mike Hearn
2012-10-10 14:06 ` Gary Rowe
2012-10-10 15:23 ` Gregory Maxwell
2012-10-10 15:55 ` Mike Hearn [this message]
2012-11-15 23:45 ` Gregory Maxwell
2012-11-16 15:59 ` Mike Hearn
2012-11-16 17:44 ` Mike Hearn
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='CANEZrP3Ei8tU=r_gp5K1fPGFe4gvX02gp+yuQRi0cwHhLLTe8g@mail.gmail.com' \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=electrum.desktop@gmail.com \
--cc=gmaxwell@gmail.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