user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: "Nicolás Ojeda Bär" <n.oje.bar@gmail.com>
Cc: meta@public-inbox.org
Subject: Re: Relationship between public-inbox and ssoma?
Date: Mon, 5 Mar 2018 02:07:54 +0000	[thread overview]
Message-ID: <20180305020754.GA11496@dcvr> (raw)
In-Reply-To: <m2371f9wau.fsf@gmail.com>

Nicolás Ojeda Bär <n.oje.bar@gmail.com> wrote:
> Hello,
> 
> Thanks very much for this great project.
> 
> I am a bit puzzled about the difference between public-inbox and ssoma. In particular:
> 
> - What is the difference between public-inbox-mda and ssoma-mda ?

public-inbox-mda is more suitable for public endpoints where
it's the primary entry point for a publically-shared mail.
ssoma-mda is/was intended for personal mail.  Originally,
public-inbox depended on and used ssoma, but that was given up
for more performance.

Sidenote: I don't recommend public-inbox-mda for running
_mirrors_ of existing mailing lists since it's stricter than
what most lists accept.  public-inbox-watch is more lenient and
more performant (on Linux with inotify, at least); so I wrote
it for mirroring.

> - Are the git repository formats the same for public-inbox and ssoma ?

Currently they are the same with one exception: ssoma allows two
different messages (different blob SHA-1) to have the same
Message-Id by default; public-inbox (current version) does not.
(ssoma-mda has a "-1" option to disable duplicate Message-Id).

The work-in-progress "v2" public-inbox format diverges and I
don't currently have plans to port ssoma to use it.  The v1
format will remain supported in public-inbox.

I'm not sure if ssoma is worth the effort any more, as it's too
much effort to promote a new sync protocol (even if based on
git).  I'd rather improve NNTP servers and clients as an option
for people to read public inboxes.

> Any comments appreciated.
> 
> Thanks a lot!

No problem, thanks for your interest.

  reply	other threads:[~2018-03-05  2:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05  0:54 Relationship between public-inbox and ssoma? Nicolás Ojeda Bär
2018-03-05  2:07 ` Eric Wong [this message]
2018-03-05 11:45   ` Nicolás Ojeda Bär
2018-03-05 17:50     ` Eric Wong
2018-03-05 18:06       ` Nicolás Ojeda Bär
2018-03-19  7:43         ` watch performance [was: Relationship between public-inbox and ssoma?] Eric Wong
2018-03-15 15:30   ` internal format (was: Relationship between public-inbox and ssoma?) Stefan Monnier
2018-03-15 16:40     ` Eric Wong
2018-03-15 18:49       ` internal format Stefan Monnier
2018-03-15 20:14         ` Eric Wong
2018-03-15 21:05           ` Stefan Monnier
2018-03-15 21:21             ` Eric Wong

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

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180305020754.GA11496@dcvr \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    --cc=n.oje.bar@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).