public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tao Effect <contact@taoeffect•com>
To: Bryan Bishop <kanzure@gmail•com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
Date: Tue, 7 Nov 2023 12:57:02 -0800	[thread overview]
Message-ID: <E10F952A-958D-47CA-893C-A4EBB87BCC43@taoeffect.com> (raw)
In-Reply-To: <CABaSBaz9OTSVa1KNk0GOrH3T-kRF_7OPVu0AtpuaFGVB=zhdwQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]

Hi, I also have faced this same problem, and here’s my solution to it:

Use the latest version of https://www.simplemachines.org/ .

This is the same forum software that powered Bitcointalk, Silk Road, etc.

It has many advantages over every other platform out there:

1. It has great anti-spam prevention tools.
2. It gives you the tools you’ve requested with respect to moderation (individual moderation accounts with customizable permissions).
3. It is simple to use.
4. It is pretty and well designed, and allows you to organize threads and forums really well (unlike Discourse).
5. It doesn’t make unnecessary use of JavaScript (unlike Discourse), and therefore works well with all search engines (present and future).
6. You can self-host it, and migrate it to another server if needed, allowing the community to maintain full control over the data (unlike Microsoft/Github).
7. It supports great search functionality.
8. It is open source, and has many community plugins.
9. It runs anywhere PHP runs.
10. It is fast.
11. It has a well established history of powering Bitcoin communities. It has been with us from Day 1.

After using phpBB for years, researching other forums software, I switched to SMF, and stuck with it. I’m happy I did so. I recommend it.

Kind regards,
Greg Slepak

> On Nov 7, 2023, at 7:37 AM, Bryan Bishop via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> 
> [moving]


[-- Attachment #2: Type: text/html, Size: 2074 bytes --]

  parent reply	other threads:[~2023-11-07 21:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 15:37 Bryan Bishop
2023-11-07 16:12 ` Andrew Chow
2023-11-08  9:05   ` email
2023-11-07 17:03 ` Ademan
2023-11-07 18:14   ` Andrew Chow
2023-11-07 19:41     ` Christopher Allen
2023-11-07 22:24       ` Ryan Breen
2023-11-07 22:59       ` Peter Todd
2023-11-07 20:15     ` Ademan
2023-11-09  4:03     ` William Casarin
2023-11-07 23:07   ` Peter Todd
2023-11-07 17:48 ` Andreas Schildbach
2023-11-07 20:07 ` David A. Harding
2023-11-07 21:03   ` Keagan McClelland
2023-11-07 20:57 ` Tao Effect [this message]
2023-11-07 22:10 ` ponymontana
2023-11-07 23:08 ` Peter Todd
2023-11-08 14:29   ` Emil Pfeffer
2023-11-08  3:56 ` Anthony Towns
2023-11-13  2:58 ` Antoine Riard
2023-11-13 15:05 ` Overthefalls
2023-11-13 18:51   ` alicexbt
2023-11-14 15:32     ` Overthefalls
2023-11-11 10:54 vjudeu
2024-01-04 13:50 ` Brad Morrison
     [not found] <mailman.15.1699963203.5599.bitcoin-dev@lists.linuxfoundation.org>
2023-11-14 12:32 ` Ali Sherief

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=E10F952A-958D-47CA-893C-A4EBB87BCC43@taoeffect.com \
    --to=contact@taoeffect$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=kanzure@gmail$(echo .)com \
    /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