tinyfeed miniature transit server

[Russ Allbery]

Forrest J Cavalier <mibsoft at epix.net> writes:

> I say including it in INN would be very confusing.  (libinn is getting
> to be pretty useful, so maybe it should be split off to encourage more
> NNTP development like this though.)

Confusing just becasue of the name or for some other reason?

I agree with you that in general it would be better as a separate package,
and libinn would probably be better as a separately distributed library
that's also included with INN, but that really would require finishing
stabilizing the API first.  I don't want to make *any* promises about the
current contents of libinn; there are still vast swaths of it that I want
to delete.

I do promise to break this off into a separate distribution when we reach
the point that it's reasonable to tell people to install libinn and then
this; that's just more work than I want to devote to this little thing at
the moment.  (It's been off running happily for over a year now, handling
all of the ftp.isc.org archives.)

> If you do include tinyfeed, could the name be changed and the first few
> paragraphs of the description improved?

Suggestions?  It was called tinynntpd, and I figured that would be even
more confusing.  I'm at a loss for the best name for it.  tinyihaved?

> From the name I thought it was a innfeed replacement, and it took me
> three paragraphs through the documentation to determine it accepted
> news.  (I know inetd accepts connections but "feed" and "server"
> generally mean you are a source of data, not a sink.)

I'm not sure how to reword it; I'll give it a try, but more suggestions
would be welcome.

> And just to tease you a bit....Hard-coded size limits are so 80's.

Yeah, I just haven't gotten around to adding a few command-line options to
it yet.  (I want it to not require inn.conf.)

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.