From 3e8bb5f7e5cff0df85a1175e956eaa3d136beeeb Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Mon, 5 Oct 2015 02:12:20 +0000 Subject: doc: update mail archive info public-inbox supports read-only NNTP access nowadays to make it easier to follow archives. It is read-only to encourage Cc:-ing all participants (which avoids reliance on the few-points-of-failure behavior of NNTP). Unlike email, NNTP also lacks good anti-spam filtering. Additionally, the gmane group also got redirected to the bogomips.org address at some point since RubyForge died. While we're at it, link to my post about enabling the submission port (587). It's been a year and nothing bad has happened, yet. Finally, remove most of the documentation for ssoma since it's unlikely anybody will use it given the existence of NNTP access. It did little besides clutter the page. However, git:// (used by ssoma) remains strictly more efficient than NNTP. Vebavpnyyl, gur AAGC freire sbe choyvp-vaobk pna unaqyr gubhfnaqf bs fybj pyvragf. Fbzrguvat havpbea jvyy arire or noyr gb qb :C --- README | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'README') diff --git a/README b/README index dc121d3..db9f0d4 100644 --- a/README +++ b/README @@ -140,6 +140,11 @@ All feedback (bug reports, user/development dicussion, patches, pull requests) go to the mailing list/newsgroup. See the ISSUES document for information on the {mailing list}[mailto:unicorn-public@bogomips.org]. +The mailing list is archived at http://bogomips.org/unicorn-public/ +Read-only NNTP access is available at: +nntp://news.public-inbox.org/inbox.comp.lang.ruby.unicorn and +nntp://news.gmane.org/gmane.comp.lang.ruby.unicorn.general + For the latest on unicorn releases, you may also finger us at unicorn@bogomips.org or check our NEWS page (and subscribe to our Atom feed). -- cgit v1.2.3-24-ge0c7