On 30 Dec 2023, apam said the following...The tricky part is distribution, everyone expects an ftp server that
can dynamically create a QWK file to download on request. In my mind
it would have made more sense to use HTTP, then you could just have a
php script or something create the qwk packet - but I don't know the history.
The history goes back to dial-up days when you had to dial in and have
the dialing software run a script to exchange packets with the hub. Some BBSes may have had a more automated way of doing that, but it predates
the internet.
mystic can use qwkpoll to import qwk packets that were previously wget-ed. so you're not stuck with qwkpoll doing ftp internally.. it just wouldn't be as automagic .. i think mystic by default will do "qwkpoll all" which would do nothing for a default config, but just automatically work if you add a qwk hub in mystic -cfg.. whereas you'd have to replace that event with a script to wget the packet, import it, check it was imported correctly.. have the script pass along the exitstatus so mystic is happy.. not as clean but certainly not venturing into hackish territory.
| Sysop: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 126 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 02:07:50 |
| Calls: | 7,684 |
| Files: | 9,369 |
| D/L today: |
107 files (14,348K bytes) |
| Messages: | 392,399 |