Subj : Re: 2023 > 2024
To   : fusion
From : Blue White
Date : Sun Dec 31 2023 09:05:01

 > iirc QWK networking is (was before Mystic/maybe others implemented it)
 > Synchronet-specific.
 > 
 > maybe it was.. Wildcat? that had a QWK implementation also?

QWK networking goes back pretty far.  Several DOS based BBSes had either
built in or third party add-ons that allowed for QWK networking.  The
ones I am aware of required the client/node to run a script to log onto
the host/hub bbs, access the QWK networking option/door and move the
packets.  I am sure there were other more automated ways but that is the
way I was familiar with.

 > i don't think it's really very complicated.. just run the same scan
 > for
 > messages as a normal user, download the packet, import it into your
 > BBS. i bet
 > you could write a utility to mod whatever might actually be different
 > in a
 > generic QWK packet from any old BBS.. so everyone could be a HUB.. the
 > import
 > part is more special..

There is/was a network status flag that allowed certain systems to upload
messages not from the uploader.  So you could not use just a regular user
account because the BBS would reject messages from other users who were
not associated to the account uploading the REP packet.


--- Talisman v0.51-dev (Linux/armv7l)
 * Origin: possumso.fsxnet.nz * telnet:2123/ssh:2122/ftelnet:80 (21:4/134)

.