From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-Status: No, score=-3.8 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id EE0361F4B4;
	Mon, 21 Dec 2020 21:39:14 +0000 (UTC)
Date: Mon, 21 Dec 2020 21:39:14 +0000
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: public-inbox + mlmmj best practices?
Message-ID: <20201221213914.GA9374@dcvr>
References: <20201221212032.syunaxzrvcqcrose@chatter.i7.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20201221212032.syunaxzrvcqcrose@chatter.i7.local>
List-Id: <meta.public-inbox.org>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Hello:
> 
> One of our projects is looking at mailing list hosting and I was wondering if
> I should steer them towards public-inbox + mlmmj as opposed to things like the
> moribund googlegroups, groups.io, etc.
> 
> I know meta uses mlmmj, but there don't appear to be many docs on how things
> are organized behind the scenes. Is there anything to help me figure out the
> best arrangement for this setup?

There's scripts/ssoma-replay which was v1-only and dependent on
ssoma.  I've been meaning to convert into something that reads
NNTP so it's not locked into public-inbox.  Maybe it could be
part of `lei', too, for piping to arbitrary commands, dunno...