Any #lei / #publicinbox experts around to help me with this (maybe @monsieuricon?):

What's the best to subscribe to a thread on lore[1]?

My current plan looks like this:

* Move a message from the thread I care about to a dedicated imap folder

* regularly run a script that

1. extracts the msg-ids from all messages in that folder
2. run a lei query[2] to get all messages from threads with said msg-ids

Or can lei handle that more elegantly, e.g. without a script?

[1] e.g. if one of a few Dozent mails an earlier lei search found turns out to be something I want to monitor?

[2] e.g. "lei q -I https://lore.kernel.org/all/ -o maildir:/some/place --threads --dedupe=mid [email protected] rt:90.days.ago.."

All of lore.kernel.org

So today I failed to configure #anubis in front of #publicinbox on #nixos

I try to set up a #nixos host with a #simple-nixos-mailserver and #publicinbox and test the whole thing with a nixos VM test.

But I fail hard to get the very basics working - right now making public-inbox behind a nginx reverse proxy available (curl'ing the site returns 404).

Has someone done this before and some nix code I can look at?

I ask this every now and then here: has someone a #nixos #mailserver #snm setup for #mailinglist #mailinglists with #publicinbox (the software, not the concept) that they can share?
Has someone a template for setting up simple #nixos #mail #server #snm with a mailinglist (or multiple) and #publicinbox ?
Lei, the Local Email Interface

The documentation of #publicinbox is really bad.

I just cloned the git public inbox, how can I now read it?

Re-reading #email patch workflow stuff and the #b4 and #publicinbox docs and ... maaan... that is the only true way of developing software together in large teams.

I mean, I don't care for your 5 person project, do what you want.

But for large projects, that really is the only way to develop that truly scales.

Maybe, just maybe, #radicle can become the second way of doing that. Right now, it clearly is not (mainly because it is too young), but I still have hope!

That said, #sourcehut is also really nice, but right now I like public-inbox a bit more. I guess you could combine the two, possibly?

#git #github #shithub #gitlab #shitlab

I want to process 4714 message-id's to collect some patch stats for the last year. I could collect with #b4 which uses the #lore archive but I wonder does it cache or will I end up with lots of redundant mbx files? Worse still would I just be hammering an overloaded server? I guess I should check out the #PublicInbox docs.

Bottle in the sea to the #fediverse, looking for author and owner of the great https://yhetil.org unofficial online service.

yhetil.org provides #publicinbox mirrors to main #emacs, #guile and #guix maillists, facilitating a practical means of browsing through history of exchanges, replying and contributing.

https://sigmoid.social/@csantosb/113962405321383147

unofficially hosted mirrors at yhetil.org