home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky alt.bbs:8189 alt.bbs.allsysop:954
- Newsgroups: alt.bbs,alt.bbs.allsysop
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!rpi!usenet.coe.montana.edu!news.u.washington.edu!henson!n8948315
- From: n8948315@henson.cc.wwu.edu (Arthur Morgan)
- Subject: Re: BBS Development ideas.. Some thoughts..
- Message-ID: <1993Jan25.215638.24177@henson.cc.wwu.edu>
- Organization: Western Washington University
- References: <1993Jan22.101934.12535@exucom.com> <1993Jan22.102511.1@acad.drake.edu> <1993Jan23.150727.8050@globv1.hacktic.nl>
- Date: Mon, 25 Jan 1993 21:56:38 GMT
- Lines: 20
-
- In article <1993Jan23.150727.8050@globv1.hacktic.nl> peter@globv1.hacktic.nl (Peter Busser) writes:
- >agb001@acad.drake.edu writes:
- >
- >>> 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....
- >
- >That is the same strategy that Magpie follows, no file areas, only attaches
- >and I like that. TBBS also has some kind of attaches, but it has file areas.
- >There are more systems that support file attaches to messages.
- >
- I run a Citadel, and it has a system kind of in between. A given echo/forum/
- room can be set up with a pointer to a directory. You can access the given
- directory for purposes of reading and/or writing from that room. Different
- rooms have different directories attached to them, yielding the different file
- areas on the system. A given directory will have a purpose and content similar
- --
- Arthur Morgan <n8948315@henson.cc.wwu.edu>
-