user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: rack-devel@googlegroups.com
Cc: meta@public-inbox.org
Subject: [ANN] public-inbox.org/rack-devel mirror available
Date: Thu, 29 Jun 2017 00:40:42 +0000	[thread overview]
Message-ID: <20170629004042.GA5869@dcvr> (raw)

Gmane still isn't doing well, so my announcement(*) last year
about mirroring rack-devel@googlegroups has been moot unless
you're reading off NNTP.  Of course, Google Groups still seems
to require JS, making it inaccessible to some, including me :<

So, I've setup a mirror on my own server using an archive Christian
sent me last year, along with my own mail:

	https://public-inbox.org/rack-devel/
        nntp://news.public-inbox.org/inbox.comp.lang.ruby.rack.devel

Tor users can use .onion endpoints, too:

        http://ou63pmih66umazou.onion/rack-devel/
        nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.rack.devel


Fwiw, I also started mirroring ruby-core a few days ago, too:

	https://public-inbox.org/ruby-core/20170623032722.GA8124@dcvr/

There's also https://public-inbox.org/git/ for those interested
in git development.


You can also clone all the messages (around 10 MB):

	git clone --mirror https://public-inbox.org/rack-devel

And the AGPL-3.0+ source code (Perl5):

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

And hack + run it yourself.  I suggest doing this since I am an
unreliable sysadmin and wish to encourage decentralization.
Maybe I'll write a Ruby implementation, one day :)


Relevant bits of the config are below:

==> ~/.public-inbox/config <==
[publicinbox "rack-devel"]
	address = rack-devel@googlegroups.com
	url = //public-inbox.org/rack-devel
	mainrepo = /path/to/rack-devel.git
	newsgroup = inbox.comp.lang.ruby.rack.devel
	nntpmirror = nntp://news.gmane.org/gmane.comp.lang.ruby.rack.devel
	infourl = https://groups.google.com/group/rack-devel
	watch = maildir:/path/to/maildir/.INBOX.rack-devel
	watchheader = List-Id:<rack-devel.googlegroups.com>
	; bleh, I hate address obfuscation, but I guess some people are used to it :<
	obfuscate = true
	replyto = :list,Cc,To,Reply-To


(*) https://public-inbox.org/rack-devel/20160510-rack-devel-hopefully-mirrored@gmane/

                 reply	other threads:[~2017-06-29  0:40 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=20170629004042.GA5869@dcvr \
    --to=e@80x24.org \
    --cc=meta@public-inbox.org \
    --cc=rack-devel@googlegroups.com \
    /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).