Received: from out0.migadu.com (out0.migadu.com [94.23.1.103])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 11EF5782CD7
	for <~alpine/devel@lists.alpinelinux.org>; Wed, 22 Apr 2020 20:07:54 +0000 (UTC)
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dereferenced.org;
	s=default; t=1587586073;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=9VbZNC0NhrLW2FaafVDLIlXiiuuTSDg+2ZuU9ROwCRs=;
	b=RhFENF2tj2UGGNoorgLWef3q85p70dqlX+bdzPNrsuZve58Qftch2xU+ZDOIzfq6HW1RfD
	GMy9+TU1q21sN2ZOvYsM3h2lG2z/6GFFRGxCPsS5HX74ES2KJ3AeDicZrcmVJIeqcvrSVJ
	W2jHCQHjz1dQpTEvuCTKnU/g/a3o4MM=
From: Ariadne Conill <ariadne@dereferenced.org>
To: Wolf <wolf@wolfsden.cz>
Cc: j3s <j3s@c3f.net>, ~alpine/devel@lists.alpinelinux.org
Subject: Re: mailing lists, processes, modernization
Date: Wed, 22 Apr 2020 14:07:43 -0600
Message-ID: <1968226.q4d85KMkOx@localhost>
In-Reply-To: <20200422170608.c2foaeyscr2gq3lr@wolfsden.cz>
References: <66694f73048e047cadbe9e3f715801d8@dereferenced.org> <3422451.PHdjXsENna@localhost> <20200422170608.c2foaeyscr2gq3lr@wolfsden.cz>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.90

Hello,

On Wednesday, April 22, 2020 11:06:08 AM MDT Wolf wrote:
> On 2020-04-22 10:27:21 -0600, Ariadne Conill wrote:
> > As Wolf mentioned, modern Hyperkitty versions can post from the web UI,
> > which is why it was proposed as an alternative to Discourse that allows
> > us to meet the same goal of allowing web and e-mail users to make use of
> > the same communications channel.
> 
> IMO it seems like a reasonable compromise.
> 
> At the same time, I do not know how hard it would be to add the same
> option to sourcehut. Or if ddevault would be willing to. But if yes, it
> would achieve the same goal without having to migrate anything.

Unfortunately, as a reminder, due to the way Sourcehut processes mail from 
several mail clients, including the default iOS and Android clients (rejecting 
such mail), we are going to have to switch anyway.  This has caused several 
contributors to stop contributing to the project already because they find 
being scolded by our mailing list server when they reply to an inquiry from 
their phone to be unacceptable.

While it is true that the Sourcehut mailing list software now has the 
capability to accept HTML e-mail, it requires that there be a text/plain part 
as well.  This unfortunately breaks both the iOS and Android e-mail clients, 
resulting in the mailing list advising you to read a website that simply 
suggests using an alternative client.

Asking people to make significant changes to their workflow simply to 
participate on our lists is obviously absurd, and that's where this process 
started six months ago.  Had we known last year that the Sourcehut software 
would be incompatible with commonly used e-mail software, such as the e-mail 
clients built in to iOS and Android, we would not have moved forward with the 
switch.

Ariadne