New Releases – July 2024

It’s been a little bit too long, but hey, Demonic Productions is back with a slew of new releases!

Reading a test news message with Hinews 0.2

First off, esc is in the midst of another bout of hyper-focusing on Daydream/Linux. Not only does that mean impending updates to Daydream itself, but it also means more mods! Continuing the theme of his last several Daydream releases, he’s taken some of his favorite old, but now totally broken Daydream mods and utilities by other authors and got them working again, along with bug fixes and other updates. As usual, these all include some sick oldschool ASCII artwork and their complete source code:

  • dd_listmsgs v1.0.3 – originally by Niels Haedecke, this is a simple message lister door.
  • ddtext v1 – originally by 2mad^Gilden and later pandur, ddtext is a nice little TUI based utility for editing your Daydream strings files.
  • Hinews v0.2 – originally by Rezine/Drunken, Hinews is a news bulletin door that will only show new/unviewed bulletins to each user. Throw it in your login process!
  • Last 100 ULS Grouped v1.2 – originally by flOwer/project deedee, this door displays a sorted/grouped list of the last 100 uploads.

Additionally, esc has put together a quick guide on how to build and configure a 32-bit Windows 7 VPN on DigitalOcean. A handy answer to those questions that often come up regarding how to started with remotely hosting a BBS using Windows.

Moving on to my (Jack Phlash) own stuff, literally the day after releasing REFDoor v1.3, I started working to provide a more complete example of how REFDoor could be used to create an e-mag. The @SHOW SCROLL function is pretty much all you need, and the WHATSNEW.REF file included with REFDoor and “The Bloody Claw Newsletter” included in RTREAD02.ZIP get you a lot of the way there. Still, I wanted to build an approximation of an actual, full-fledged take on a traditional e-mag. Given my involvement with Gutter and that Natedogg and I released the full source code to one of the issues previously with Demonic, including all of the raw data I’d need, that was the most logical and, honestly, easiest place to start. What I’m calling Gutter #11 REF Edition includes this original version in “G11RV1.ZIP” which also comes with some more detailed notes on what it took to do the conversion.

Reading Gutter #11 via REFDoor!

While I think the results are passable, I did encounter some issues that made the conversation a little less ideal than I’d imagined. That’s where REFDoor 1.4.1 comes in. It includes a lot of miscellaneous additions and changes, but practically all of them related to my work on this script. Here’s the whole whatsnew.txt:

v1.4.1 - Released 7/15/24 (A few minor fixes for 1.4.0)
---
 ! Greatly reduced the artificial delay experienced when using the escape key
   via any single key input routines (such as DO GETKEY, LIGHTBAR, CHOICE,
   etc.) This delay was added in order to properly trap ANSI style arrow key
   codes (which of course, start with an escape character.) The delay should
   now be much less noticeable and will still HOPEFULLY sufficient to work with
   arrow keys, even over slow dial-up connections.
 ! Fixed WHATSNEW.TXT to remove various "O" SethCode references, which totally
   broke the hell out of the included WHATSNEW.REF demonstration script as they
   would inadvertently turn code parsing back on, leaving it on when scrolling
   down just a bit more and encountering the note about `^ stripping, which
   would then turn all of the foreground text black for the rest of the file,
   making it appear as if the text wasn't being rendered properly. Doh!
 ! Script variables will now be re-initialized every time a new script is
   launched from the REF picker menu. This is more in line with how RTReader
   works and, well, how you'd think it would work. Not re-initializing
   variables between launching scripts could otherwise cause some bizarre or
   at least unexpected results. Note that variables are still maintained
   when launching scripts using ROUTINE or RUN, as before.

 v1.4.0 - Unreleased (Gutter #11 related fixes and changes.)
---
 ! Fixed the way REFDoor appends .REF to filenames from the command line.
   Previously, any filename that didn't include ".REF" would have the extension
   appended, which caused the unintended behavior of REF scripts with different
   extensions (i.e. ".LIB") to be appended with an additional extension. Now
   it will only append .REF to any filename without an extension. This also
   impacts other commands which call new scripts such as "ROUTINE" and "RUN".
 + Minor logging addition to log the filesize of a script when in memory mode
   with verbose logging enabled. This should make it easier to troubleshoot
   not enough memory errors when using memory mode with REFD16.EXE.
 + Added new command "ESCCHOICE [option]" which can set how the ESC key behaves
   by default when using the "CHOICE" and "LIGHTBAR" commands. If set to 0, ESC
   acts the same as ENTER, just like in previous versions. If set to a valid
   option, it will default to that. If set to an invalid option, it simply does
   nothing. This is mainly intended for scripts that are heavily reliant on
   lightbar menus in which case escape might be used to quickly back out of
   multiple submenus, and defaulting to enter instead breaks desired flow.
 + Added new command "DISPLAYSPEED  [delay]" which can be used to slow
   down the display of the "DISPLAY" and "DISPLAYFILE" commands in order to
   output ANSI at rates approximating modem baud rates. A parameter of 0 is
   default/best effort, while 1-255 are valid speeds, with 1 being the slowest.
   What the speed ACTUALLY represents is how many characters to display before
   delaying. The default delay is 1ms, but the optional delay parameter allows
   you to raise that up to 255ms (which is about a quarter of a second.) Used
   in conjunction, for instance, with speed set to 1 and delay 255, you can
   slow your display to an absolute crawl. Unfortunately because this relies
   on how fast the ANSI is parsed, the speed of the two display commands is
   *highly* dependent on the performance of the system they're executing on and
   the build itself, with REF16.EXE tending to far out perform REFD32.EXE. For
   instance, on my system using the REFD32.EXE, a speed resembling 57600 bps is
   "75" while using REFD16.EXE, it's closer to "7". Quite a difference! That
   said, I highly suspect this varies wildly. For that reason, I'd recommend
   assigning the speed to an easy to change variable in any scripts you
   distribute that rely on this command so SysOps can easily tweak it as
   desired. Note: Avoid using NOSKIP when combined with slow speeds and long
   ANSIs, unless you hate your users.
 ! "DISPLAY" now only stops when a new section ("@#") is encountered. Prior to
   this fix, REFDoor would treat ANY "@" encountered as the end of the section,
   which was not only inaccurate to how RTReader behaved, but would also cause
   headaches when trying to display files with legitimate uses of the @
   character (Internet email addresses being an obvious example.)
 ! Fixed a bug in "KEY" and "PAUSE" where the cursor was moved back to column 1
   after the prompt had been erased. This was NOT accurate to RTReader's
   behavior, which would move it back to its original location. This was likely
   rarely encountered since "SHOW" is the main form of output used in REF and
   always writes an entire line at a time, but could cause some issues with "DO
   WRITE" and "PRINT".
 + Added the new "O" SethCode style display code which allows you to toggle
   parsing of control codes on and off dynamically. This is not a global
   setting, and is reset after the calling command has completed. Furthermore,
   this functionality is only supported by specific commands:
      * "DISPLAY" and "DISPLAYFILE" - O will affect parsing of display codes.
        Control codes parsed when read will not be affected, as they are not
        normally parsed by these commands. As with other display codes, O will
        take effect as soon as the code in encountered. Also, note that O
        interacts with the NOCODE parameter added in REFDoor 1.3. For example,
        if O is found in a file that is being displayed with NOCODE, it will
        re-enable code parsing.
      * "SHOW" and "SHOW SCROLL" - O will affect parsing of all codes, although
        control codes parsed when read are only affected on a line by line
        rather than a character by character basis. In other words, if you
        disable parsing, non-display codes will still be parsed until the next
        line of text is processed. As with "DISPLAY" and "DISPLAYFILE", O
        interacts with "SHOW SCROLL"'s implementation of the NOCODE parameter.
      * "DO WRITE" "PRINT" and "CENTER" - O will affect parsing of display
        codes. While technically capable of disabling non-display codes as
        well, since these codes are parsed on a line by line basis, and each of
        these commands only outputs a single line of code, this will have no
        effect. The good news is that it's unlikely that parsing non-display
        codes will cause display problems as only VALID codes are removed,
        unlike when display codes are parsed.
   This new code should be stripped as normal by various internal functions and
   commands (i.e. "STRIPBAD") that strip SethCodes.
 ! Fixed a bug where SethCode `^ was missing from STRIPBAD which could have
   caused it to be accidentally stripped.
 + "SHOW SCROLL" (in either mode) will now support lines of text with a
   theoretically unlimited length. Of course, "SHOW SCROLL" generally assumes
   that the text is more or less preformatted, so you should still keep your
   text less than 80 columns wide for the best results. This is AFTER parsing,
   however, which means that complex ANSIs (which can include lines that are
   many hundreds of characters long) should now render properly, which was
   the entire point of this fix, actually. Woot!

   Note: For best results, ANSIs should not include long lines stored as a
   single line that wraps on the 80th column down to multiple lines. While
   these will render fine themselves, they break the rendering of the "SHOW
   SCROLL" routine because of improper calculation of the number of lines and
   pages. The easiest way to avoid this is the old tried and true method of
   erasing/deleting text on the 80th column, which should cause most ANSI
   editors to place each new line on a separate line in the file.
 * In relation to the above "SHOW SCROLL" changes, temporary files created when
   calling "SHOW SCROLL" without providing an external file name will be
   converted to a format that includes full line length, but only if long lines
   are detected. This conversion process is a little kludgy due to otherwise
   needing to majorly rewrite parts of the main parser to implement, so it
   isn't extremely efficient right now, and a delay may be noticeable when
   running this on older machines. Worth the trade-off for full ANSI support in
   "SHOW SCROLL", IMHO.
 * Note: The normal "SHOW" command doesn't support lines longer than 255
   characters, but ANSIs saved with a 255 or less line length will render fine
   since, unlike "SHOW SCROLL", the cursor up ANSI codes (ESC[xA) typically
   used by ANSI editors to compensate for splitting lines) will not interfere
   with rendering when scrolling. "DISPLAY" and "DISPLAYFILE" (which do support
   long line lengths) can also be used as alternatives.
 ! Fixed an issue with the way I was patching CRT for the infamous RTE200 issue
   in REFD16.EXE - the fixed "delay" routine didn't seem to always work
   properly, sometimes causing inaccurate timing when using the "DELAY" command
   and so much other stuff.
 ! Fixed a very rare issue with "DISPLAY" which could cause REFDoor to get
   stuck in an infinite loop trying to find a header *if* the header happened
   to be cutoff by the end of the buffer I use for these searches. This should
   be extremely rare, but now if it is encountered, REFDoor will fallback to
   doing a partial search for the header, which should hopefully be adequate
   most of the time. If you run into issues with "DISPLAY" not finding your
   headers or causing other issues, try using /V to look for the log message
   that indicates this issue. Moving things around in your script (even just
   adding an extra blank line) is often enough to workaround the buffer issue.
 ! Fixed a longstanding (though likely rarely encountered) issue with the way
   that the "SHOW SCROLL" routine (in both normal and memory mode) would
   calculate the number of pages, occasionally resulting in a last page that
   was entirely blank. Not a huge deal, but this has annoyed me for quite a
   while now.

Gutter #11 REF Edition also includes a version 2 in “G11RV2.ZIP” which has been updated to take advantage of the fixes and additions in REFDoor 1.4, as well as some other changes (like fixing all of the ANSIs to display properly in NetRunner.) Naturally, v2 is the superior version of the script, but of course requires REFDoor 1.4 and, honestly, I thought including both made for a more interesting release all around.

That’s it for now. Stay tuned for more, and I think we’re overdue for another one of those wacky Demonic NFO files. I’m not sure when I’ll get around to it, but expect at least one this year!

Zer0net 2024 Changes

A lot of these details only pertain to Zer0net node SysOps, however a huge part of this announcement is extremely relevant to any perspective new nodes, and none of it is anything in any way sensitive, so I’m posting this for all to read.

Zer0net font by Jack Phlash

It will be no surprise to many of you to read that I’ve been tossing around a lot of ideas about how to overhaul or otherwise update Zer0net for a couple of years now. We’ve had some interesting ideas, like shifting to a highly moderated structure and even focusing on new/different themes. In the end, I feel that Zer0net should stay true to, and in fact embrace, its identity as a network that values free speech even if that means taking the bad along with the good when it comes to open conversation, and staying true to our underground BBS scene aligned roots, and instead of changing the conversation, focus on having more of it. With that in mind, here’s what is changing with Zer0net in 2024, which, by the way, marks the network’s 25th birthday!

  • Paulie420 of 2o fOr beeRS will be joining me as the co-admin of Zer0net. I’ve greatly always appreciated help from others, and while Zer0net isn’t exactly a democracy, more often than not I poll our node operators for feedback on changes and other concerns about the network, and even work with some of them quite closely. While that won’t be changing, I believe that having another person, especially one with a different background, different values, and a different personality than me helping officially steer things can only be a good thing for the network’s future.

    Paulie will be highly involved with recruiting new nodes, reviewing applications, and otherwise working with prospective new members. He already does a lot of work helping and mentoring other SysOps, and generally trying to be involved in the whole BBS scene community, so this is a natural fit for him, and it’s especially important given a change detailed in a couple more paragraphs. The apply AT zer0net.org address we currently have in our documentation is still the best way to apply for the moment, and it will forward to him as well as me now.

    Also because he doesn’t pimp it nearly enough, and it’s pertinent to the interests of the readers of this blog, here’s his YouTube channel!

  • Esc AKA Ryan of Monterey and maintainer of the Daydream BBS software will also be officially joining the network’s staff. Of those Zer0net node operators I mentioned above, I’ve probably leaned most heavily on my friend Esc for many years now. He’s also joined me as one of the members of the relaunched Demonic Productions in 2022. Overall, he’s been one of the network’s most steadfast contributors for quite some time, and I wanted to recognize that. Speaking of both things, he runs Demonic’s small, private Discord server, and we have a Zer0net channel if any SysOps or frequent posters would like to join – just ask!
  • Zer0net has been opened up, and acceptance criteria has been loosened considerably. Ultimately, most of us are members of echo mail networks in order to be able to participate in more active conversations with a wider variety of people than just what is happening in our local message bases with our local users, even those of us lucky enough to have very active local message areas. Having an “elite” membership when (more times than not) we have very little active conversation, seems a bit self-defeating.

    Additionally, we’ve rejected quite a few boards that haven’t met our criteria over the years, but since one of the possible acceptance criteria is a lot of message activity, if those boards are relatively new, or the SysOp themselves is one of the most active posters, as is often the case, they never really get a chance to prove themselves before being rejected. While it has regrettably sometimes been taken this way, our mission here has never been to snub or otherwise discourage new SysOps, so this change should also help to address this issue.

    That said, we still want serious SysOps who are going to be around more than a month or two, and we still want nodes who will actually add something to the network rather than membership just being one more thing they can list on their advertisements. And uh, yeah, we’re still going to be pretty damn judgemental of totally stock boards. Sorry, we can’t help ourselves on that one! 🙂

    In the spirit of the old system, Zer0net will have two classes of member nodes:

    1. Elite status nodes are boards that meet our original criteria: great artwork and/or modifications, with an underground feel, notable affiliations and/or staff, a lot of activity in form of posts and/or other contributions, etc. All current and legacy nodes will be grandfathered in as elite status boards. Elite status boards do not need to meet any sort of minimal activity level, and can come and go as they wish, just as today.
    2. Normal status nodes are boards that do not necessarily meet the old, more strict criteria but we’ve decided to accept regardless. They must maintain a minimal level of activity (that is, we want to see new posts originating from the node!) We’ll do a quarterly or bi-yearly review of activity and any normal board who has not been active will be put into probationary status. The SysOp will be notified and if that status hasn’t changed by the next review, they’ll be removed.

    Normal status boards can be promoted to elite status. If they’ve proven themselves to have been highly active or otherwise grown to meet our original criteria. SysOps can ask for us to review their nodes for this, but more often than not we’ll proactively reach out to them if we feel they’ve earned a change in status.

    I’m not exactly expecting the floodgates to open, as it were, but then we have rejected a lot of nodes over the years, and I’ve told quite a few to hold off on their applications until these changes are finally implemented in the last year or so, so who knows!?

  • Echo housekeeping! In with the old and out with the slightly less old?

    It’s been quite a while since we’ve done this, so as a quick reminder of the point of this type of thing, like a fine dining restaurant with a small, focused menu, I strongly believe that less is more when it comes to message areas. That is, I’d rather have a small list of echos with broader topics, each with at least some activity, than have dozens upon dozens of echos dedicated to more specific topics, the majority of them entirely dead.

    1. This one is a long time coming. We’ll be removing the 0N-INFO and 0N-NEWS echos which have been around since the very beginning. Both echos have grown to feel redundant to me over the years, as most posts about the network’s administration will go into 0N-SYSOP anyway, and anything else more often than not winds up in our general discussion echo, 0N-CHAT.
    2. Similarly, we’ll be merging 0N-ANARC, 0N-HACKN, and 0N-PHRKN into the all encompassing new echo 0N-HPCAV. On paper, these echos have always been some of my favorites since the network started, but in reality these are seldom used as there simply isn’t as much crossover between the retro BBS scene and this stuff as I imagined. That was even true in the late 90s, as multiple BBS related underground disciplines had long been diverging into their own distinct scenes. Even when we do have users who want to go in depth on some of these topics, I’d imagine many of them don’t feel that an FTN network is the most secure place to do so. Still, Zer0net will always be aligned with the underground, and that’s not changing. At the very least, news related to security events always make for fun discussion.
    3. We’ll be adding a new echo, 0N-RETRO related to all things retro-computing. This one might ALSO feel redundant, but while BBSing in 2024 is undeniably “retro”, what most of us have been doing in the BBS scene is just an extension of what we were doing back in the dial-up days. The huge boom in retro-computing in the last 5+ years feels entirely distinct, with a lot more people, both in the scene and outside of the scene, taking an interest in vintage hardware and software, including jumping into the world of BBSing. A great number of us here are into retro computing and/or gaming to some degree, including myself, Paulie, and Esc, so I’m confident that this can be a place for some good conversations. As with our other echos, the actual intention of this echo will be a bit broader than that, with any conversations about vintage OR retro-targeted hardware, alternative OSes, software, games, emulation, etc. all being appropriate.
    4. With the aforementioned low-key rebirth of Demonic Productions back in 2022, we had previously added two new echos, 0N-DPUB and 0N-DPRI. 0N-DPUB is for public discussions and release announcements regarding Demonic Productions releases and related topics, while 0N-DPRI is, as the name might suggest, a private echo for Demonic members only, and because it requires special permissions, is not included in the echo list. Still, I’d love for anyone who hasn’t added it to make sure 0N-DPUB has been added to their boards.

  • File Fun!

    First, for those of you who care way too much about this sort of thing, I will endeavor to start doing a better job updating our nodelist file and infopack more or less in real-time as we add and remove nodes. I’ve already automated this process somewhat, including publishing them to Zer0net’s website for those of you who’d like to automate updates via wget (or whatever.) The biggest component of this, however, is that we’ll finally be adding a small number of file echos to the network:

    • 0N-NODEL – This will contain the latest Zer0net uncompressed nodelist file auto-hatched using the same filename every time, which should make it very easy for individual nodes to automate consuming them.
    • 0N-INFOP – This will contain the latest, most up to date version of the Zer0net infopack, again, using the same filename, always available to reference, distribute, etc. As with the last revision in 2020, this includes a variety of documentation regarding the network, some information and useful files for its setup, and some awesome artwork that you can use to give your system look as cool as it surely is if it’s a member of Zer0net.
    • 0N-DMNIC – New Demonic Productions releases will be hatched in this echo as they’re released. Speaking of which, we’ll have a new batch of releases very soon!

    Initially, no one will be linked to these new file echos by default, as previously our nodes were not configured with TIC passwords or other configuration needed to support file tossing. While I have made these changes on the hub side I don’t want to make any assumptions about your configurations, nor do I want to spam you with .TIC files and junk files you don’t want. Please use FileFix via a netmail to 911:1423/0 to add any desired echos when/if you’re ready to start receiving file hatches. Initially, your TIC password will be the same as those used for PKTs, AreaFix, or if you had nothing but defaults for those, BinkP.

  • There’s a lot of changes here, and given that some of our legacy nodes are more or less on autopilot, I won’t be nuking any of these old echos immediately. Instead, you’ll have until August 1st, 2024 to make any of the appropriate changes. A whole month! That said, these new message echos and file echos will be available immediately. Given all of these changes, there is a new major revision of our infopack (including an updated nodelist) coming… now! Yep, it’s released as of the posting of this announcement. Go grab it!

TL;DR version: Expect to see much more Paulie420 around. We have a Discord server! Expect to see a lot more new nodes and hopefully more posts, but this should not impact existing nodes. A new infopack is out! Please remove 0N-INFO, 0N-NEWS, 0N-ANARC, 0N-HACKN, and 0N-PHRKN from your configurations and add 0N-HPCAV and 0N-RETRO (and 0N-DPUB if you haven’t already done so.) Oh, and please fix that shit by August! If you’d like to receive file hatches of network nodelists, infopacks, and/or Demonic Productions releases, please configure your system to support TIC processing, add the new file echos 0N-NODEL, 0N-INFOP, and/or 0N-DMNIC, and link them via FileFix. Later!

Hawk Hubbard

This is an edited version of a spur of the moment message I posted to Zer0net the day I found out, updated and posted here for posterity.

By now, most of the people reading have already seen the news, or at the very least, knew that Hawk had been struggling with both heart issues and liver cancer for some time now. If not, I wanted to pass on the very sad news that on June 27th, the legendary Brian “Hawk” Hubbard passed on. I didn’t know Hawk as well as many people in the BBS and particularly art scenes did, so forgive me for not being able to write a legitimate eulogy, but I still feel compelled to say more.

A Toast to The Captain by Misfit and Ungenannt

Hawk, better known to most in the BBS scene back then as “Captain Hood“, and I crossed paths quite a few times in the late 90s and early 2000s. I recall email exchanges in which he wanted help setting up his own echomail network, locating some old esoteric Illness releases, that kind of thing. We always had a friendly, mutually respectful relationship, though it was always pretty casual so I can’t say he and I ever got to know each other well. He was, as I mentioned, already a bit of a legend by then; an absolute fixture in scene IRC channels like #acid, and his name was constantly popping up in group member and distro lists, greets on ANSI and ASCIIs, and in zines and e-mags for as long as I can remember, and truthfully, I don’t expect that to change even now.

Hawk was an ardent supporter of the scene, often encouraging and complimenting artists and supporting art groups, and in the post 2000s scene he was almost always in the mix of whatever new and exciting group or other project was in the works. I believe he was actually quite instrumental in making sure the BBS and art scenes, which had been diverging since the 1990s, remained undeniably linked. He was a (if not the) dude who artists loved to draw for (I mean, who else has multiple tribute pieces like the ones shown here?!) yet his involvement had always centered around his BBSes. This seemed to be the case even in the 1990s, looking at all of the amazing art he’d gathered and how many different affils his board had even back then. In the post 2000s scene, however, this got some of the top tier ANSI artists, who largely stopped taking requests or otherwise drawing more utilitarian art, to draw for ACTUAL BBSes again, which I’m sure also rippled out to influencing other artists to do pieces for other boards too.

Outside of the art scene, Hawk is known by many today for his impressive fleet (or armada, as he called it) of BBSes. He had multiple different systems over the years, each completely decked out with themed ANSIs and ASCIIs, including sick Oblivion/2 and PCBoard setups, and a RIPscrip focused Searchlight system. I remember calling the original Piranha when he first put it up on telnet full-time (and possibly earlier via dial-up, though my memory is a bit hazy there) and recall being absolutely floored by all of the amazing art he’d gathered and the modding he’d done. He later gained a bit of much deserved notoriety outside of the scene after 2013 when he launched Piranha: Under the Black Flag (AKA, just “Black Flag“) which was timed perfectly to gain notice from the growing retro computing scene, with Black Flag often showing up in various articles with lists of “must call” telnet BBSes. Black Flag was frequently at the #1 spot.

Piranha RIP by Satanic Sly

It was after a relaunch of the original Piranha around 2011 that Hawk joined Zer0net. With countless chats that usually started with troubleshooting or otherwise tweaking his echomail setups, this is when Hawk and I got to know each other a bit better. I’m proud to say that just about every system in Hawk’s mighty armada was also a member of Zer0net at one time or another. In fact, as I write this, his boards still occupy a ridiculous 4 slots in our node list! 😅

I should also definitely mention that all 4 of those BBSes that Hawk still had up (the aforementioned Piranha and Black Flag, plus Acid Underworld and The Black Tower) actually remain up, and hopefully will remain up in memorial to Hawk for quite sometime, as Hawk had moved away from hosting his BBSes locally with the help of Slime City BBS SysOp m00p. While it won’t be quite the same to call one of his BBSes without an extremely good chance of having Hawk break into chat with you, I think the whole scene is happy to know that his BBSes aren’t going to just unceremoniously disappear. Thanks m00p!

The Fiddler - Under the Black Flag by Whazzit

Of course, there’s a whole lot more to Hawk than I can really go into, most notably his life as a fiddle player and member of various bands, and all of the travels and other adventures he had around those times. Smooth actually created an echo on Araknet called “True Adventures” exclusively for Hawk to share all of those wild stories and otherwise wax philosophical about life. I only wish he used it more, as some of the few stories he had posted there and elsewhere were pretty damn incredible.

Likewise, I wish I knew more about Hawk and his history with the scene. How in the hell did he go from a fiddle player in Indiana to the SysOp of one of the sickest BBSes in Florida? I’d love to know more about how he first got into computers, his early days as a BBSer, and how he wound up being associated with the underground scene, and particularly ACiD Productions. As I mentioned briefly back in my 2022 update post, I’d been planning to do sort of mini-BBS reviews, complete with interviews with SysOps for this blog, and still hope to someday, but I’d always intended for Hawk and his fleet of awesome BBSes to be my first subject. Hawk and I talked a bit about it early last year, and when I first heard about him getting sick back in January, I scrambled to put together a lengthy Q&A style interview for him to work on whenever he felt up to it. He definitely seemed into the idea, but no doubt had much higher priorities in the months since, and I’m sure his energy was sapped much of the time from fighting the good fight on top of that. The truth is, he certainly didn’t need my help being immortalized in the scene!

Rest in Peace, Captain! You will not be forgotten.


1. we-a_toast_to_the_captain.ans by Misfit and Ungenannt from Blocktronics Acid Trip (2013)
2. ss-pira!.rip by Satanic Sly from CiA #37 (1996)
3. wz – the fiddler – under the black flag.ans by Whazzit from Blocktronics Blockfury (2015)