emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.org, Eric Wong <e@yhbt.net>
Subject: Re: New mailing list archive at https://orgmode/list/
Date: Sun, 07 Jun 2020 21:39:25 -0700	[thread overview]
Message-ID: <87pnaamarm.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87h7vmw7zp.fsf@kyleam.com> (Kyle Meyer's message of "Mon, 08 Jun 2020 03:29:14 +0000")

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

>> Bastien <bzg@gnu.org> writes:
>>> with Kyle's help, I've set up a new mailing list archive:
>>> https://orgmode/list/
>>> References in https://orgmode.org and https://orgmode.org/list
>>> that pointed to gmane.org are now using this, so many links are
>>> functional again.
>> Cool! I note that there's also NNTP access at news.yhetil.org, in
>> addition to gmane.io. Does yhetil have a search interface, or are there
>> other mechanisms for searching the archives (ideally in Gnus :))?
> The web interface (<https://orgmode.org/list> or
> <https://yhetil.org/orgmode>) is the main mechanism for searching.  You
> don't necessarily have to leave Emacs for that, as public-inbox's pages
> render nicely in EWW.  But of course that's not the Gnus-based search
> you're hoping for.
> I use Gnus to follow some lists via NNTP, a mix of public-inbox archives
> and gmane.io, but I've never really done any fancy searching from it and
> don't use Gnus for my mail.  To try it out, I hit GG to search on a
> gmane.io list, but got an error [^1], so I suppose its search capability
> went away with Gmane's HTTP interface.

Yup, Gmane hasn't had in-Gnus search since then.

> Poking around a bit, I guess nnweb.el would be the main place that
> public-inbox's web search could be integrated into Gnus?  I've been
> (slowly) working on an Emacs package [^2] that adds public-inbox-related
> functionality to different "endpoints" (currently Notmuch, Gnus, EWW,
> Elfeed), and I'd be interested in any ideas for improving the Gnus
> support.

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.

(Basically this is all the old Gmane search functionality did.)

> A couple of other notes:
>   * You can get the entire archive locally with a 'git clone', in which
>     case you can transform it into a form that can be indexed/searched
>     however you prefer (including with public-inbox, running a local
>     public-inbox-httpd).  There are some pointers on extracting an
>     archive to a Maildir at
>     <https://public-inbox.org/meta/20200426060542.GA15896@dcvr/>.

That would certainly be one approach! But not one that scales to many
users :)

>   * In the message above, Eric W. mentions that he is considering
>     working on client tools with mairix-like search results.  That'd
>     make the search capabilities available locally, and I'd imagine
>     something like that could be nicely integrated with Gnus,
>     considering it already has a mairix backend to use as a guide.

Yup, basically we'd just want a way to retrieve matching article numbers
that (ideally) didn't involve scraping a web page.

Thanks again,

  reply	other threads:[~2020-06-08  4:40 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 [this message]
2020-06-08  4:55       ` Eric Wong
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=87pnaamarm.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=bzg@gnu.org \
    --cc=e@yhbt.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.com \


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