unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: mongrel-unicorn@rubyforge.org
Cc: unicorn-public@bogomips.org
Subject: Re: [ANN] public-inbox - "archives first" approach to mailing lists
Date: Sun, 4 May 2014 07:42:51 +0000	[thread overview]
Message-ID: <20140504074251.GA28038@dcvr.yhbt.net> (raw)
In-Reply-To: <20140421183728.GA27047@dcvr.yhbt.net>

Eric Wong <normalperson@yhbt.net> wrote:
> Feedback comments/greatly appreciated: http://public-inbox.org/

We only have a few days left before this list goes away.

> If needed, there'll be an SMTP replayer to do push delivery like a
> normal mailing list, but anybody may also run the delivery-only
> service, too.

I'm still not sure if I want to run one; if I did, I might would take
the drastic step of making the subscribers list public so anybody may
takeover the distribution list[1].

Right now only I (and Rubyforge admins) have access to the subscribers
list on RubyForge, (but I hate website logins, so I never look at it
:P).  I don't feel like anybody should have the exclusive privilege of
knowing who subscribes to a list.

I may also run a read-only NNTP server (not sure how to enforce
a Cc:-all workflow if posting were allowed).

> AFAIK, we don't have many ML subscribers anyways, and VERP seems
> reasonable...

I do get a lot of rubyforge bounce messages from spam bots attempting to
subscribe (and I think some of them succeed, even).  So maybe attempting
to do SMTP delivery isn't worth it with public-inbox...


[1] Obviously I know it'd be easy for spammers to harvest lurker
    this way, but they already harvest addresses from every poster.
    I suspect most folks on ML have decent spam filters these days.
    (and if you don't, I use and recommend SpamAssassin)

  parent reply	other threads:[~2014-05-04  7:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21 18:37 [ANN] public-inbox - "archives first" approach to mailing lists Eric Wong
2014-04-21 19:07 ` Eric Wong
2014-05-04  7:42 ` Eric Wong [this message]
2014-05-04  7:47   ` Eric Wong

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://yhbt.net/unicorn/

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

  git send-email \
    --in-reply-to=20140504074251.GA28038@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=mongrel-unicorn@rubyforge.org \
    --cc=unicorn-public@bogomips.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://yhbt.net/unicorn.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).