From: agb001@acad.drake.edu
Subject: Re: BBS Development ideas.. Some thoughts..
Organization: Drake University, Des Moines, Iowa, USA
Date: Fri, 22 Jan 1993 16:25:11 GMT

In article <1993Jan22.101934.12535@exucom.com>, kjv@exucom.com (Karl J. Vesterling) writes:
> In article <1993Jan19.212134.1@acad3.alaska.edu> nsmca@acad3.alaska.edu writes:
>>Source Code available for right price to make modifications.
> 
> Ooooohh..  Now that spells trouble...  Eight million versions running
> around...  Nahh...  Just make it USER customisable.

Well, it seems to give variety. I mean without differences among BBSes, they 
would all look and feel the same. Even WITH User customizing. If it was slow
in some places, ALL would be slow. No thanks. Personally I like keeping my
BBS a little better than the other by rewriting the code with my own when I
can. 

> 
>>Doors (drivers?) for different game types.. Also maybe some graphics
>>interfaces..
> 
> Well, how about a terminal program that does the graphics, this
> reduces the ammount of traffic over the modem.  For instance, Falcon
> 3.0.  Needless to say, this is not possible to supply at a reasonable
> cost to the user...

JJust curious, but what type of computer MUST a person use to log into that
BBS. If they have the graphics in the Terminal program, then new terminal
programs must be written for ALL systems. I know. I call either from a
MacIntosh SE, an Amiga 1000, a Commodore 128, or a Commodore 64. Now who is
going to write these new terms? 

I disagree. It is MUCH easier on the user by letting the BBS have its own
graphics. That way a user not only can choose their own Terminal program, but
can also use any computer they want.

>>Move Around BBS Ease: ease to get from file area to doors area and 
>>then discussio areas..
> 
> Hmmmm...  How about something like ELM, and TIN on the UNIX side,
> along with something along those lines for the transfer section.

Actually, there is a BBS I call in St.Louis running MTABBS. It has the files IN
the message base. The messsage shows up with a little descriptor saying
"<Download>" and it is known that it is a download. Not only is that nicer in
that the actual description is a message in the BBS, but also the download can
be scrolled off and accesssed without having to jump around. There is also a
seperate set of commands to access the download areas, but the ability to have
it in messages is a GREAT asset.

>>Color? More than ANSI color, maybe some form of VR color.. 
> 
> VR Color?  No...  Make the terminal program do the color...  This
> tactic saves time..  Also build into the terminal program that when iy
> logs in that it checks it's version automaticly, and if it's out of
> date, it automaticly downloads the newer version.

See above in regards to terminals.

> 
>>Versions: Be able to run BBS on different Operating Systems or atleast have
>>different versions.. NAmely MSDOS, Apple/MAC, OS2, UNIX (main version?),
>>Amiga and ?..
> 
> Hmmmmm...  If you went with UNIX, you would have most of the stuff
> done already...  You'd have support for hundreds of different
> terminals, UUCP, and USENET...   Heck, even the multiple user stuff is
> built into it...  Go check out LINUX..  PD UNIX OS.

Yes, but each version of UNIX still has its own problems. What do you do if you
are running on a 512K Amiga and UNIX takes up 400K on its own. It think that a
simple set of code which can be transported would be much better. Then even
systems without cheap UNIXes (Sorry, I wouldn't want to pay $500 for A/UX then
have to pay $100 for the BBS program. No thanks) or UNIX equivalents. But also
at that same time, when transported, the systems can take advantage of the
differences between systems. (I.E. Graphical interfaces, Multitasking, or even
Built-In Battery Backedup Clocks.)

>>Host Mode? Maybe a way to dial out.. Also maybe a was to recognice the CIS(?)
>>(where the phone tells you what number is called..)
>>
> 
> ANI you mean..  Write a new "getty", and have a modem that's capable
> of it.


How about this... Just write it so that it makes use of Caller ID. Then you
could also put in features to block out Caller ID Blocked calls and the like.

> 
>>Terminual Emulation: atleast 5 different types.. ansi, VT52+, and a few
>>others.. to handle main terminal types.. maybe a 132 cpi emulation.
>>
> 
> Hmmm...  UNIX, and after they log into the machine, and the terminal
> has been determined, a simple:
> 
> eval `resize`
> 
> 	Should work just fine...
> 

But that's if it is on a UNIX. And again, it is a matter of what system it is
being run on.
             
>>
>>Any other suggestions?? Please post them here on alt.bbs or  suggest a better
>>place to post...
>>
> 
> Yes...  Get rid of MS-DOS & Windows Whoahs...  If you're going to run
> a BBS, run it on UNIX...  It solves a lot of problems...  The other
> problems that other people may bring up are irrellivent.  UNIX does
> automaticly in the OS what the BBS applications are attempting to do.
> 
>>
>>Anyone into a BBS development newsgroup.. 
> 
> Yes, very interested...
> 

Yes, I would be interested myself in such a newsgroup.

>>alt.bbs.develop or comp.bbs.develop  ??
>>
> 
> How about, "comp.unix.bbs"
> 

No thanks. Not my cup of tea. :) (Gawd, there's a scary thought. A C-64 running
Unix. :)


>>Michael Adams
>>Alias: Morgoth/Ghost Wheel 
>>nsmca@acad2.alaska.edu
> -------------------------------------------------------------------------------
> kjv@exucom.com				| I was better, but I got over it.
> Karl J. Vesterling			| On my door I have a sign;
> (716) 634-6550 Work			|	INTeL OUTSIDE!


ParaPsykotic (DSW)
Tony Bossaller
AGB001@acad.drake.edu