public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
To: "yanmaani@cock.li" <yanmaani@cock.li>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Cc: Prayank <prayank@tutanota.de>
Subject: Re: [bitcoin-dev] bitcoin.org missing bitcoin core version 22.0
Date: Mon, 08 Nov 2021 03:02:33 +0000	[thread overview]
Message-ID: <d-6yONWH6zDSQXl7l6cJR2QsGw_iL-CyTJI16XZ4AkAwAdT65p3JylrIZ4VLbAAFQyfxyaDA3zUhctgiEkJKVQvfhzA-slPmPYdKW1L8M_4=@protonmail.com> (raw)
In-Reply-To: <3d686c3a100338514c3ebcc264ec24f2@cock.li>

Good morning yanmaani,


> > 3.More people from different countries getting involved in important
> > roles.
>
> Isn't Bitcoin already plenty distributed? Funding people in
> under-represented countries seems to me like a textbook exercise in
> 'box-ticking, but moreover, I'd frankly rather have reasonably well-off
> guys from Western Europe/America who have the financial backbone to not
> worry that much about attacks to their funding, than mercenaries who
> have to follow orders or get fired. Even if they're from West
> Uzbekistan.
>
> (Maybe they need a union?)
>
> > 4.Few anons.
>
> Gonna guess you mean "a few anons," not fewer anons.
>
> Again, problem is money. These days, nobody threatens anyone with
> anything substantive, like murder - the threats all involve cutting off
> some funding. So having anonymous people being funded by non-robust
> sources doesn't really buy you that much, because the weakest link will
> pretty much never be the de-jure, legal freedom of an individual.
>
> Having a system that allows people to fund anonymous people better would
> be interesting, but it has some challenges with trust and so on.

<ZmnSCPxj coughs quietly in GMT+8 timezone>

On the other hand, one can argue that "ZmnSCPxj" at this point is a bonafide name (that happens to once have been simply a random sequence of letters) rather than an anonymous cover.

As to box-ticking: the simple fact of the matter is that smart humans will arise everywhere.
It is to the interest of Bitcoin users that more of thhem contribute to the success of Bitcoin.
The alternative by default is that smart people who became smart because they happened to start out with the disadvantage of having to fight tooth and claw in a bad environment will be quite willing to do anything, including attack Bitcoin, just to get out of such a situation.

Regards,
ZmnSCPxj


  reply	other threads:[~2021-11-08  3:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20 14:47 [bitcoin-dev] bitcoin.org missing bitcoin core version 22.0 Prayank
2021-10-20 19:20 ` Owen Gunden
2021-10-20 19:37   ` Pieter Wuille
2021-10-20 19:49     ` Owen Gunden
2021-10-20 19:43   ` Charles Hill
2021-10-20 20:18   ` Kate Salazar
2021-11-05  8:17     ` Prayank
2021-11-05 10:52       ` damian
2021-11-05 14:45       ` yanmaani
2021-11-08  3:02         ` ZmnSCPxj [this message]
2021-11-09 12:49         ` Prayank
  -- strict thread matches above, loose matches on Subject: below --
2021-10-20 21:50 Andrew Chow
2021-10-20 12:54 Owen Gunden

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='d-6yONWH6zDSQXl7l6cJR2QsGw_iL-CyTJI16XZ4AkAwAdT65p3JylrIZ4VLbAAFQyfxyaDA3zUhctgiEkJKVQvfhzA-slPmPYdKW1L8M_4=@protonmail.com' \
    --to=zmnscpxj@protonmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=prayank@tutanota.de \
    --cc=yanmaani@cock.li \
    /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