Synchronet is the BBS I have online for folks to connect too..
I also have a BBBS, Mystic and MBSE just to keep up with things going on.
Here's a BBS I prepared earlier... just bake for 30 mins on gas mark 7 :)
Here's a BBS I prepared earlier... just bake for 30 mins on gas markI actually have others too that I don't know so well.. yet. :)
Re: Re: Keeping up with Al :)
By: Avon to Al on Fri Jan 22 2021 07:48 pm
Here's a BBS I prepared earlier... just bake for 30 mins on gas
mark 7 :)
I actually have others too that I don't know so well.. yet. :)
I wish I had made a list of all BBS software that I installed and tested in the 90s.
On 01-22-21 11:29, Al wrote to Oli <=-
Re: Keeping up with Al :)
By: Oli to Al on Fri Jan 22 2021 09:30 am
I wish I had made a list of all BBS software that I installed and tested in the 90s.
I think to myself sometimes that it is a pointless exercise, but I
can't help myself.. :)
It's only pointless if your software isn't 4D capable. ;)
It's only pointless if your software isn't 4D capable. ;)
I'm lost now whether I am 3D, 4D or 5D compatible. I think I have a bit
of all that.
Ok, so does 3D = 21:1/2, 4D = 21:1/2.3 and 5D = 21:1/2.3@fsxnet?
I'm lost now whether I am 3D, 4D or 5D compatible. I think I have
a bit of all that.
Do all these dimensions require a Tardis? Cue the signature tune.....
NOW!
Do all these dimensions require a Tardis? Cue the signature tune..... NOW!
It's only pointless if your software isn't 4D capable. ;)
I'm lost now whether I am 3D, 4D or 5D compatible. I think I have a bit
of all that.
3D-only software is really retro, I cannot remember any from the 90s.
And what about 2D? There was a time before zones.
3D-only software is really retro, I cannot remember any from the
90s.
I think I am still 3D/4D. My outbound directories are outbound, outbound.002 and outbound.015 although there is an @fidonet or @fsxnet.
That's the case with SBBS and hpt.
And what about 2D? There was a time before zones.
Today we could use 2D but when the networks were growing the developers
at the time were looking forward with the growth that was happening in those days.
On 01-23-21 14:58, Al wrote to Vk3jed <=-
Re: Re: Keeping up with Al :)
By: Vk3jed to Al on Sun Jan 24 2021 08:18 am
It's only pointless if your software isn't 4D capable. ;)
I'm lost now whether I am 3D, 4D or 5D compatible. I think I have a bit
of all that.
It works, so I'm happy with that. :)
--- SBBSecho 3.12-Linux
At least 4D. :) I kinda call SBBSecho's support "4.5D", because while it does recognise domains, it uses a fixed zone to domain mapping, which kinda defeats the purpose of domains (to resolve zone conflicts in different FTNs).
Of course, Rob (Digital Man) can correct me if I'm wrong. :)
Well, SBBSecho is very much 4D. It's BinkIt that is 5D (or 4.5D?).
On 01-30-21 23:02, Digital Man wrote to Vk3jed <=-
Re: Re: Keeping up with Al :)
By: Vk3jed to Al on Tue Jan 26 2021 08:12 pm
At least 4D. :) I kinda call SBBSecho's support "4.5D", because while it does recognise domains, it uses a fixed zone to domain mapping, which kinda defeats the purpose of domains (to resolve zone conflicts in different FTNs).
Of course, Rob (Digital Man) can correct me if I'm wrong. :)
Well, SBBSecho is very much 4D. It's BinkIt that is 5D (or 4.5D?).
On 30 Jan 2021 at 11:02p, Digital Man pondered and said...
Well, SBBSecho is very much 4D. It's BinkIt that is 5D (or 4.5D?).
This sounds bit like Dolby 5.1 :)
Well, SBBSecho is very much 4D. It's BinkIt that is 5D (or 4.5D?).
Well SBBSecho will at least scan to outbound directories for multiple domains, which is why I called it "4.5D". 4D to me means the todder will put all outbound mail under the main outbound name (with hex extensions
for different zones). :)
On 01-31-21 13:00, Oli wrote to Vk3jed <=-
binkd is 5D-ish, but only for outbound (maybe that's why it's called 5D BSO?). I also would like to have 5D inbound. Unfortunately binkd's 5D
BSO is not compatible with FTS-5005 aka BinkleyTerm 5D BSO. Si we also need a name to distinguish between binkd style outbound and BinkleyTerm style outbound. Multi-4D?
The problem with 5D for mail is that FSC-0039 and FSC-0048 PKTs only support 4D and FSC-0045 (which supports 8 character long domains) is
not very common. Then we also have the problem that the addresses in
the messages itself are only 2D. I'm not sure if there is a de facto standard for putting the domain or full 5D address in a kludge (like
INTL FMPT TOPT). Let's not talk about 5D PATH and 5D SEEN-BY ...
5D means netmails and echomails between 2:*@fidonet and 2:*@classic without side effects.
With >30000 free available zone numbers for <2000 nodes the incentive
for going full 5D is pretty low.
I'm using Amiga _4D_ Outbound in binkd which looks like
fsxnet/21.3.100.0.flo
othernet/32000.23423.15894.22146.flo
On 01-31-21 13:00, Oli wrote to Vk3jed <=-
binkd is 5D-ish, but only for outbound (maybe that's why it's
called 5D BSO?). I also would like to have 5D inbound.
Unfortunately binkd's 5D BSO is not compatible with FTS-5005 aka
BinkleyTerm 5D BSO. Si we also need a name to distinguish between
binkd style outbound and BinkleyTerm style outbound. Multi-4D?
Hmm, I'm not up with the details, and I no longer have access to a working BinkleyTerm system (I could resurrect my old BBS as a museum piece
though). :)
I never used 5D in the old days, due to lack of tosser
support. Everything was 4D (I did run points).
With >30000 free available zone numbers for <2000 nodes the
incentive for going full 5D is pretty low.
In practice, 4000, due to the limitations of BSO on some systems.
I'm using Amiga _4D_ Outbound in binkd which looks like
fsxnet/21.3.100.0.flo
othernet/32000.23423.15894.22146.flo
ASO, actually looks like a nice setup.
fsxnet/21.3.100.0.flo
othernet/32000.23423.15894.22146.flo
ASO, actually looks like a nice setup.
fsxnet/21.3.100.0.flo
othernet/32000.23423.15894.22146.flo
ASO, actually looks like a nice setup.
I saw something like this in the hpt docs although I have never tried it, it looks like hpt does support ASO.
Yes, I just tried it with my old husky config (because I couldn't remember if it worked or not). Of course it's only 4D ASO (outbound/1.2.3.4) and not 5D ASO (domain/1.2.3.4).
On 01-30-21 23:02, Digital Man wrote to Vk3jed <=-
Re: Re: Keeping up with Al :)
By: Vk3jed to Al on Tue Jan 26 2021 08:12 pm
At least 4D. :) I kinda call SBBSecho's support "4.5D", because while it does recognise domains, it uses a fixed zone to domain mapping, which kinda defeats the purpose of domains (to resolve zone conflicts in different FTNs).
Of course, Rob (Digital Man) can correct me if I'm wrong. :)
Well, SBBSecho is very much 4D. It's BinkIt that is 5D (or 4.5D?).
Well SBBSecho will at least scan to outbound directories for multiple domains, which is why I called it "4.5D". 4D to me means the todder will put all outbound mail under the main outbound name (with hex extensions for different zones). :)
On 02-01-21 12:58, Oli wrote to Vk3jed <=-
:) Only difference is that binkd doesn't put hex extension on the
default zone of the othernet. Like
So binkd it's incompatible with many tossers in 5D mode. Which is weird
as binkd only supports 4D with a workaround (never worked out for me).
I started with Squish and BinkleyTerm, which both supported 5D. I
wasn't aware that most other software never did (or I was and doesn't remember it anymore).
With >30000 free available zone numbers for <2000 nodes the
incentive for going full 5D is pretty low.
In practice, 4000, due to the limitations of BSO on some systems.
I wonder why. It's not that the inventor of 4D BSO was forced to make
it work with hex numbers and the 3 character extension. It's perfectly possible to use base32 (e.g. 0-1 A-V) and get 15-bits (0-32767) out of
3 characters. Or use sub directories.
ASO, actually looks like a nice setup.
I started using this out of frustration with binkd's non-standard 5D
BSO implementation. And it was easy to hack it into Squish and
Crashmail, only a few lines of code to change ...
[2 minutes later]
.... actually in Crashmail it is just one line to edit
- sprintf(buf,"%04x%04x",n4d->Net,n4d->Node);
+ sprintf(buf,"%u.%u.%u.%u",n4d->Zone,n4d->Net,n4d->Node,n4d->Point);
and then deleting the if blocks for non-default zones and points.
On 02-01-21 22:45, Digital Man wrote to Vk3jed <=-
Well SBBSecho will at least scan to outbound directories for multiple domains, which is why I called it "4.5D". 4D to me means the todder will put all outbound mail under the main outbound name (with hex extensions for different zones). :)
Right, I forgot about that feature. So yeah, sure, 4.5D. :-)
My binkd seems to be working in %D(ish) mode. :)
ASO, actually looks like a nice setup.
I started using this out of frustration with binkd's non-standard 5D
BSO implementation. And it was easy to hack it into Squish and
Crashmail, only a few lines of code to change ...
Ahh OK. Only possible on modern OSs. Don't try this on DOS! :D
On 02-03-21 10:26, Oli wrote to Vk3jed <=-
Ahh OK. Only possible on modern OSs. Don't try this on DOS! :D
You mean non-obsolete OSs? Even MS-DOS 7.1 and FreeDOS support long
file names [1] ...
.... but okay, Fidonet is stuck in the early 1990s ;)
[1] http://www.cn-dos.net/msdos71/doslfns.htm
("Long File Name (LFN) compatible programs for DOS")
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 38:44:10 |
| Calls: | 2,096 |
| Files: | 11,142 |
| Messages: | 949,870 |