home.social

#bulletinboardsystem — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #bulletinboardsystem, aggregated by home.social.

  1. What better way to relax on your Sunday by visting a BBS or few. We have an ever growing BBS Directory and while there why not list your own BBS!

    Our BBS DIRECTORY Here:
    8bitboyz.com/bbs-directory/

    #BBS #BulletinBoardSystem #Telnet

  2. Feb. 16, 1978 -- forty eight years ago today -- the first public dial-up bulletin board system or BBS went online.

    Wired: "1978: Ward Christensen and Randy Suess launch the first public dialup bulletin board system. The two unleash the kernel of what would eventually spawn the world wide web, countless online messaging systems..."

    wired.com/2010/02/0216cbbs-fir

    I got my first modem in the summer of 1986, a Prometheus ProModem 1200A (modem on a card) for the Apple II. The first BBS I logged in to was OxGate, an RBBS/RCPM system the phone number of which I still can remember (my earliest BBS software -- firmware-based on that modem card -- had no phone book). I used BBSs avidly until sometime in 1994, when I subscribed to a local ISP's (Widomaker of Williamsburg, VA) dial-up modem-based PPP service that brought TCP/IP to my 486 PC with Windows 3.1. I could then browse the web from home, and that was basically the end of BBSing for me -- for the moment, anyway.

    For those interested in experiencing this early form of online community, there are many BBSs online right now, accessible via telnet on systems old and new. I've enjoyed getting back into BBSing this way, especially when using vintage systems to login.

    Most any computer can do it, today. Tips on how: bytecellar.com/bbsing

    #BulletinboardSystem #BBS #BBSing #telnet #dialup #modem #online #terminals #terminalprograms #computinghistory #history #computers #vintagecomputing #retrocomputing #retrocomputers #nostalgia #ATDT #onlineforums #preinternet #internet #communication #RBBS #AppleII #CRT #memories #Wired #tech #technews #technology

  3. Did you know I run a BBS (bulletin board system)? In the year 2026? On a Commodore VIC-20?! It's a great little board - give it a call!

    bbs.deepskies.com:6400

    It runs at 1200 baud and is open 24/7! Tell them Rick sent you!

    #BBS #BulletinBoardSystem #VICBBS #VIC20 #Commodore #C64 #Atari #RetroComputing #RetroProgramming #Modem #Telnet #Terminal #OldSchool

  4. Happy New Year!!!!!
    What better way to start off 2026 than with the yearly update for Image BBS v3.0!
    Here is the link to the latest yearly update just realease by X-Tec:
    8bitboyz.com/download/2025-fix

    #Commodore #BBS #BulletinBoardSystem #Telenet #C64

  5. Did I ever mention RC-BOX BBS - the world's first and (currently) only RC2014 based bulletin board system?!

    Running on a real RC2014, powered by a Z80, CP/M 2.2 and a highly customized fork of RBBS4 this single-user system offers you the 1985 online experience.

    Text games available on the CP/M command shell !!

    P.S.: connection info is in the ALT-text or in my profile info.

    #rc2014bbs
    #rcbox
    #rc2014
    #bbs
    #rcbbs
    #bulletinboardsystem
    #z80

  6. Did I ever mention RC-BOX BBS - the world's first and (currently) only RC2014 based bulletin board system?!

    Running on a real RC2014, powered by a Z80, CP/M 2.2 and a highly customized fork of RBBS4 this single-user system offers you the 1985 online experience.

    Text games available on the CP/M command shell !!

    P.S.: connection info is in the ALT-text or in my profile info.

    #rc2014bbs
    #rcbox
    #rc2014
    #bbs
    #rcbbs
    #bulletinboardsystem
    #z80

  7. Did I ever mention RC-BOX BBS - the world's first and (currently) only RC2014 based bulletin board system?!

    Running on a real RC2014, powered by a Z80, CP/M 2.2 and a highly customized fork of RBBS4 this single-user system offers you the 1985 online experience.

    Text games available on the CP/M command shell !!

    P.S.: connection info is in the ALT-text or in my profile info.

    #rc2014bbs
    #rcbox
    #rc2014
    #bbs
    #rcbbs
    #bulletinboardsystem
    #z80

  8. Did I ever mention RC-BOX BBS - the world's first and (currently) only RC2014 based bulletin board system?!

    Running on a real RC2014, powered by a Z80, CP/M 2.2 and a highly customized fork of RBBS4 this single-user system offers you the 1985 online experience.

    Text games available on the CP/M command shell !!

    P.S.: connection info is in the ALT-text or in my profile info.

    #rc2014bbs
    #rcbox
    #rc2014
    #bbs
    #rcbbs
    #bulletinboardsystem
    #z80

  9. Did I ever mention RC-BOX BBS - the world's first and (currently) only RC2014 based bulletin board system?!

    Running on a real RC2014, powered by a Z80, CP/M 2.2 and a highly customized fork of RBBS4 this single-user system offers you the 1985 online experience.

    Text games available on the CP/M command shell !!

    P.S.: connection info is in the ALT-text or in my profile info.

    #rc2014bbs
    #rcbox
    #rc2014
    #bbs
    #rcbbs
    #bulletinboardsystem
    #z80

  10. Speaking of the - now abandoned - #MagickaBBS: I've preserved the last "known to compile and run" version of the code on my #Codeberg because I really like this software and always thought it was a pity that the project was halted.

    I've also been able to preserve some of the original documentation for the software, although I can *not* guarantee that it will match the checked in codebase in any way. Yet, I still think it's useful.

    codeberg.org/ufud-org/MagickaB

    #BBS
    #bulletinboardsystem

  11. addendum: I've found something more or less useful to do with the aforementioned setup. I'm still trying to iron out a few things, but it's amazing what a little overclocking can do.

    I'm quite impressed at how responsive #NetBSD on the #RapberryPi Model 1 B (without the "plus" but with 512MB RAM - it's a rather early board manufactured in 12/2011) is.

    So I decided to run #MagickaBBS on it, simply because it was the only #BBS software that I was able to compile on NetBSD - most other #bulletinboardsystem #software will not compile on #NetBSD (evbarm platform) for one or another reason - what a shame.

    Anyway: about five years ago, I've had quite a creative burst and designed several #ANSI screens (example: see below) that I've never put into use. But this seems to be the right time to finally change that.

    Stay tuned or follow: #netbsdonoldpi (NetBSD on old Pi) - I'll try to provide further updates in case you are interested ...

  12. Out there, in the worrying world of today is a little #Zilog #Z80 computer with a mere 64KB of #RAM and running the #1970s CP/M operating system.

    This little machine is connected to the #intertubes and it's serving a #singleuser #bulletinboardsystem for you, the worrying souls of #yesteryears to visit.

    Take a break from today, connect like it's 1985 - here on RC-BOX BBS, the world's first and (currently) only #rc2014 based bulletin board system in the world!

    Check out the #alttext or my #profile info for information on how to connect.

    #bbs
    #rc2014bbs
    #rcbox

  13. Out there, in the worrying world of today is a little #Zilog #Z80 computer with a mere 64KB of #RAM and running the #1970s CP/M operating system.

    This little machine is connected to the #intertubes and it's serving a #singleuser #bulletinboardsystem for you, the worrying souls of #yesteryears to visit.

    Take a break from today, connect like it's 1985 - here on RC-BOX BBS, the world's first and (currently) only #rc2014 based bulletin board system in the world!

    Check out the #alttext or my #profile info for information on how to connect.

    #bbs
    #rc2014bbs
    #rcbox

  14. Out there, in the worrying world of today is a little #Zilog #Z80 computer with a mere 64KB of #RAM and running the #1970s CP/M operating system.

    This little machine is connected to the #intertubes and it's serving a #singleuser #bulletinboardsystem for you, the worrying souls of #yesteryears to visit.

    Take a break from today, connect like it's 1985 - here on RC-BOX BBS, the world's first and (currently) only #rc2014 based bulletin board system in the world!

    Check out the #alttext or my #profile info for information on how to connect.

    #bbs
    #rc2014bbs
    #rcbox

  15. Out there, in the worrying world of today is a little #Zilog #Z80 computer with a mere 64KB of #RAM and running the #1970s CP/M operating system.

    This little machine is connected to the #intertubes and it's serving a #singleuser #bulletinboardsystem for you, the worrying souls of #yesteryears to visit.

    Take a break from today, connect like it's 1985 - here on RC-BOX BBS, the world's first and (currently) only #rc2014 based bulletin board system in the world!

    Check out the #alttext or my #profile info for information on how to connect.

    #bbs
    #rc2014bbs
    #rcbox

  16. Out there, in the worrying world of today is a little #Zilog #Z80 computer with a mere 64KB of #RAM and running the #1970s CP/M operating system.

    This little machine is connected to the #intertubes and it's serving a #singleuser #bulletinboardsystem for you, the worrying souls of #yesteryears to visit.

    Take a break from today, connect like it's 1985 - here on RC-BOX BBS, the world's first and (currently) only #rc2014 based bulletin board system in the world!

    Check out the #alttext or my #profile info for information on how to connect.

    #bbs
    #rc2014bbs
    #rcbox

  17. Happy BBSday !!

    On this day today in 1978, Ward Christensen and Randy Suess took the world's first bulletin board system (the "CBBS") officially online.

    #BBSDay
    #CBBS
    #WardChristensen
    #RandySuess
    #BulletinBoardSystem

  18. ... 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

  19. ... 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

  20. ... 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

  21. ... 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

  22. ... 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

  23. The Excalibur BBS client had led me down the most crazy rabbit hole in the last week.

    It's 16-bit, and not like, good 16 bit so the newest OS that can run it is absolutely ancient: XP.

    So I thought, hey, wine can run 16 bit apps! Well, no, wine won't run this particular one.

    Then I was like 'I could make a VM and distribute that to people to use it!' and sure, I could and did.

    But I found something even more cool: you can just like, do it in your browser instead.

    Found a project, v86, which is a bundle of WASM and JS and is basically a subset of QEMU and after far far too much fiddling, breaking stuff, and reading JS code (I do not like JS, I really do not.) I've set up a website that you can literally just load, and instantly up comes a Windows 95 machine with the client running ready for someone to use.

    The future is great, especially when you're using it to access the past.
    #retrocomputing #retropc #bbs #bulletinboardsystem

  24. A pretty fascinating multi-part look at the IGS BBS protocol (Instant Graphics, later Instant Graphics & Sound) on the Atari ST.

    This is part of the #BBS scene that I missed, I must say. By 1990 I was still BBSing full tilt, but had moved off of Atari.

    breakintochat.com/blog/2024/08

    #BBSing #BulletinBoardSystem #dialup #Atari #AtariST #IGS #BBSs #telecommunications #vintagecomputing #retrocomputing #retrocomputers #TOS #GEM #modems #blog #screenshot

  25. While I wait on FTN applications to be approved for my Telegard #BBS, I've moved on to some more uh, unique? options that existed.

    Excalibur BBS was a very late entry into BBS software, but it's main claim to fame is that it was a fully GUI-based software. Basically, it was sold as a run-your-own-AOL type proposition.

    It was unique, neat, and horribly expensive and saw limited use.

    It also has a major problem of requiring a proprietary client to do anything, which is, of course, a 16-bit app and not really usable on modern systems.

    But VMs exist, and you can run it: Using NT4 for the server and XP for the client you get this lovely chunk of
    #retrocomputing #bulletinboardsystem history.