#funwithforth — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #funwithforth, aggregated by home.social.
-
... an update from the trenches:
the code snippet which has been loosely resembling #BBS core functionality (the one I once wrote in #DXForth) has seen a few updates recently.
so now "DX BBS" is able to read and output ASCII text files (it could only read #Forth screen blocks before).
I've also fixed several issues where a connection drop would sometimes allow the next caller to "capture" the previous session.
Next on the list will be the whole "post-a-message" process: writing an index file entry for each new message and storing the corresponding message text etc.
long distant future design goals (so far):
(+) implement DX Forth SIO/2 driver
(+) implement a stable (disconnect proof) BBS program loop
(+) stay true to pure ASCII output only, no fancy escape squences or colors - just like RBBS / RCBBS do
(+) implement text (ASCII) file output
(-) store BBS configuration in plain ASCII text file
(-) implement mesage posting procedure
(-) implement message reading procedure
(-) implement message maintenance procdure (delete msg.)
(-) implement user database
(-) implement user database maintenace procedure (delete / modify user)
(-) implement simple user ACL / flag system
(-) implement (x)modem transfers
I don't have a real roadmap, my motivation may vary and the above is just what I think are the minimum requirements for a classic CP/M based bulletin board system. To give you an impression: it should resemble what #rc2014 #rcbbs does at the moment.
#rc2014
#cpm
#retrocoding
#forth
#bulletinboardsystem
#funwithforth -
... an update from the trenches:
the code snippet which has been loosely resembling #BBS core functionality (the one I once wrote in #DXForth) has seen a few updates recently.
so now "DX BBS" is able to read and output ASCII text files (it could only read #Forth screen blocks before).
I've also fixed several issues where a connection drop would sometimes allow the next caller to "capture" the previous session.
Next on the list will be the whole "post-a-message" process: writing an index file entry for each new message and storing the corresponding message text etc.
long distant future design goals (so far):
(+) implement DX Forth SIO/2 driver
(+) implement a stable (disconnect proof) BBS program loop
(+) stay true to pure ASCII output only, no fancy escape squences or colors - just like RBBS / RCBBS do
(+) implement text (ASCII) file output
(-) store BBS configuration in plain ASCII text file
(-) implement mesage posting procedure
(-) implement message reading procedure
(-) implement message maintenance procdure (delete msg.)
(-) implement user database
(-) implement user database maintenace procedure (delete / modify user)
(-) implement simple user ACL / flag system
(-) implement (x)modem transfers
I don't have a real roadmap, my motivation may vary and the above is just what I think are the minimum requirements for a classic CP/M based bulletin board system. To give you an impression: it should resemble what #rc2014 #rcbbs does at the moment.
#rc2014
#cpm
#retrocoding
#forth
#bulletinboardsystem
#funwithforth -
... an update from the trenches:
the code snippet which has been loosely resembling #BBS core functionality (the one I once wrote in #DXForth) has seen a few updates recently.
so now "DX BBS" is able to read and output ASCII text files (it could only read #Forth screen blocks before).
I've also fixed several issues where a connection drop would sometimes allow the next caller to "capture" the previous session.
Next on the list will be the whole "post-a-message" process: writing an index file entry for each new message and storing the corresponding message text etc.
long distant future design goals (so far):
(+) implement DX Forth SIO/2 driver
(+) implement a stable (disconnect proof) BBS program loop
(+) stay true to pure ASCII output only, no fancy escape squences or colors - just like RBBS / RCBBS do
(+) implement text (ASCII) file output
(-) store BBS configuration in plain ASCII text file
(-) implement mesage posting procedure
(-) implement message reading procedure
(-) implement message maintenance procdure (delete msg.)
(-) implement user database
(-) implement user database maintenace procedure (delete / modify user)
(-) implement simple user ACL / flag system
(-) implement (x)modem transfers
I don't have a real roadmap, my motivation may vary and the above is just what I think are the minimum requirements for a classic CP/M based bulletin board system. To give you an impression: it should resemble what #rc2014 #rcbbs does at the moment.
#rc2014
#cpm
#retrocoding
#forth
#bulletinboardsystem
#funwithforth -
... an update from the trenches:
the code snippet which has been loosely resembling #BBS core functionality (the one I once wrote in #DXForth) has seen a few updates recently.
so now "DX BBS" is able to read and output ASCII text files (it could only read #Forth screen blocks before).
I've also fixed several issues where a connection drop would sometimes allow the next caller to "capture" the previous session.
Next on the list will be the whole "post-a-message" process: writing an index file entry for each new message and storing the corresponding message text etc.
long distant future design goals (so far):
(+) implement DX Forth SIO/2 driver
(+) implement a stable (disconnect proof) BBS program loop
(+) stay true to pure ASCII output only, no fancy escape squences or colors - just like RBBS / RCBBS do
(+) implement text (ASCII) file output
(-) store BBS configuration in plain ASCII text file
(-) implement mesage posting procedure
(-) implement message reading procedure
(-) implement message maintenance procdure (delete msg.)
(-) implement user database
(-) implement user database maintenace procedure (delete / modify user)
(-) implement simple user ACL / flag system
(-) implement (x)modem transfers
I don't have a real roadmap, my motivation may vary and the above is just what I think are the minimum requirements for a classic CP/M based bulletin board system. To give you an impression: it should resemble what #rc2014 #rcbbs does at the moment.
#rc2014
#cpm
#retrocoding
#forth
#bulletinboardsystem
#funwithforth -
... an update from the trenches:
the code snippet which has been loosely resembling #BBS core functionality (the one I once wrote in #DXForth) has seen a few updates recently.
so now "DX BBS" is able to read and output ASCII text files (it could only read #Forth screen blocks before).
I've also fixed several issues where a connection drop would sometimes allow the next caller to "capture" the previous session.
Next on the list will be the whole "post-a-message" process: writing an index file entry for each new message and storing the corresponding message text etc.
long distant future design goals (so far):
(+) implement DX Forth SIO/2 driver
(+) implement a stable (disconnect proof) BBS program loop
(+) stay true to pure ASCII output only, no fancy escape squences or colors - just like RBBS / RCBBS do
(+) implement text (ASCII) file output
(-) store BBS configuration in plain ASCII text file
(-) implement mesage posting procedure
(-) implement message reading procedure
(-) implement message maintenance procdure (delete msg.)
(-) implement user database
(-) implement user database maintenace procedure (delete / modify user)
(-) implement simple user ACL / flag system
(-) implement (x)modem transfers
I don't have a real roadmap, my motivation may vary and the above is just what I think are the minimum requirements for a classic CP/M based bulletin board system. To give you an impression: it should resemble what #rc2014 #rcbbs does at the moment.
#rc2014
#cpm
#retrocoding
#forth
#bulletinboardsystem
#funwithforth