It may please some of you to learn that I'm working on the NNTP server now.

It may please some of you to learn that I'm working on the NNTP server now.
begin Karen J. Cravensquotation from news:stakeholders.main.00000172@phoenyx.net: > It may please some of you to learn that I'm working on the NNTP server > now. It may please you even more to learn that that was posted from it.
On Wed, Jul 25, 2007 at 03:41:44AM +0000, Karen J.Cravens wrote: > It may please some of you to learn that I'm working on the NNTP server > now. Oooh! Me, me!
On Wed, 25 Jul 2007, Chuk Goodin wrote: CG>Oooh! Me, me! You can try connecting to it (nntp://roc.phoenyx.net:119/ or whatever the standard way of expressing an nntp url is) though I haven't been leaving it up when I'm not actively working on it (and it yoyos when I am). It's still very RFC-compliant, which means it doesn't work on most clients yet...
On Wed, Jul 25, 2007 at 03:50:21PM +0000, Karen Cravens wrote: > On Wed, 25 Jul 2007, Chuk Goodin wrote: > > CG>Oooh! Me, me! > > You can try connecting to it (nntp://roc.phoenyx.net:119/ or whatever the > standard way of expressing an nntp url is) though I haven't been leaving > it up when I'm not actively working on it (and it yoyos when I am). It's > still very RFC-compliant, which means it doesn't work on most clients > yet... I'm using trn -- I think we had some trouble last time.
On Wed, 25 Jul 2007, Chuk Goodin wrote: CG>I'm using trn -- I think we had some trouble last time. Yep, because wildmats are a problem, and because trn expects response codes to be significant past the numeric code (BAD BAD BAD BAD EVIL!) I just added support for such a response to "list active control", so you can try again.