user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: libreplanet-discuss@libreplanet.org
Cc: meta@public-inbox.org
Subject: libreplanet-discuss mirror on public-inbox.org
Date: Mon, 26 Jun 2017 21:12:45 +0000	[thread overview]
Message-ID: <20170626211245.GA32252@dcvr> (raw)

Hi all, a searchable, JWZ-threading-aware archive for the
libreplanet-discuss list is now available at:

	https://public-inbox.org/libreplanet-discuss/
        nntp://news.public-inbox.org/inbox.comp.libreplanet.discuss

For Tor users:
        http://ou63pmih66umazou.onion/libreplanet-discuss/
        nntp://ou63pmih66umazou.onion/inbox.comp.libreplanet.discuss

public-inbox stores all messages in git, allowing easy
synchronization and relatively efficient storage.

This means you can clone all the messages (around 20 MB):

	git clone --mirror https://public-inbox.org/libreplanet-discuss

And the AGPL-3.0+ source code:

	git clone https://public-inbox.org/public-inbox

And hack + run it yourself.  I suggest doing this since I am an
unreliable sysadmin and have frequent reliability problems
(or just want to encourage decentralization :>)

Feel free to run "git fetch" frequently on both of the above
repos to ensure up-to-date-ness.

It also allows some client-side customization via user-supplied
CSS (a work-in-progress):

https://public-inbox.org/design_www.txt (bottom of text)


All data was originally sourced from
ftp://list.gnu.org/libreplanet-discuss/ and lightly de-spammed.
Future messages will go through my Maildir for the
libreplanet-discuss list (via public-inbox-watch).
Please let me know if I missed or corrupted anything during the
import: bugs happen :x

                 reply	other threads:[~2017-06-26 21:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

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

  git send-email \
    --in-reply-to=20170626211245.GA32252@dcvr \
    --to=e@80x24.org \
    --cc=libreplanet-discuss@libreplanet.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://80x24.org/public-inbox.git

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