From: Natanael <natanael.l@gmail.com>
To: NxtChg <nxtchg@hush.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Censorship
Date: Mon, 31 Aug 2015 13:46:10 +0200 [thread overview]
Message-ID: <CAAt2M18R2oXypR8UU=D7bUnbiCxUuea1PqpHtJS10syJtaVc_w@mail.gmail.com> (raw)
In-Reply-To: <20150831084538.399E0200EF@smtp.hushmail.com>
[-- Attachment #1: Type: text/plain, Size: 2276 bytes --]
One last comment here on this topic;
For anybody who wants to discuss decentralized communication mechanisms in
general, they can come to www.reddit.com/r/p2pcomms (up until these
decentralized forums have become stable and common).
I've seen quite a few more of these projects lately, I want to make a list
of them and would definitely like to contribute to making them not just
usable, but good enough to gain popularity on their own.
(And in case you wonder about my approach to moderation: let every user
pick which moderators / filters / servers he trusts, and let them share
their subscription preferences in place of sharing links to centralized
forums.)
- Sent from my phone
Den 31 aug 2015 10:45 skrev "NxtChg via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org>:
>
> >I am creating a de-centralized forum, and I mean truly decentralized as I
> nor anyone else will be able to control it.
>
> Zander is working on the same thing:
> https://www.reddit.com/r/AetheralResearch/
>
> But it's actually quite difficult to make it truly censorship-resistant:
> both in solving the theymos factor and spam/abuse/overloading as an attack.
>
>
> >There is no doubt that the centralization and censorship of the Bitcoin
> community is massively inhibiting the advance of Bitcoin
> >and also the growth of the Bitcoin economy. We are scaring away
> intellectuals, businessman, and newbies that are just getting started.
>
> We have /r/bitcoinxt and so far it has been great. But we also need a
> regular forum.
>
> Roger Ver controls bitcoin.com, as I understand?
> https://bitcoin.com/forum/ would be nice.
>
> And it must be a real community, not "say whatever you want because free
> speech". We've seen how that turned out to be.
>
> Something like battle.net or Steam forums: heavily moderated, not for
> opinions, but for spam/noise/insults.
>
> Again, this needs leadership. Anyone can install a forum software, what is
> needed is an "official seal of approval" and regular presence of top XT
> people there.
>
> And a will to setup proper moderation. Then people will move.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 3228 bytes --]
next prev parent reply other threads:[~2015-08-31 11:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-21 18:03 [bitcoin-dev] Censorship sisadm101
2015-08-22 13:39 ` David Vorick
2015-08-23 6:48 ` Jorge Timón
2015-08-31 6:43 ` hurricanewarn1
2015-08-31 8:45 ` NxtChg
2015-08-31 9:35 ` hurricanewarn1
2015-08-31 9:37 ` Btc Drak
2015-08-31 9:49 ` NxtChg
2015-08-31 10:25 ` Btc Drak
2015-08-31 10:38 ` NxtChg
2015-08-31 9:51 ` NxtChg
2015-08-31 11:46 ` Natanael [this message]
2015-08-31 12:06 ` hurricanewarn1
2015-08-31 10:33 ` Wladimir J. van der Laan
[not found] <CALGZhhvAV3iB=QDs2-NtLR5U7toqnygQAWU_ShPvL1xWX_upQQ@mail.gmail.com>
2015-08-31 17:00 ` hurricanewarn1
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='CAAt2M18R2oXypR8UU=D7bUnbiCxUuea1PqpHtJS10syJtaVc_w@mail.gmail.com' \
--to=natanael.l@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=nxtchg@hush.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