Xref: utzoo comp.unix.xenix:2367 comp.unix.questions:7341 comp.unix.wizards:9007 comp.unix.microport:755 Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!mandrill!hal!ncoast!allbery From: allbery@ncoast.UUCP (Brandon S. Allbery) Newsgroups: comp.unix.xenix,comp.unix.questions,comp.unix.wizards,comp.unix.microport Subject: Re: WRONG! Summary: obnoxious flames about BBS software Message-ID: <7842@ncoast.UUCP> Date: 31 May 88 21:50:46 GMT References: <208@turnkey.TCC.COM> Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery) Followup-To: poster Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 23 Sandy: I suspect that your "attacker" has got us confused -- although where he got a copy of UNaXcess 0.2 (aka UBBS) I'll never know, as it was ncoast internal and not available for distribution. I admit that some things are "block copied" (although file area maintenance was not, it started out as an external program and needs more than a simple "collapsing" of duplicate code to integrate). I've been cleaning them up steadily (you, no doubt, wondered where 1.1 is? That's where -- that, and a badly needed linting), and 1.1 will be modular. "Non-standard file formats": some people praise me for using MH-style messages, some flame me for it. I'm sticking with separate ASCII files. You just have to expect flames from someone. (I expect I'll get MASSIVELY flamed when 1.2 converts all the ASCII control files to hashed binary.) Make your own choice -- and if someone else doesn't like those choices, they can bloody well write their *own* BBS! Yours in BBS authorship, ++Brandon -- Brandon S. Allbery, moderator of comp.sources.misc {well!hoptoad,uunet!marque,cbosgd,sun!mandrill}!ncoast!allbery Delphi: ALLBERY MCI Mail: BALLBERY