@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?

#PublicInbox 1.6.0 :
« A big #release containing several performance optimizations, a new #anonymous #IMAP server, and more.

[…] Indexing can be now be tuned to give somewhat usable performance on HDD storage, though we can't defy the laws of physics, either.

[…] See https://public-inbox.org/TODO for what the future holds. »
https://public-inbox.org/meta/20200916200309.public-inbox-1.6.0-rele@sed/
#Mail #Git #Perl