public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: grarpamp <grarpamp@gmail•com>
To: Cpunks List <cypherpunks@cpunks•org>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Bitcoin philosophical musings and pressures 7 years in [drifted from: txrate, forking, etc]
Date: Tue, 7 Jul 2015 15:21:50 -0400	[thread overview]
Message-ID: <CAD2Ti28Tw7Kz+RoW3DYqEPbB4KfS=TiTSwbtneL7ps1QsKvzvw@mail.gmail.com> (raw)

> Then again maybe I am missing the key reasoning for this fork.

People often miss the fundamental reasons Bitcoin exists,
the various conjoined ethos behind its creation. This is to be
expected, it's so far ouside any thinking or life process they've
ever had to do or been exposed to. It's also partly why figuring
out what to do or code or adopt, is hard. And certainly not made
any easier by the long term need and the current value at stake.

Creating a system in which a Botswanan can give a few bits
of their impoverished wages to their friend in Mumbai without
it being gated, permitted, hierarchied, middlemanned, taxed,
tracked, stolen and feed-upon until pointless... this simply
doesn't compute for these people. Their school of thought is
centralization, profit, control and oppression. So of course they
see txrate ramming up against an artificial wall as perfectly fine,
it enables and perpetuates their legacy ways.

Regardless of whichever technical way the various walls are torn down,
what's important is that they are. And that those who are thinking
outside the box do, and continue to, take time to school these
legacy people such that they might someday become enlightened
and join the ethos.

Otherwise might as well work for ICBC, JPMC, HSBC, BNP, MUFG
and your favorite government. Probably not as much fun though.


                 reply	other threads:[~2015-07-07 19:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAD2Ti28Tw7Kz+RoW3DYqEPbB4KfS=TiTSwbtneL7ps1QsKvzvw@mail.gmail.com' \
    --to=grarpamp@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=cypherpunks@cpunks$(echo .)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