unearthed this old demo screencast of wwivtoss setup for linux that i wrote. made the demo 8 years ago.

https://asciinema.org/a/12253

wwivtoss is a DOS program that allows a #WWIV BBS to work with #fidonet

when i wrote the wsetup config tool, the only way to get wwivnet or fidonet connectivity for linux wwiv was to run the networking components in dosemu. fast-forward a couple of years, and the wwiv 5 project had the networking components running natively on linux, including ftn.

#wwivdev #bbs

oh wow! i may have a few #wwivnet nodes using my wwiv5lastcall mod. :)

#WWIV #WWIVDEV #BBS #telnet

tried sending a "hand-crafted" main type 20 (sub list info) ping to wwivnet nodes just a while ago and waiting for the results. :)
experimenting like this is part of the fun.

#WWIVDEV #WWIV #BBS

i should probably have two interfaces to my board, with one using vanilla development version #WWIV, and another that is my MODded version. eventually, there should be a fully web-based interface.

#BBS #WWIVDEV

cleaned up ibbs-extract3 so it reads only undeleted message text. previously, it would read the raw message.dat file, which could contain the text of already deleted posts. the modification spawns wwivutil to dump the message base to stdout, which ibbs-extract3 then processes. processing is actually much faster, maybe because this version reads the entire message base text to process into memory all at once versus the line by line reading from the file.

#WWIVDEV #WWIV #BBS

while waiting for my son and his cousin to arrive at their destination, i'm bug hunting on new "old" software that few people care about. WWIV is still alive! :D

#WWIV #BBS #WWIVDEV #retrocomputing

just finished writing ibbs-extract3, which is part 2 of my wwiv5ibbslastcaller package. xwibbslastcaller.py was part 1.

xwibbslastcaller.py handles posting a rot47 encoded message with basic caller info on logon to a networked sub.

ibbs-extract3 reads data from networked subs of rot47 encoded messages and generates a laston.txt file for each network.

currently works on #WWIVnet and #fsxNet

#HobbyCoding #WWIV #BBS #WWIVDEV #retrocomputing

eureka!

i can now write hi-bit IBM characters the way a #BBS ANSI file uses by using "latin_1" encoding instead of "cp437" in #python3.

#WWIVDEV #retrocomputing

did some experiments with "eprogs.net" and "epreproc.net" processing in #WWIV #BBS. was able to make super basic example processors for both using #python3.

#WWIVDEV #retrocomputing

no #WWIV #BBS stuff today.
was out practically the entire day.
but ideas are percolating.
will prolly try them out tomorrow.

#WWIVDEV #retrocomputing

Finished a few more fixes on chains in #WWIV #BBS. Changed fmt::sprintf to fmt::format.

Fixed call to EPROGS.NET for new external programs in network2. Started experimenting with a rudimentary external packet processor in Python3. Need to refactor write_wwiv_packet().

#WWIVDEV #retrocomputing

need to add to the code i just wrote to adjust for !okansi() callers.

#wwivdev #wwiv #bbs #retrocomputing #hobbycoding

been looking at the chains code in WWIV and fixing little bits here and there.

one of these days, i will need to sit down and spin up a droplet to deploy the new code to so that the chains code gets tested in "production". :D

#WWIV #BBS #retrocomputing #WWIVDEV

filed a couple of new issues on https://github.com/wwivbbs/wwiv/issues several related to SUBs and network3. wrote up suggested fixes. Rushfan will probably greenlight these. happily getting the hang of this.

#WWIV #BBS #WWIVDEV #retrocomputing

i wrote python2 utilities that read and write binary files from WWIV, various data files and wwivnet packets. converting these to python3 is a challenge because of differences in handling of string and binary between python2 and python3. i found it much easier in python2.

#python #python2 #python3 #WWIV #WWIVDEV

found a bug in current WWIV boardedit, but need someone else to verify. posted the problem in the WWIVDEV sub. it looks like a simple fix.

#WWIV #BBS #WWIVnet #WWIVDEV #retrocomputing