From: Milly Bitcoin <milly@bitcoins•info>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Scaling Bitcoin conference micro-report
Date: Sun, 20 Sep 2015 16:54:30 -0400 [thread overview]
Message-ID: <55FF1D06.7000301@bitcoins.info> (raw)
In-Reply-To: <CAAjy6kCACMaW_7q8w2hOGizEoXGPiZvB0+je_3AW6=WxDv28Uw@mail.gmail.com>
Your reply has nothing to do with my comment. It looks like you just go
around posting wing nut stuff without regard to what is being discussed.
A proper threat model considers all possible threats and looks at the
probability of each.
Obviously from your comment you have no experience in threat models and
limited education in general.
Russ
On 9/20/2015 4:23 PM, Steven Pine wrote:
> It's amazing how foolish some people are to continue trusting
> governments especially in light of recent history: a seemingly endless,
> Orwellian 'war on terror', multiple regional conflicts often justified
> by fake evidence, wholesale disregard of law and basic human covenants
> such as do not torture, ubiquitous and secret global surveillance.
>
> Anyone who doesn't consider governments the proper threat model is
> either a shill or an idiot.
>
> On Sep 20, 2015 12:34 PM, "Milly Bitcoin via bitcoin-dev"
> <bitcoin-dev@lists•linuxfoundation.org
> <mailto:bitcoin-dev@lists•linuxfoundation.org>> wrote:
>
> Until this is settled, Bitcoin has no clear direction and
> developers cannot make effective decisions:
>
>
> How exactly do things set "settled" in this environment?
>
> People looking at Bitcoin think a small group of developers and
> miners "control" these decisions. Not sure if "control" is the
> right word but that is the perception.
>
> Russ
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> <mailto:bitcoin-dev@lists•linuxfoundation.org>
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
next prev parent reply other threads:[~2015-09-20 20:54 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 21:32 Jeff Garzik
2015-09-16 21:51 ` Matt Corallo
2015-09-18 5:55 ` Mark Friedenbach
2015-09-18 17:10 ` Dave Scotese
2015-09-18 17:28 ` Eric Lombrozo
2015-09-18 20:06 ` Matt Corallo
2015-09-18 22:33 ` Mike Hearn
2015-09-19 16:03 ` cipher anthem
2015-09-19 20:43 ` Mike Hearn
2015-09-19 1:47 ` Peter Todd
2015-09-19 6:06 ` NxtChg
2015-09-19 6:56 ` Eric Voskuil
2015-09-19 7:27 ` NxtChg
2015-09-19 7:39 ` Eric Voskuil
2015-09-19 7:57 ` NxtChg
2015-09-19 8:52 ` Eric Voskuil
2015-09-19 13:32 ` NxtChg
2015-09-19 20:57 ` Mike Hearn
2015-09-19 21:53 ` phm
2015-09-20 1:26 ` Dave Scotese
2015-09-20 2:18 ` Milly Bitcoin
2015-09-20 9:18 ` NxtChg
2015-09-20 9:25 ` Mike Hearn
2015-09-20 15:43 ` Mark Friedenbach
2015-09-20 16:21 ` NxtChg
2015-09-20 16:34 ` Milly Bitcoin
2015-09-20 20:23 ` Steven Pine
2015-09-20 20:54 ` Milly Bitcoin [this message]
2015-09-20 21:33 ` s7r
2015-09-20 21:45 ` Eric Lombrozo
2015-09-20 22:02 ` Milly Bitcoin
2015-09-20 22:21 ` Eric Lombrozo
2015-09-20 22:51 ` Milly Bitcoin
2015-09-20 23:11 ` Eric Lombrozo
2015-09-21 0:11 ` Dave Scotese
2015-09-21 5:04 ` Corey Haddad
2015-09-21 11:45 ` Milly Bitcoin
2015-09-21 8:48 ` NxtChg
2015-09-20 21:10 ` NxtChg
2015-09-20 21:13 ` Steven Pine
2015-09-20 21:34 ` Milly Bitcoin
2015-09-20 21:24 ` Milly Bitcoin
2015-09-20 21:16 ` Eric Lombrozo
2015-09-21 10:30 ` Mike Hearn
2015-09-18 22:15 ` [bitcoin-dev] Improving Blocksize Communication Through Markets Paul Sztorc
2015-09-20 11:41 ` Isidor Zeuner
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=55FF1D06.7000301@bitcoins.info \
--to=milly@bitcoins$(echo .)info \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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