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

@jfrench @donkeyblam @baldur #Git has some glaring omissions in that design that #Fossil doesn't have (all the bug-tracking and wiki features).

#GitBug (https://github.com/MichaelMure/git-bug) attempts to fix that, but it hasn't been widely adopted.

(Yes, ironic choice of hosting, I know. Incidentally Gitlab is also enshittifying.)

Working over #email also works better if you also use #PublicInbox (https://public-inbox.org/README.html), as synchronization of an archive is non-trivial if you just use mailman's builtins.

HTML email. Most #sourceware projects allow it, if there is at least a text/plain alternative.

But #publicinbox is not so forgiving, it only allows plain-text emails, HTML is rejected by default.

So the https://inbox.sourceware.org archive was incomplete.

We now have a filter that removes redundant HTML parts before storing in public-inbox. And we re-imported missing emails to make the archive complete.

But please don't sent HTML email. It will make DKIM verification of your email impossible.

@Hyolobrika @BrodieOnLinux In that case I would still recommend using some in-repository bug-tracking such as https://github.com/MichaelMure/git-bug, so that loss of the hosting instance for whatever reason doesn't kill the project.

The usual answer of #MailingLists https://sourcehut.org/blog/2020-10-29-how-mailing-lists-prevent-censorship/ & a #PublicInbox archive is also applicable to #AnonymousNetworks, but requires more setup. Using some of the NNTP servers on those networks for duplicating also works.

@nul For some additional censorship resistance & ease of porting mailing lists to new hosts, keeping a #PublicInbox (https://public-inbox.org/README.html) instance around is pretty nice.

I’m trying hard to love #PublicInbox, or to even just try it out, but I keep failing. To the point I’m not even sure what I’m supposed to get.

I guess I need “public-inbox for dummies”? Suggestions anyone?

#b4 is a handy tool for managing code review via emailed patches. It was designed to work with #publicinbox archives but it works on arbitrary #mbox's as well. #sourcehut supports pulling the mbox for a thread so it works there too!

https://lists.sr.ht/~sircmpwn/public-inbox/patches/20099

who needs github...

https://public-inbox.org/marketing.html hehe... #publicinbox
Example: https://lore.kernel.org/lkml/