From: Vali Zero <valizero@yahoo.ro>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Annoucing Not-BitcoinXT
Date: Mon, 17 Aug 2015 13:40:44 +0100 [thread overview]
Message-ID: <1439815244.89850.YahooMailBasic@web173102.mail.ir2.yahoo.com> (raw)
In-Reply-To: <20150817100918.BD1F343128@smtp.hushmail.com>
Hi,
If you want to write such baseless acusations and inflamatory phrases, please do it somewhere else. We should have the highest respect for what these people are doing, and we should try to do something constructive, not waste time with anger and disrespect.
Nobody should be forced to do anything. People like you will not force me or anyone else to run code for your controversial hard fork just because you think the future will be bright with huge blocks. Just like the developers will not force you to continue running code implementing the current consensus rules.
The developers are not telling you what to do, they are trying to do what they consider is best for the ecosystem given their technical abilities.
Valiz
--------------------------------------------
În data de L, 17.8.15, NxtChg via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> a scris:
Subiect: Re: [bitcoin-dev] Annoucing Not-BitcoinXT
Către: jyellen@toothandmail.com, bitcoin-dev@lists.linuxfoundation.org
Data: Luni, 17 August 2015, 13:09
>Announcing Not-BitcoinXT
>https://github.com/xtbit/notbitcoinxt#not-bitcoin-xt
> "This version can be
used to protect the status quo until real technical
consensus is formed about the blocksize."
> "...real technical
consensus..."
You mean
the bunch of self-proclaimed Bitcoin wizards, who decided
they have the right to tell everybody what to do, and who
never got to grow up and are now angry at the world for not
listening to them anymore? That "technical
consensus"?
"Bitcoin is decentralized, but you are
only allowed to do what we tell you to do. It's our pet
project, we wrote code for it!"
That's what it all boils down to, all these
dirty games of calling XT an alt-coin and censoring its
posts, pretending to be Satoshi, sabotaging XT switch, etc.:
"How dare they not listen to Us The Smartest
anymore?!!!"
Pathetic.
The history will roll over you in a blink. The harder you
try, the quicker it will go.
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2015-08-17 12:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 22:34 [bitcoin-dev] Annoucing Not-BitcoinXT jyellen
2015-08-17 3:10 ` jl2012
2015-08-17 7:04 ` Peter Todd
2015-08-17 10:09 ` NxtChg
2015-08-17 12:40 ` Vali Zero [this message]
2015-08-17 13:34 ` NxtChg
2015-08-17 14:03 ` Eric Lombrozo
2015-08-17 14:09 ` Levin Keller
2015-08-17 14:30 ` Eric Lombrozo
2015-08-17 14:36 ` Adam Back
2015-08-17 14:58 ` GC
2015-08-17 15:03 ` Levin Keller
2015-08-17 15:07 ` Eric Lombrozo
2015-08-19 3:49 ` odinn
2015-08-17 15:10 ` NxtChg
2015-08-17 16:37 ` Eric Lombrozo
2015-08-17 16:55 ` Eric Lombrozo
2015-08-18 4:37 ` Dave Scotese
2015-08-18 5:13 ` GC
2015-08-18 5:33 ` Dave Scotese
2015-08-18 9:46 ` NxtChg
2015-08-19 9:47 ` Jorge Timón
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=1439815244.89850.YahooMailBasic@web173102.mail.ir2.yahoo.com \
--to=valizero@yahoo.ro \
--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