Overall, I really think that it was best summarized in the line about "keeping the art alive."
The BBS is a dead concept, almost completely. It's replaced, appropriately, by either using separate tools on UNIX systems (gopher, IRC, locally delivered mail and lists) or with new software that uses the capabilities of modern computers (graphics and new networking protocols and easier access to TCP/IP in the 1990s, and the web here in the 2000s) to make communication with others easier for more people.
Aside from serving as a platform for people who have specific nostalgia for them, I personally don't see a reason to run a BBS. (I even have a writer group full of people who have specified that they'd be interested if I wanted to run something wild for our group's communication, and the craziest I'm willing to go is giving them accounts on my own Windows domain, which I don't even see a reason to do, because there really are better ways for our group to communicate, especially if we should ever pick up any members who aren't comfortable on a text-commands console of some sort.
Pablo Draw is interesting for ASCII art purposes though, and what I'd advise is that it's worth not confusing "ASCII art" with "BBS" -- BBSs often carried ascii art, but that's by no means the only place it can exist, so while it's neat to see that there's software specifically designed to create it, I don't know if I'd consider it strictly relevant here, just because the whole point of this conversation seems to be justifying BBSes.
Not that you shouldn't run your BBS, just that I don't think they'll ever get more popular than they are today. Web sites have mass appeal, and if you wanted to cater to the Linux or Unix crowd, I don't think that a monolithic piece of software storing all of its information in a database that was meant to be dialed into by home computers is necessarily the best way to appeal to that crowd, which prefers small single-purpose binaries, pipes, and text files.
Excuse me, but I think that you are a little confused in your facts.
First of all, PC-ANSI-based Macintosh BBS packages PRECEDED by years First Class, Telefinder, Hotline and other iterations of the graphic-oriented BBS.
Second, I don't think that it is wise for you to speak for Macintosh users as a whole. Someone is bound to take offense if your opinion differs from their own.
Third, if there was no interest in running Macintosh versions of PC-ANSI based BBSes, then popular BBS packages such as Hermes II, Public Address, MacCitadel, Mansion and Starbase7 would have never been written. Yet they were written.
It's moderately possible that the ANSI BBS packages for Macs were 1) ports from other platforms (such as maccitadel in particular) and that they existed before other enabling technologies (such as PPP, from 1994) enabled better solutions.
How many of those packages were updated on the Mac after Hotline et al shipped with graphical interfaces for the Mac?
There's interested in that software, but very little of it is on the Mac, especially these days when there are much more Mac-like solutions available, and when most of the problems previously solved by BBSs are now solved by other groupware solutions, most of which are either integrated with phones and proper Internet e-mail, or are a web application.
ANSI BBSs are a very technical solution to a problem that now has a much easier solution, and for that reason are doomed to either only being used by very specific people, or in "retrocomputing" contexts.
I'd say that the ANSI BBSes that existed for Macs in the early days was one of those anomalies that often happens on the Mac simply because technology isn't at a certain place yet.
I assume SharePoint sort of takes over this in the corporate world.
Exchange, Lync, and SharePoint are essentially the corporate/institutional productivity holy grail, and they together do a lot of things you might expect a BBS or an older integrated communication solution (profs, notes, firstclass, etc.)
To be honest, they're better tools than a BBS. They're not the only tools, but they are very popular, and one of the things Microsoft is trying to get even more into is using Lync as an IP-PBX, to integrate voice and video to make the whole thing a Unified Communications solution, but that's pretty tangential.
Another thing they do that most BBSes and even a lot of other groupware solutions don't is that SharePoint document libraries are a document storage and versioning system. It's essentially svn/git/mercurial but for Office documents, implemented as a web interface with WEBDAV and usable by people who odn't specifically care about computers.
The big question, in my view, is this: How many Macintosh-based BBS packages are still being developed and updated on a regular or semi-regular basis, and how many are being used by a large number of people?
I think answering this three-part question really tells the tale regarding Macintosh BBSing.
And, what's the answer? Do you know it or are we speculating or is this a recommended research project?
1) Hermes was last updated in 1999. It's more recently than Citadel for Mac, which is still being updated for Linux, and seems to focus on being open source and group collaboration, essentially it's trying to be a competitor to the communications functions in Exchange/SharePoint/Lync. (Next up: it'll be the default webmail client and group calendaring solution in Zentyal. The project site is very confident in its ability to replace SharePoint and Exchange, but they've arranged the functionality in a different way and it doesn't have all the functionality of either, so they're definitely relying on somebody having bought and then pretty massively under-utilized both of those things.)
2) Widely used by people who have a specific interest in BBSes, and widely used by "regular people" are different things, and these days, BBS software is widely used by people who have a specific interest in BBSes and that particular aspect of retrocomputing. Even Google Groups isn't very popular in the face of much more modern solutions such as facebook, discourse, and other web applications.
3) I only see two parts to this three part question.