emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Wong <e@yhbt.net>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org
Subject: Re: New mailing list archive at https://orgmode/list/
Date: Mon, 8 Jun 2020 04:55:06 +0000	[thread overview]
Message-ID: <20200608045506.GB20150@dcvr> (raw)
In-Reply-To: <87pnaamarm.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
> Kyle Meyer <kyle@kyleam.com> writes:
> > [ +cc Eric Wong, mostly to say thanks for all the work he puts into
> >   public-inbox, which is the software behind these archives, but also so
> >   that he can correct me if I misrepresent any capabilities of or plans
> >   for public-inbox ]
> Thanks for this response, Kyle (and thanks for public-inbox, Eric)!

you're welcome, both :>

> You wouldn't really use one backend (nnweb) to provide search support
> for another (nntp). nnir can assign different search engines to
> different backends -- what a "search engine" boils down to is a function
> that accepts group search criteria, and returns groups and article
> numbers (and optional relevance scoring) for matching messages. So if
> public-inbox had some sort of an API that accepted a query and returned
> the above information in some sort of easily-digestible format, it
> wouldn't be hard to write a engine for it. Articles referenced in the
> search results would then be retrieved via NNTP, so the article numbers
> would need to correspond.

Fwiw, I've been trying to avoid exposing NNTP article numbers in
the HTTP endpoint in favor of Message-IDs because serial numbers
aren't decentralization-friendly.  Of course, sometimes
Message-IDs get reused, so public-inbox will return all messages
which match a particular Message-ID in those rare cases.

Btw, POST with the "&x=m" query parameter already allows search
to return a gzipped mboxrd.

And also what I just wrote about about JMAP/GraphQL in the other

A read-only IMAP server is also coming with search support,
and IMAP UIDs will be equivalent to NNTP article numbers.

  reply	other threads:[~2020-06-08  7:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05  7:47 New mailing list archive at https://orgmode/list/ Bastien
2020-06-05  8:43 ` Marco Wahl
2020-06-06  8:15   ` Bastien
2020-06-05  9:39 ` Eric S Fraga
2020-06-05 10:51   ` Bastien
2020-06-05 11:24     ` Diego Zamboni
2020-06-05 14:04       ` Bastien
2020-06-05 15:47 ` Eric Abrahamsen
2020-06-08  3:29   ` Kyle Meyer
2020-06-08  4:39     ` Eric Abrahamsen
2020-06-08  4:55       ` Eric Wong [this message]
2020-06-12 16:08         ` Eric Abrahamsen
2020-06-14  6:17           ` Kyle Meyer
2020-06-18 16:39             ` Eric Abrahamsen
2020-06-18 17:11               ` Kyle Meyer
2020-06-18 17:18                 ` Eric Abrahamsen
2020-06-18 17:43                   ` Colin Baxter
2020-06-19  3:01                   ` Kyle Meyer
2020-06-19  8:02                     ` Eric Wong
2020-06-19 17:37                       ` Eric Abrahamsen
2020-06-08  4:47     ` Eric Wong
2020-08-14 10:39 ` mailing list archive link in FAQ Maxim Nikulin
2020-08-14 11:16   ` Maxim Nikulin
2020-08-15 20:25     ` Kyle Meyer
2020-08-17 16:01       ` Maxim Nikulin
2020-08-17 23:55         ` Kyle Meyer

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=20200608045506.GB20150@dcvr \
    --to=e@yhbt.net \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \


* 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


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).