public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] bitcoin-dev Digest, Vol 102, Issue 20
Date: Wed, 8 Nov 2023 06:47:15 +0000	[thread overview]
Message-ID: <CAPweEDxvu73nr=P27tzyzRRC+BTPW5+=g4pX_=N_MkfNJ2GL6w@mail.gmail.com> (raw)
In-Reply-To: <mailman.12459.1699415789.1202.bitcoin-dev@lists.linuxfoundation.org>

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

On Wednesday, November 8, 2023, <
bitcoin-dev-request@lists.linuxfoundation.org> wrote:

> delvingbitcoin.org is something I setup; it's a self-hosted discourse
> instance.

nice.

> For what it's worth, I think (discourse) forums have significant
> advantages over email for technical discussion:
>
>  * much better markup: you can write LaTeX for doing maths,

i love this aspect of discourse, but in all seriousness if
you are relying exclusively on "web interfaces" for standard
development of something as significant as bitcoin then there
is something very very wrong.

there is a reason why the linux kernel is hosted and run
(patches) entirely via email.

you *cannot* assume that every contributor will have permanent
24x7 high bandwidth internet.  i am currentl operating solely
off of a *mobile* LTE/WIFI dongle for example.  it is PAYG
*not* a contract.  service is adversely affected by weather
conditions and an "always-on web interface" is a serious
problem.

please please everyone: for goodness sake don't assume every
contributor will have real-time permanent high-quality
gigabit-speed internet just because in your country you happen
to have that, ok?

if you want graphs/maths you can use texstudio then
*commit the latex into a git repository* or upload it
somewhere online or ask someone to do so on your behalf.

(i run libre-soc.org entirely self-hosted and made sure
*all* resources are in git. mailing list (public-inbox - git),
wiki (ikiwiki - git), bugtracker is the only one (i considered
fossil and bugseverywhere)

ah! i forgot! of course, there is fossil!
https://opensource.com/article/20/11/fossil

l.


-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

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

           reply	other threads:[~2023-11-08  6:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <mailman.12459.1699415789.1202.bitcoin-dev@lists.linuxfoundation.org>]

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='CAPweEDxvu73nr=P27tzyzRRC+BTPW5+=g4pX_=N_MkfNJ2GL6w@mail.gmail.com' \
    --to=lkcl@lkcl.net \
    --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