If you are running multiple FTN-based message areas, is the badareas.lst updated generically? I believe it is. For example, FidoNet may have a SYSOP echo, but WWIVnet may also have a SYSOP echo, creating confusion amongst the file and for a re-import. Could a change be put in to reflect the Message Group for the creation of a new badareas.lst file, e.g. fidonet-badareas.lst, micronet-badareas.lst, etc.? Or, keep the file but group them with tags that can be interpretted by the Import Areas function of SCFG:

[fidonet]
.
.
.
[scinet]
.
.
.
[micronet]
.
.
.

...just trying to make things a little more logical.

Brian Klauss <-> Dream Master
Caught in a Dream | caughtinadream.com a Synchronet BBS

---
þ Synchronet þ Caught in a Dream - caughtinadream.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Dream Master to All on Thu Jan 28 2021 08:56 am

For example, FidoNet may have a SYSOP echo, but WWIVnet may also have a SYSOP echo, creating confusion amongst the file and for a re-import. Could a change be put in to reflect

There can be no two areas with the same tag, that will never work. You would have to have two configurations and a headache.

Othernets generally use a prefix like WWIV_SYSOP or something similar.

Ttyl :-),
Al

... Every action has an equal and opposite government program

---
þ Synchronet þ The Rusty MailBox - Penticton, BC Canada
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Dream Master to All on Thu Jan 28 2021 08:56 am

If you are running multiple FTN-based message areas, is the badareas.lst updated generically? I believe it is.

Echo-tags for all FTNs shared by the same area file share the same namespace. Put another way, duplicate echo-tags in an area file are not allowed.

For example, FidoNet may have a
SYSOP echo, but WWIVnet may also have a SYSOP echo, creating confusion amongst the file and for a re-import.

They're exactly the same echo-tag? That would be a problem in a lot of ways for a single configuration of SBBSecho.

Could a change be put in to reflect
the Message Group for the creation of a new badareas.lst file, e.g. fidonet-badareas.lst, micronet-badareas.lst, etc.?

I don't see how that solves a problem. You can't have 2 echoes using the same echo-tag in the same area file.

Or, keep the file but
group them with tags that can be interpretted by the Import Areas function of SCFG:

If you have multiple FTNs with echo-tag collisions, you'll need to run multiple SBBSecho configurations (with different area files) to keep them separate. Both the area file and the bad area file names and paths are configurable in your sbbsecho configuratoin. So using multiple SBBSecho configurations would be the first step to the solution there.
--
digital man

Synchronet/BBS Terminology Definition #52:
NNTP = Network News Transfer Protocol
Norco, CA WX: 53.9øF, 58.0% humidity, 1 mph SW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Digital Man to Dream Master on Thu Jan 28 2021 08:00 pm

If you have multiple FTNs with echo-tag collisions, you'll need to run multiple SBBSecho configurations (with different area files) to keep them separate. Both the area file and the bad area file names and paths are configurable in your sbbsecho configuratoin. So using multiple SBBSecho configurations would be the first step to the solution there.

There is an allowance for bad area file names for different echo groups? Okay... this makes sense as I didn't think there was. Going to play with that feature now.

Thank you!

Brian Klauss <-> Dream Master
Caught in a Dream | caughtinadream.com a Synchronet BBS

---
þ Synchronet þ Caught in a Dream - caughtinadream.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Dream Master to Digital Man on Fri Jan 29 2021 12:07 am

Re: badareas.lst
By: Digital Man to Dream Master on Thu Jan 28 2021 08:00 pm

If you have multiple FTNs with echo-tag collisions, you'll need to run multiple SBBSecho configurations (with different area files) to keep them separate. Both the area file and the bad area file names and paths are configurable in your sbbsecho configuratoin. So using multiple SBBSecho configurations would be the first step to the solution there.

There is an allowance for bad area file names for different echo groups?

No, there's an allowance for specific/different bad area file name for different SBBSecho configurations. e.g. you have a fidonet.ini (alternate sbbsecho.ini file) which has a different bad area file name or path than the primary sbbsecho.ini file.
--
digital man

This Is Spinal Tap quote #3:
How much more black could this be? and the answer is none. None more black. Norco, CA WX: 46.6øF, 90.0% humidity, 0 mph SSW wind, 0.76 inches rain/24hrs --- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Digital Man to Dream Master on Fri Jan 29 2021 07:33 pm

There is an allowance for bad area file names for different echo groups?

No, there's an allowance for specific/different bad area file name for different SBBSecho configurations. e.g. you have a fidonet.ini (alternate sbbsecho.ini file) which has a different bad area file name or path than the primary sbbsecho.ini file.

Wait, really? Was this recently changed (was this from the commit earlier this week or late last week)?

Brian Klauss <-> Dream Master
Caught in a Dream | caughtinadream.com a Synchronet BBS

---
þ Synchronet þ Caught in a Dream - caughtinadream.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Dream Master to Digital Man on Fri Jan 29 2021 10:12 pm

Re: badareas.lst
By: Digital Man to Dream Master on Fri Jan 29 2021 07:33 pm

There is an allowance for bad area file names for different echo groups?

No, there's an allowance for specific/different bad area file name for different SBBSecho configurations. e.g. you have a fidonet.ini (alternate sbbsecho.ini file) which has a different bad area file name or path than the primary sbbsecho.ini file.

Wait, really? Was this recently changed (was this from the commit earlier this week or late last week)?

SBBSecho has always supported multiple/separate config files, if that's what the sysop desired (most don't). And as long as it has supported a "bad areas file", it has allowed the sysop to configure the name and path of that file.
--
digital man

Synchronet "Real Fact" #104:
The official Synchronet YouTube channel went live on May 6, 2019
Norco, CA WX: 43.9øF, 92.0% humidity, 0 mph SW wind, 0.76 inches rain/24hrs
--- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Digital Man to Dream Master on Fri Jan 29 2021 07:33 pm

No, there's an allowance for specific/different bad area file name for different SBBSecho configurations. e.g. you have a fidonet.ini (alternate sbbsecho.ini file) which has a different bad area file name or path than the primary sbbsecho.ini file.

I think I found a problem. Although sbbsecho.ini can be split off into individual FTN files (fidonet.ini, scinet.ini, ...), tickit.js only parses sbbsecho.ini. Would it be possible to put in an echo configuration to specify those individual configuration files, for example:

[TickIT]
EchoCfg1=../ctrl/fidonet.ini
EchoCfg2=../ctrl/scinet.ini
EchoCfg3=../ctrl/micronet.ini
.
.
.

I've purged my sbbsecho.ini (well, renamed it to sbbsecho.ini.old) and can see in the logs that TickIT is looking for the file to parse. Unless you tell me there's a way to hack the crap out of sbbsecho.ini, I'm kind of at a loss how to do it any other way.

Brian Klauss <-> Dream Master
Caught in a Dream | caughtinadream.com a Synchronet BBS

---
þ Synchronet þ Caught in a Dream - caughtinadream.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Dream Master to Digital Man on Sat Jan 30 2021 01:43 pm

Re: badareas.lst
By: Digital Man to Dream Master on Fri Jan 29 2021 07:33 pm

No, there's an allowance for specific/different bad area file name for different SBBSecho configurations. e.g. you have a fidonet.ini (alternate sbbsecho.ini file) which has a different bad area file name or path than the primary sbbsecho.ini file.

I think I found a problem. Although sbbsecho.ini can be split off into individual FTN files (fidonet.ini, scinet.ini, ...), tickit.js only parses sbbsecho.ini. Would it be possible to put in an echo configuration to specify those individual configuration files, for example:

[TickIT]
EchoCfg1=../ctrl/fidonet.ini
EchoCfg2=../ctrl/scinet.ini
EchoCfg3=../ctrl/micronet.ini
.
.
.

I've purged my sbbsecho.ini (well, renamed it to sbbsecho.ini.old) and can see in the logs that TickIT is looking for the file to parse. Unless you tell me there's a way to hack the crap out of sbbsecho.ini, I'm kind of at a loss how to do it any other way.

Most sysops do not desire or require multiple sbbsecho configurations. Compared to SBBSecho, TickIT is relatively new, but not *that* new, and nobody has reported the issue you are (I agree, it's an issue) - anyway, so I'm wondering if perhaps you're trying to solve a non-problem. Do you actually have multiple FTNs with the same echo-tags between them? If it's only WWIVnet and FidoNet that are colliding, maybe no other SBBSecho users are also on WWIVnet (seems unlikely).

In the mean time, I'll look at a way for TickIT to use multiple SBBSecho configuration files.
--
digital man

Synchronet "Real Fact" #92:
Digital Man's manifesto from '96: http://wiki.synchro.net/history:manifesto Norco, CA WX: 59.5øF, 55.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Digital Man to Dream Master on Sat Jan 30 2021 02:35 pm

In the mean time, I'll look at a way for TickIT to use multiple SBBSecho configuration files.

If you still want to go the multiple configs route, you should now be able to pass a unique configuration filename on the command-line to tickit.js (e.g "?tickit fidotick.ini")

And then in within that configuration file, specify "echocfg=fidoecho.ini", and that would link that fidotick.ini to fidoecho.ini.

If this works for you, I'll look into updating tickitcfg to support this paradigm too. For now, you'd have to hand edit the custom named tickit config file.
--
digital man

Rush quote #3:
The men who hold high places must be the ones who start... Closer to the Heart Norco, CA WX: 61.2øF, 53.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Digital Man to Dream Master on Sat Jan 30 2021 02:35 pm

Most sysops do not desire or require multiple sbbsecho configurations. Compared to SBBSecho, TickIT is relatively new, but not *that* new, and nobody has reported the issue you are (I agree, it's an issue) - anyway, so I'm wondering if perhaps you're trying to solve a non-problem. Do you actually have multiple FTNs with the same echo-tags between them? If it's only WWIVnet and FidoNet that are colliding, maybe no other SBBSecho users are also on WWIVnet (seems unlikely).

My problem is the monolithic sbbsecho.ini file and my desire to split off inbound, outbound, and nonsecure into their own directory structures:

FidoNet:

/sbbs/fido/_fidonet/outbound
/sbbs/fido/_fidonet/inbound
/sbbs/fido/_fidonet/nonsecure

SciNet:

/sbbs/fido/_scinet/outbound
/sbbs/fido/_scinet/inbound
/sbbs/fido/_scinet/nonsecure
.
.
.

I've now received multiple TICs coming in that are from multiple FTNs with the same filename (and it pisses me off). For example, someone that is sending a file not from the FidoNet FTN but from another FTN, is sending the latest FidoNet nodelist/nodediff to me. Where my problem comes in is when something like this happens:

4 -rw------- 1 sbbs sbbs 1270 Jan 30 11:11 ti_008m8.tic
412 -rw------- 1 sbbs sbbs 418428 Jan 30 11:10 ww210130.zip
4 -rw------- 1 sbbs sbbs 1241 Jan 30 02:24 ti_008m4.tic
4 -rw------- 1 sbbs sbbs 1450 Jan 30 02:24 ti_008m2.tic
4 -rw------- 1 sbbs sbbs 1405 Jan 30 02:24 ti_008m3.tic
4 -rw------- 1 sbbs sbbs 1167 Jan 30 02:24 ti_008m0.tic
4 -rw------- 1 sbbs sbbs 1486 Jan 30 02:24 ti_008m1.tic
4 -rw------- 1 sbbs sbbs 1298 Jan 30 02:24 ti_008l_.tic
4 -rw------- 1 sbbs sbbs 1403 Jan 30 02:24 ti_008l-.tic
4 -rw------- 1 sbbs sbbs 1300 Jan 30 02:24 ti_008lz.tic
24 -rw------- 1 sbbs sbbs 20990 Jan 30 02:10 VIRNET.ZIP
2872 -rw------- 1 sbbs sbbs 2940039 Jan 30 02:10 JUSTANET.ZIP
1072 -rw------- 1 sbbs sbbs 1094756 Jan 30 02:10 RMININFO.ZIP
1012 -rw------- 1 sbbs sbbs 1035836 Jan 30 02:10 LIN_INFO.ZIP
36 -rw------- 1 sbbs sbbs 32871 Jan 30 02:10 FMLYNET.ZIP
1520 -rw------- 1 sbbs sbbs 1555582 Jan 30 02:10 ADVNET.ZIP
2880 -rw------- 1 sbbs sbbs 2945776 Jan 30 02:10 JN_INFO.ZIP
32 -rw------- 1 sbbs sbbs 31545 Jan 30 02:10 ZYXELNET.ZIP
4 -rw------- 1 sbbs sbbs 1167 Jan 30 01:53 ti_008ly.tic
3252 -rw------- 1 sbbs sbbs 3328130 Jan 30 01:40 ap210130.zip
4 -rw------- 1 sbbs sbbs 906 Jan 29 22:37 ti_008lu.tic
52 -rw------- 1 sbbs sbbs 51742 Jan 29 22:35 Z1DAILY.Z30
4 -rw------- 1 sbbs sbbs 1270 Jan 29 22:04 ti_008ln.tic
4 -rw------- 1 sbbs sbbs 1167 Jan 29 22:04 ti_008lj.tic
4 -rw------- 1 sbbs sbbs 1138 Jan 29 22:04 ti_008lf.tic
4 -rw------- 1 sbbs sbbs 825 Jan 29 22:03 ti_008l6.tic
4 -rw------- 1 sbbs sbbs 1004 Jan 29 22:03 ti_008ld.tic
4 -rw------- 1 sbbs sbbs 906 Jan 29 22:03 ti_008k_.tic
4 -rw------- 1 sbbs sbbs 1100 Jan 29 22:03 ti_008ks.tic
4 -rw------- 1 sbbs sbbs 961 Jan 29 22:03 ti_008kt.tic
4 -rw------- 1 sbbs sbbs 1960 Jan 29 22:03 ti_008ku.tic
28 -rw------- 1 sbbs sbbs 25000 Jan 29 22:00 AGORANET.ZIP
4 -rw------- 1 sbbs sbbs 566 Jan 29 22:00 AGN_DIFF.Z29
12 -rw------- 1 sbbs sbbs 10026 Jan 29 22:00 AGORANET.Z29
4 -rw------- 1 sbbs sbbs 430 Jan 29 19:11 fenodes.077
4 -rw------- 1 sbbs sbbs 430 Jan 29 19:11 fenodes.dat
4 -rw------- 1 sbbs sbbs 847 Jan 29 19:06 ti_008kk.tic
4 -rw------- 1 sbbs sbbs 2259 Jan 29 18:53 16stg91p.tic
4 -rw------- 1 sbbs sbbs 2278 Jan 29 18:53 16stg8yq.tic
412 -rw------- 1 sbbs sbbs 420921 Jan 29 11:10 ww210129.zip
12 -rw------- 1 sbbs sbbs 9187 Jan 29 02:05 micronet.zip
20 -rw------- 1 sbbs sbbs 19910 Jan 29 02:05 MININFO.ZIP
6128 -rw------- 1 sbbs sbbs 6271116 Jan 29 01:20 ap210129.zip
52 -rw------- 1 sbbs sbbs 51769 Jan 28 22:37 Z1DAILY.Z29
4 -rw------- 1 sbbs sbbs 1747 Jan 28 22:20 NODEDIFF.Z29
4 -rw------- 1 sbbs sbbs 2291 Jan 28 22:05 NODEDIFF.A29

All this shit can't be processed and this is before I split off into individual echocfg files. TickIT barfed when trying to process this. All the file areas are created and tickit.ini is properly configured, yet, I get the above. Knowing where half this shit comes from may help me narrow stuff done and also give me an opportunity to fix anything hokey in my config (but, I've double checked everything multiple times and it still won't process).

In the mean time, I'll look at a way for TickIT to use multiple SBBSecho configuration files.

Thank you. For as many years as I've known you, you are still a stand-up guy (with less hair than the last time I saw you). :)

Brian Klauss <-> Dream Master
Caught in a Dream | caughtinadream.com a Synchronet BBS

---
þ Synchronet þ Caught in a Dream - caughtinadream.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Digital Man to Dream Master on Sat Jan 30 2021 03:23 pm

If you still want to go the multiple configs route, you should now be able to pass a unique configuration filename on the command-line to tickit.js (e.g "?tickit fidotick.ini")

And then in within that configuration file, specify "echocfg=fidoecho.ini", and that would link that fidotick.ini to fidoecho.ini.

I performed a Git pull about an hour ago then saw this message. I made the necessary changes and here's the output:

Jan 30 17:13:26 ciad-n1 sbbs: 1/30 17:13:26 evnt DAILY Semaphore signaled for Timed Event: FIDO_TIC
Jan 30 17:13:26 ciad-n1 sbbs: 1/30 17:13:26 evnt FIDO_TIC Running timed event: FIDO_TIC
Jan 30 17:13:26 ciad-n1 sbbs: 1/30 17:13:26 evnt FIDO_TIC !JavaScript /sbbs/exec/load/fido_syscfg.js line 43: Error: 2 opening '/sbbs/ctrl/sbbsecho.ini'
Jan 30 17:13:26 ciad-n1 sbbs: 1/30 17:13:26 evnt FIDO_TIC Timed event: FIDO_TIC returned 0

In the file I called /sbbs/ctrl/fidonet_tick.ini, I added this on the first line:

EchoCfg=/sbbs/ctrl/fidonet.ini

Error 2 opening sbbsecho.ini.

Thoughts?

Brian Klauss <-> Dream Master
Caught in a Dream | caughtinadream.com a Synchronet BBS

---
þ Synchronet þ Caught in a Dream - caughtinadream.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Dream Master to Digital Man on Sat Jan 30 2021 05:00 pm

Re: badareas.lst
By: Digital Man to Dream Master on Sat Jan 30 2021 02:35 pm

Most sysops do not desire or require multiple sbbsecho configurations. Compared to SBBSecho, TickIT is relatively new, but not *that* new, and nobody has reported the issue you are (I agree, it's an issue) - anyway, so I'm wondering if perhaps you're trying to solve a non-problem. Do you actually have multiple FTNs with the same echo-tags between them? If it's only WWIVnet and FidoNet that are colliding, maybe no other SBBSecho users are also on WWIVnet (seems unlikely).

My problem is the monolithic sbbsecho.ini file and my desire to split off inbound, outbound, and nonsecure into their own directory structures:

FidoNet:

/sbbs/fido/_fidonet/outbound
/sbbs/fido/_fidonet/inbound
/sbbs/fido/_fidonet/nonsecure

SciNet:

/sbbs/fido/_scinet/outbound
/sbbs/fido/_scinet/inbound
/sbbs/fido/_scinet/nonsecure

Each domain can already have its own outbound root (configured in echocfg->Domains).

For hub-specific secure-inbounds, you could acheive that with inboxes. But BinkIT doesn't support inboxes (you'd have to use BinkD or another mailer that supported inboxes).

I've now received multiple TICs coming in that are from multiple FTNs with the same filename (and it pisses me off). For example, someone that is sending a file not from the FidoNet FTN but from another FTN, is sending the latest FidoNet nodelist/nodediff to me. Where my problem comes in is when something like this happens:

All this shit can't be processed and this is before I split off into individual echocfg files. TickIT barfed when trying to process this. All the file areas are created and tickit.ini is properly configured, yet, I get the above. Knowing where half this shit comes from may help me narrow stuff done and also give me an opportunity to fix anything hokey in my config (but, I've double checked everything multiple times and it still won't process).

Dunno. I haven't actually use TickIT myself and don't have any immediate plans to, but of course, the source is right there in your exec dir for further debugging or fixing of issues you observe.

In the mean time, I'll look at a way for TickIT to use multiple SBBSecho configuration files.

Thank you. For as many years as I've known you, you are still a stand-up guy (with less hair than the last time I saw you). :)

Ha! Yeah, it's been long time. You were the first person to purchase Synchronet (or first of very few to purchase the source code) as I recall. Do you still have that old source code?
--
digital man

Rush quote #6:
... but most of us just dream about the things we'd like to be
Norco, CA WX: 60.3øF, 49.0% humidity, 0 mph WSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Dream Master to Digital Man on Sat Jan 30 2021 05:15 pm

Re: badareas.lst
By: Digital Man to Dream Master on Sat Jan 30 2021 03:23 pm

If you still want to go the multiple configs route, you should now be able to pass a unique configuration filename on the command-line to tickit.js (e.g "?tickit fidotick.ini")

And then in within that configuration file, specify "echocfg=fidoecho.ini", and that would link that fidotick.ini to fidoecho.ini.

I performed a Git pull about an hour ago then saw this message. I made the necessary changes and here's the output:

Jan 30 17:13:26 ciad-n1 sbbs: 1/30 17:13:26 evnt DAILY Semaphore signaled for Timed Event: FIDO_TIC
Jan 30 17:13:26 ciad-n1 sbbs: 1/30 17:13:26 evnt FIDO_TIC Running timed event: FIDO_TIC
Jan 30 17:13:26 ciad-n1 sbbs: 1/30 17:13:26 evnt FIDO_TIC !JavaScript /sbbs/exec/load/fido_syscfg.js line 43: Error: 2 opening '/sbbs/ctrl/sbbsecho.ini'
Jan 30 17:13:26 ciad-n1 sbbs: 1/30 17:13:26 evnt FIDO_TIC Timed event: FIDO_TIC returned 0

In the file I called /sbbs/ctrl/fidonet_tick.ini, I added this on the first line:

EchoCfg=/sbbs/ctrl/fidonet.ini

Error 2 opening sbbsecho.ini.

Thoughts?

Are you psasing "fidonet_tick.ini" on the tickit.js command-line?
--
digital man

This Is Spinal Tap quote #45:
I don't really think the end can be assessed as of itself as being the end Norco, CA WX: 60.1øF, 49.0% humidity, 0 mph WSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Digital Man to Dream Master on Sat Jan 30 2021 04:48 pm

Are you psasing "fidonet_tick.ini" on the tickit.js command-line?

Sorry for the late reply but I've been busy with family stuff.

The SCFG configuration has the specific Timed Event as the following:

?tickit.js /sbbs/ctrl/fidonet_tick.ini

I will be damned if I typed that wrong.

Brian Klauss <-> Dream Master
Caught in a Dream | caughtinadream.com a Synchronet BBS

---
þ Synchronet þ Caught in a Dream - caughtinadream.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Digital Man to Dream Master on Sat Jan 30 2021 04:44 pm

Ha! Yeah, it's been long time. You were the first person to purchase Synchronet (or first of very few to purchase the source code) as I recall. Do you still have that old source code?

I believe I was the first to purchase both. :) No. When I moved from Anaheim to Placentia, everything was put into boxes by my mother as I wasn't being very helpful in the move (you know, having a life). When I was going through the boxes, I tagged everything that was important. After leaving home and moving to Corona Hills (91 and Green Mountain), my mother put all the boxes up and then a couple years later my parents decided to clean out the garage. Guess where my "super duper really important box" was at? NOT THERE!

Brian Klauss <-> Dream Master
Caught in a Dream | caughtinadream.com a Synchronet BBS

---
þ Synchronet þ Caught in a Dream - caughtinadream.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On 01-30-21 14:35, Digital Man wrote to Dream Master <=-

Most sysops do not desire or require multiple sbbsecho configurations. Compared to SBBSecho, TickIT is relatively new, but not *that* new, and nobody has reported the issue you are (I agree, it's an issue) -
anyway, so I'm wondering if perhaps you're trying to solve a
non-problem. Do you actually have multiple FTNs with the same echo-tags between them? If it's only WWIVnet and FidoNet that are colliding,
maybe no other SBBSecho users are also on WWIVnet (seems unlikely).

I'm on WWIV-FTN, but perhaps I'm not linked to a conflicting echo on the Fidonet side. :)


... Apathy Error: Strike any key...or none, for that matter.
=== MultiMail/Win v0.52
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Re: badareas.lst
By: Dream Master to Digital Man on Sun Jan 31 2021 12:19 am

Re: badareas.lst
By: Digital Man to Dream Master on Sat Jan 30 2021 04:48 pm

Are you psasing "fidonet_tick.ini" on the tickit.js command-line?

Sorry for the late reply but I've been busy with family stuff.

The SCFG configuration has the specific Timed Event as the following:

?tickit.js /sbbs/ctrl/fidonet_tick.ini

I don't think that would work as the code I wrote expected just the filename to be specified (e.g. "?tickit.js fidonet_tick.ini"). The ctrl directory is assumed.
--
digital man

Rush quote #9:
One likes to believe in the freedom of ... baseball!
Norco, CA WX: 49.3øF, 60.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Dream Master to Digital Man on Sun Jan 31 2021 12:23 am

Re: badareas.lst
By: Digital Man to Dream Master on Sat Jan 30 2021 04:44 pm

Ha! Yeah, it's been long time. You were the first person to purchase Synchronet (or first of very few to purchase the source code) as I recall. Do you still have that old source code?

I believe I was the first to purchase both. :)

That's pretty prestigious. :-)

No. When I moved from
Anaheim to Placentia, everything was put into boxes by my mother as I wasn't being very helpful in the move (you know, having a life). When I was going through the boxes, I tagged everything that was important. After leaving home and moving to Corona Hills (91 and Green Mountain), my mother put all the boxes up and then a couple years later my parents decided to clean out the garage. Guess where my "super duper really important box" was at? NOT THERE!

Ah. :-( Well, at least I can restore the source code to you after all these years: https://gitlab.synchro.net/main/sbbs1a
--
digital man

Sling Blade quote #3:
Karl (re: killing Doyle): That second one just plum near cut his head in two. Norco, CA WX: 49.3øF, 60.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Digital Man to Dream Master on Sun Jan 31 2021 01:59 am

I believe I was the first to purchase both. :)

That's pretty prestigious. :-)

It was ironic how close you and I lived and whom we associated with. :)

Looking back, the best part of my whole relationship with my girlfriend at the time was meeting you in person. (seriously)

Ah. :-( Well, at least I can restore the source code to you after all these years: https://gitlab.synchro.net/main/sbbs1a

I think I'll stick with SBBS3 instead of 1a. There's been a "few" improvements since then.

Brian Klauss <-> Dream Master
Caught in a Dream | caughtinadream.com a Synchronet BBS

---
þ Synchronet þ Caught in a Dream - caughtinadream.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Digital Man to Dream Master on Sun Jan 31 2021 01:58 am

I don't think that would work as the code I wrote expected just the filename to be specified (e.g. "?tickit.js fidonet_tick.ini"). The ctrl directory is assumed.

The last outstanding problem is binkit.js. binkit.js wants sbbsecho.ini instead of command line ini file. I was able to adjust the fidoin/fidoout appropriately:

%!sbbsecho%. -ce /sbbs/ctrl/fidonetini
%!sbbsecho%. -ce /sbbs/ctrl/scinet.ini
.
.
.
%!sbbsecho%. -ni /sbbs/ctrl/fidonet.ini
%!sbbsecho%. -ni /sbbs/ctrl/scinet.ini
.
.
.

In terms of tickit, yes:

?tickit.js fidonet_tick.ini
?tickit.js scinet_tick.ini
.
.
.

?tickfix, though, doesn't take any arguments.

Okay ... I'm annoyed as I think I just fucked myself. :|

Time to consolidate all the files and start again. (I need an eye roller)


Brian Klauss <-> Dream Master
Caught in a Dream | caughtinadream.com a Synchronet BBS

---
þ Synchronet þ Caught in a Dream - caughtinadream.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Dream Master to Digital Man on Sun Jan 31 2021 05:53 pm

Re: badareas.lst
By: Digital Man to Dream Master on Sun Jan 31 2021 01:59 am

I believe I was the first to purchase both. :)

That's pretty prestigious. :-)

It was ironic how close you and I lived and whom we associated with. :)

But seriously, thank you. Those early sales were my inspiration to keep going. If nobody else wanted to use the software, I'm sure I'd have lost interest long ago. But not many bought (or were offered) the source code back then either. I (like most software devs of the time) was overly-paranoid about protecting my "intelectual property". Seems silly in hindsight.

Looking back, the best part of my whole relationship with my girlfriend at the time was meeting you in person. (seriously)

Ah, well that's a whole other conversation we probably shouldn't be having here. :-)

Ah. :-( Well, at least I can restore the source code to you after all these years: https://gitlab.synchro.net/main/sbbs1a

I think I'll stick with SBBS3 instead of 1a. There's been a "few" improvements since then.

Ah, yeah, just a few. It was fun to get that old code compiling and working again (post Y2K and all), using those old tools. It all feels like a toy now: so few files, so few lines of code, so few dependencies. Piece of cake to find and fix bugs in, even without the use of a debugger.
--
digital man

Rush quote #39:
Sounds that build high like a mountain or notes that fall, gently, like rain Norco, CA WX: 61.4øF, 42.0% humidity, 5 mph WSW wind, 0.00 inches rain/24hrs --- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Dream Master to Digital Man on Sun Jan 31 2021 06:19 pm

Re: badareas.lst
By: Digital Man to Dream Master on Sun Jan 31 2021 01:58 am

I don't think that would work as the code I wrote expected just the filename to be specified (e.g. "?tickit.js fidonet_tick.ini"). The ctrl directory is assumed.

The last outstanding problem is binkit.js. binkit.js wants sbbsecho.ini instead of command line ini file.

Ah, try my most recent commit to binkit.js. It should now support that. You'd have to update your timed event and services.ini command-lines.
--
digital man

Synchronet "Real Fact" #79:
172 Synchronet Match Maker registrations were sold (@$69) between 1995 and 1996.
Norco, CA WX: 61.2øF, 42.0% humidity, 3 mph E wind, 0.00 inches rain/24hrs
--- SBBSecho 3.12-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Dream Master to Digital Man on Sun Jan 31 2021 05:53 pm

It was ironic how close you and I lived and whom we associated with. :)

Looking back, the best part of my whole relationship with my girlfriend at the time was meeting you in person. (seriously)

whoa whoa whoa. TMI TMI

speak no further.
---
þ Synchronet þ ::: BBSES.info - free BBS services :::
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Digital Man to Dream Master on Sun Jan 31 2021 06:37 pm

But seriously, thank you. Those early sales were my inspiration to keep going. If nobody else wanted to use the software, I'm sure I'd have lost interest long ago. But not many bought (or were offered) the source code back then either. I (like most software devs of the time) was overly-paranoid about protecting my "intelectual property". Seems silly in hindsight.

I think the problem with everyone young and in IT, whether developers or sysadmins, is no longer being "useful". I spent too many years hoarding knowledge forcing me to be the subject matter expert on many areas. This bit me in the ass and I lost out on early promotions. We learn and that's all that matters.

Looking back, the best part of my whole relationship with my girlfriend at the time was meeting you in person. (seriously)

Ah, well that's a whole other conversation we probably shouldn't be having here. :-)

Yep. :) But hey, look where we are now.

Ah, yeah, just a few. It was fun to get that old code compiling and working again (post Y2K and all), using those old tools. It all feels like a toy now: so few files, so few lines of code, so few dependencies. Piece of cake to find and fix bugs in, even without the use of a debugger.

<snort> I believe there are so many things we as developers and sysadmins did in the 80s and 90s that we truly regret. My favorites, "This program won't be needed past the 90s" or "we should get rid of all the COBOL and Fortran programs. They cost too much."

Brian Klauss <-> Dream Master
Caught in a Dream | caughtinadream.com a Synchronet BBS

---
þ Synchronet þ Caught in a Dream - caughtinadream.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: MRO to Dream Master on Sun Jan 31 2021 09:22 pm

Looking back, the best part of my whole relationship with my girlfriend at the time was meeting you in person. (seriously)

whoa whoa whoa. TMI TMI

speak no further.

Everything was on the up and up, MRO. No shady shit.

Brian Klauss <-> Dream Master
Caught in a Dream | caughtinadream.com a Synchronet BBS

---
þ Synchronet þ Caught in a Dream - caughtinadream.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Dream Master to Digital Man on Sun Jan 31 2021 06:19 pm

Okay ... I'm annoyed as I think I just fucked myself. :|
Time to consolidate all the files and start again. (I need an eye roller)

I'm trying to figure out why you want to add so much complexity to your setup. Back to the original issue, I have WWIVnet and many others with no echotag conflicts. All the WWIV echotags are prefixed with "WWIV_".

If its a filegate issue, I must admit I don't always subscribe to more then the nodelist filegates*, but I haven't had a problem there either. :-/

*Plus the requisite FIDONEWS filearea. All hail P4.

Bob Roberts

---
þ Synchronet þ Halls of Valhalla =San=Francisco= hovalbbs.com:2333
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: badareas.lst
By: Bob Roberts to Dream Master on Mon Feb 01 2021 07:50 am

I'm trying to figure out why you want to add so much complexity to your setup. Back to the original issue, I have WWIVnet and many others with no echotag conflicts. All the WWIV echotags are prefixed with "WWIV_".

If its a filegate issue, I must admit I don't always subscribe to more then the nodelist filegates*, but I haven't had a problem there either. :-/

I'm not a fan of monolithic files. When trying to troubleshoot issues, I like to split apart thingss to see where the problem may stem from.

Brian Klauss <-> Dream Master
Caught in a Dream | caughtinadream.com a Synchronet BBS

---
þ Synchronet þ Caught in a Dream - caughtinadream.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Dream Master wrote to Digital Man <=-

I think the problem with everyone young and in IT, whether developers
or sysadmins, is no longer being "useful". I spent too many years hoarding knowledge forcing me to be the subject matter expert on many areas. This bit me in the ass and I lost out on early promotions. We learn and that's all that matters.

I went from being a technical jack-of-all-trades to managing small teams to managing large teams, and then, after a layoff, going back to being Jack again. I'm glad I had those technical skills (and kept most of them while I was a people manager) in order to adapt and keep working.

Ah, yeah, just a few. It was fun to get that old code compiling and working again (post Y2K and all), using those old tools.

I missed the first part of this thread, but I downloaded Turbo Pascal and wanted to start playing with it again. Maybe some old-school ANSI C, too.

<snort> I believe there are so many things we as developers and
sysadmins did in the 80s and 90s that we truly regret. My favorites, "This program won't be needed past the 90s" or "we should get rid of
all the COBOL and Fortran programs. They cost too much."

Preach, brother. I remember when Numerical Recipes in FORTRAN came out with Numerical Recipes in C. It seemed like a lot more work for the same result, but you never saw a copy of Turbo FORTRAN at Egghead Software. :)






... Back in the stream that feeds the ocean that feeds the stream.
--- MultiMail/DOS v0.52
þ Synchronet þ realitycheckBBS -- http://realitycheckBBS.org
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)