Email list hosting service & mailing list manager

Mailman objections Lassi Kortela (06 Dec 2023 21:40 UTC)
Re: Mailman objections Arthur A. Gleckler (06 Dec 2023 22:03 UTC)
Re: Mailman objections Lassi Kortela (09 Dec 2023 21:05 UTC)
Re: Mailman objections Arthur A. Gleckler (10 Dec 2023 01:55 UTC)
Re: Mailman objections Stephen De Gabrielle (10 Dec 2023 11:42 UTC)
Re: Mailman objections John Cowan (10 Dec 2023 13:11 UTC)
Re: Mailman objections Lassi Kortela (10 Dec 2023 13:19 UTC)
Re: Mailman objections Arthur A. Gleckler (10 Dec 2023 17:40 UTC)
Re: Mailman objections MSavoritias (10 Dec 2023 17:48 UTC)
Re: Mailman objections Arthur A. Gleckler (10 Dec 2023 18:01 UTC)
Re: Mailman objections MSavoritias (10 Dec 2023 18:34 UTC)
Range of services to host under the domain Lassi Kortela (10 Dec 2023 18:02 UTC)
Re: Mailman objections Lassi Kortela (10 Dec 2023 13:16 UTC)
Re: Mailman objections Vasilij Schneidermann (10 Dec 2023 19:16 UTC)
Re: Mailman objections Lassi Kortela (10 Dec 2023 19:29 UTC)
Re: Mailman objections Arthur A. Gleckler (15 Dec 2023 03:24 UTC)
Re: Mailman objections John Cowan (15 Dec 2023 04:15 UTC)
Re: Mailman objections Arthur A. Gleckler (15 Dec 2023 04:19 UTC)
Re: Mailman objections John Cowan (15 Dec 2023 04:46 UTC)
Re: Mailman objections Arthur A. Gleckler (15 Dec 2023 05:42 UTC)

Range of services to host under the domain Lassi Kortela 10 Dec 2023 18:01 UTC

> I have seen a lot of arguments in this thread against Slack or whatever.
>
> As a counterpoint I haven't seen mentioned:
>
> 1. The accessibility benefits that come with Discourse and chat systems
> like xmpp. instead of IRC/email.
>
> 2. The newcomers that may encourage to be involved to the development of
> scheme. If these are wanted of course.

Because those arguments are made repeatedly all over the internet, and
because this thread was about how to keep the existing mailing list
tradition going (albeit that it has now sidetracked a bit).

Anyway, IMHO scheme.org should be open to any FOSS tech that does not
put the domain at risk. Establishing discourse.scheme.org and/or
xmpp.scheme.org is fine by me as long as I don't have to maintain them.
Same goes for sourcehut, gitlab, gopher, etc.

What should probably be out of bounds:

1) Commercial software (for which scheme.com would be more appropriate)

2) Social media (Mastodon, etc.)

Commercial is too divisive across the Scheme community. Social media
focuses on "let me tell you who I am" flavored communications; those are
a magnet for unproductive conflict.