open https://gitlab.synchro.net/main/sbbs/-/issues/826

I notice thar areas.bbs have duplicates when add passthrough areas:

{width=882 height=517}

```
2024-11-17 18:00:23 SBBSecho 3.22-Linux master/9bf86ab10 nov 16 2024 21:25 GCC 10.2.1 (PID 2332106) invoked with options: -lesrby!
2024-11-17 18:00:23 Configured: 7 archivers, 55 linked-nodes, 12 echolists 2024-11-17 18:00:23 NetMail directory: /sbbs/fido/netmail/
2024-11-17 18:00:23 Secure Inbound directory: /sbbs/fido/inbound/
2024-11-17 18:00:23 Non-secure Inbound directory: /sbbs/fido/inbound.nosecure/ 2024-11-17 18:00:23 Outbound (BSO root) directory: /sbbs/fido/outbound/ 2024-11-17 18:00:23 DUPLICATE AREA (LIVE_AUDIO) in area file (../data/areas.bbs), IGNORED!
2024-11-17 18:00:23 DUPLICATE AREA (VATICAN) in area file (../data/areas.bbs), IGNORED!
2024-11-17 18:00:23 DUPLICATE AREA (YAHOONEWS) in area file (../data/areas.bbs), IGNORED!
2024-11-17 18:00:23 Read 683 areas from ../data/areas.bbs
2024-11-17 18:00:23 Read 0 areas from ../data/badareas.lst
2024-11-17 18:00:25 Read 663 echo statistics from ../data/echostats.ini 2024-11-17 18:00:25 Unpacking bundle: /sbbs/fido/inbound/3a598a00.su0 (4.2KB) ```
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6016

Do you know how to reproduce this issue?

I have a lot of pass-through areas in my areas.bbs and have a decent amount of AreaManager requests and have not seen this issue (I have no duplicate areas).
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6017

to whishlist:

I think that areas.bbs should honor the ini format as is the trend of the rest of the configuration files

for example:

```ini
[sbbs_internal_code]
tag=fido_tag
link=1:123/4
link=2:345/6
link=3:456/6

[sbbs_internal_code]
tag=fido_tag
link=1:123/4
link=2:345/6
link=3:456/6
```

this would make it easier to parse and you could even think of making an "Area manager" GUI with javascript and uifc or within sbbsecho

or from the command line it could also have utilities like:

```
jsexec areamgr.js addarea [internal_code] [fido_tag] [link] [link]
jsexec areamgr.js addlink [fido_tag] [link]
jsexec areamgr.js dellink [fido_tag] [link]

```
etc...
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6018

I can't reproduce it yet
but the context is that now my sbbs is the Z4 hub so I have links with ward, scott and nike andre for the other zones
and I also have nodes (downlinks) from various networks 4:90/0 4:900/0 etc.. and they have their own nodes and even points. that's more or less the current structure
In general everything works fine for now but I found this duplicate.
I'm going to keep investigating to see how to reproduce it
If it helps I can share my sbbsecho/anothers configurations
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6018

I can't reproduce it yet
but the context is that now my sbbs is the Z4 hub so I have links with ward, scott and nike andre for the other zones.

And I also have nodes (downlinks) from various networks 4:90/0 4:900/0 etc..

And they have their own nodes and even points.

That's more or less the current structure

In general everything works fine for now but I found this duplicate.
I'm going to keep investigating to see how to reproduce it
If it helps I can share my sbbsecho/anothers configurations
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6018

I can't reproduce it yet
but the context is that now my sbbs is the Z4 hub so I have links with ward, scott and nike andre for the other zones.

And I also have nodes (downlinks) from various networks 4:90/0 4:900/0 4:930/0 etc..

And they have their own nodes and even points.

That's more or less the current structure

In general everything works fine for now but I found this duplicate.
I'm going to keep investigating to see how to reproduce it
If it helps I can share my sbbsecho/anothers configurations
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6017

to whishlist:

I think that areas.bbs should honor the ini format as is the trend of the rest of the configuration files

for example:

```ini
[sbbs_internal_code]
tag=fido_tag
link=1:123/4
link=2:345/6
link=3:456/6

[sbbs_internal_code]
tag=fido_tag
link=1:123/4
link=2:345/6
link=3:456/6

[passthrough]
tag=fido_tag
link=1:123/4
link=2:345/6
link=3:456/6

[passthrough]
tag=fido_tag
link=1:123/4
link=2:345/6
link=3:456/6

```

this would make it easier to parse and you could even think of making an "Area manager" GUI with javascript and uifc or within sbbsecho

or from the command line it could also have utilities like:

```
jsexec areamgr.js addarea [internal_code] [fido_tag] [link] [link]
jsexec areamgr.js addlink [fido_tag] [link]
jsexec areamgr.js dellink [fido_tag] [link]

```
etc...
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Fernando Toledo wrote to GitLab note in main/sbbs <=-

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6017

to whishlist:

I think that areas.bbs should honor the ini format as is the trend of
the rest of the configuration files

for example:

[sbbs_internal_code]
tag=fido_tag
link=1:123/4
link=2:345/6
link=3:456/6

[passthrough]
tag=fido_tag
link=1:123/4
link=2:345/6
link=3:456/6

I disagree. I think this format is MUCH more awkward than the current
format of AREAS.BBS. If you have several hundred echo areas, and a
couple dozen downlinks for most of them, the file would be *VERY* long
and hard to edit. EXTREMELY hard to edit, actually.

Also, that file is not specific to Synchronet only.

this would make it easier to parse and you could even think of making
an "Area manager" GUI with javascript and uifc or within sbbsecho

or from the command line it could also have utilities like:

jsexec areamgr.js addarea [internal_code] [fido_tag] [link] [link]
jsexec areamgr.js addlink [fido_tag] [link]
jsexec areamgr.js dellink [fido_tag] [link]

This can already be done with the Import/Export functions already in
SCFG.



... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

El 17/11/24 a las 22:49, Gamgee escribió:

I disagree. I think this format is MUCH more awkward than the current
format of AREAS.BBS. If you have several hundred echo areas, and a
couple dozen downlinks for most of them, the file would be *VERY* long
and hard to edit. EXTREMELY hard to edit, actually.

I understand your point, but using a more standard format makes it
easier to create tools that manage the file

The length of the file due to the number of areas is not something that worries me. If I have to edit it manually, any editor can do a text
search quickly, even if it has thousands of lines.

Also, that file is not specific to Synchronet only.

FT> this would make it easier to parse and you could even think of making
FT> an "Area manager" GUI with javascript and uifc or within sbbsecho

FT> or from the command line it could also have utilities like:

FT> jsexec areamgr.js addarea [internal_code] [fido_tag] [link] [link]
FT> jsexec areamgr.js addlink [fido_tag] [link]
FT> jsexec areamgr.js dellink [fido_tag] [link]

This can already be done with the Import/Export functions already in
SCFG.

The import/export actions to different formats are not for managing the
file.
I don't see a way to simple make those use cases as this:

"add node 1:23/4 to areas X,Y and Z"
"remove node 1:23/4 from area X"

The ini format was just an example, maybe it could be a comma or tab
separated file like user.tab is now

I currently use sed, awk or other bash tools to do these tasks. But the inconsistencies of the lines (some have different spaces between the
columns) makes it uncomfortable.

Saludos!
---
ï¿­ Synchronet ï¿­ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: ares.bbs got duplicate areas on passthrough
By: Fernando Toledo to GitLab note in main/sbbs on Sun Nov 17 2024 16:21:13

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6017

to whishlist:

I think that areas.bbs should honor the ini format as is the trend of the rest of the configuration files

No, that'd be too much of a pain to edit by hand. Now it easy just to copy and paste a line and be done with it. I would not support that change.

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Ragnarok wrote to All <=-

El 17/11/24 a las 22:49, Gamgee escribi}|:

I disagree. I think this format is MUCH more awkward than the current format of AREAS.BBS. If you have several hundred echo areas, and a
couple dozen downlinks for most of them, the file would be *VERY* long
and hard to edit. EXTREMELY hard to edit, actually.

I understand your point, but using a more standard format makes it
easier to create tools that manage the file

We already have tools to manage it. Text editors.

The length of the file due to the number of areas is not something that worries me. If I have to edit it manually, any editor can do a text
search quickly, even if it has thousands of lines.

OK, so why would we need any additional tools?

Also, that file is not specific to Synchronet only.

FT> this would make it easier to parse and you could even think of making
FT> an "Area manager" GUI with javascript and uifc or within sbbsecho

FT> or from the command line it could also have utilities like:

FT> jsexec areamgr.js addarea [internal_code] [fido_tag] [link] [link]
FT> jsexec areamgr.js addlink [fido_tag] [link]
FT> jsexec areamgr.js dellink [fido_tag] [link]

This can already be done with the Import/Export functions already in
SCFG.

The import/export actions to different formats are not for managing the file.

Sure they are. For example, you add a whole new FTN network, and then
you can simply export it to update (add to) the existing AREAS.BBS.

I don't see a way to simple make those use cases as this:

"add node 1:23/4 to areas X,Y and Z"
"remove node 1:23/4 from area X"

That's true, the import/export isn't for that. But, see above regarding
text editors. Very simple thing to do.

The ini format was just an example, maybe it could be a comma or tab separated file like user.tab is now

I currently use sed, awk or other bash tools to do these tasks. But the inconsistencies of the lines (some have different spaces between the columns) makes it uncomfortable.

While those tools are useful, they're probably more trouble than they're
worth for something like this. You can easily edit the file with your preferred text editor, and while you're in there, fix the spacing/tabs
to make it look the way you want it to. Not difficult.

My whole point is that the existing format is very simple and efficient,
and is EASY to edit. Why complicate it just to "justify" the creation
of more "tools" we could use? We already have the tools.



... Gone crazy, be back later, please leave message.
--- MultiMail/Linux v0.52
þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6021

You can't have multiple .ini file sections with the same section name (e.g. `[passthrough]`), so I think the echo-tag would have to be section name.
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6022

Sure, it was just an example/idea anyway but it could be:

[ECHO_TAG]
code=fidonet_internalcode
passthrough=1 (or 0)
link=1:234/4
link=2:345/6

or like this:

[ECHO_TAG]
code=fidonet_internalcode
passthrough=1 (or 0)
links=1:234/4, 2:234/6, 4:56/7.8
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6023

Yes. We can't have duplicate key names either, so the list of links is probably more practical. I think it's a fine idea, as an option, at least.
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

El 18/11/24 a las 10:56, Gamgee escribió:

Ragnarok wrote to All <=-

Ra> El 17/11/24 a las 22:49, Gamgee escribi}|:

We already have tools to manage it. Text editors.

OK, so why would we need any additional tools?

Maybe I explained myself badly (sorry, but English is not my native
language).
I don't want new tools on a whim. I love editors and plain text is one
of the best formats in the world.

What has happened is that now I find myself with different use cases.
Until a few weeks ago I was a simple ftn node running sbbs with some
networks and some points

These days, my system has become a fidonet Z4 master node. So I have
found that I have to perform these other tasks that I didn't do before,
at least for now.

The sbbs area manager via scfg is perfect for bbs, but what I'm getting
at is that I also have to manage my downlink nodes.

I don't know if there is anyone else who uses sbbs at ZC level (of any
ftn) since I would like to know their experience.

I repeat, I can continue using my mcedit to continue maintaining the
areas... I just started this discussion to see if those aspects of sbbs
can be improved (Which by the way is the best bbs software I know).

Hugs!
---
ï¿­ Synchronet ï¿­ Dock Sud BBS TLD 24 HS - bbs.docksud.com.ar
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6024

Regarding the reported problem, do you have `AutoAddToAreaFile` set to `true` in your `sbbsecho.ini` file?

If yes, can you search your `sbbsecho.log` file for occurrences of the text: "Adding sub-board (x) to Area File y with uplink z, tag: t" and see if maybe the duplicate areas were "auto-added"?
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6025

I use that options as Yes

{width=423 height=263}

also I use echo lists to limit the echo visibility to different nodes/networks --- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6025

I use that options as List/File

{width=423 height=263}

also I use echo lists to limit the echo visibility to different nodes/networks --- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6026

I found some lines but it seems to be unrelated to these dupes

```
2024-10-21 12:31:41 Adding sub-board (fidonetaarp_fraud ) to Area File with uplink 4:90/1, tag: AARP_FRAUD
2024-10-21 12:31:41 Adding sub-board (fidonetbbachconinfo ) to Area File with uplink 4:90/1, tag: BBACH.CON.INFO
2024-10-21 12:31:41 Adding sub-board (fidonetgecho_help ) to Area File with uplink 4:90/1, tag: GECHO_HELP
2024-10-21 12:31:41 Adding sub-board (fidonetmozillasupportfi ) to Area File with uplink 4:90/1, tag: MOZILLA.SUPPORT.FIREFOX
2024-10-21 12:31:41 Adding sub-board (fidonetnsksysop ) to Area File with uplink 4:90/1, tag: NSK.SYSOP
2024-10-21 12:31:41 Adding sub-board (fidonetrootest ) to Area File with uplink 4:90/1, tag: ROO.TEST
2024-10-21 12:31:41 Adding sub-board (fidonetrusnews ) to Area File with uplink 4:90/1, tag: RUS.NEWS
2024-10-21 12:31:41 Adding sub-board (fidonetsuancientlife ) to Area File with uplink 4:90/1, tag: SU.ANCIENT.LIFE
2024-10-21 12:31:41 Adding sub-board (fidonetsuastronomy ) to Area File with uplink 4:90/1, tag: SU.ASTRONOMY
2024-10-21 12:31:41 Adding sub-board (fidonetsuformula1 ) to Area File with uplink 4:90/1, tag: SU.FORMULA1
2024-10-21 12:31:41 Adding sub-board (fidonetsuhardw ) to Area File with uplink 4:90/1, tag: SU.HARDW
2024-10-21 12:31:41 Adding sub-board (fidonetsuhardwchainik ) to Area File with uplink 4:90/1, tag: SU.HARDW.CHAINIK
2024-10-21 12:31:41 Adding sub-board (fidonetsukaschenkogloba ) to Area File with uplink 4:90/1, tag: SU.KASCHENKO.GLOBAL
2024-10-21 12:31:41 Adding sub-board (fidonetsuphilosophy ) to Area File with uplink 4:90/1, tag: SU.PHILOSOPHY
2024-10-21 12:31:41 Adding sub-board (fidonetsupolfree ) to Area File with uplink 4:90/1, tag: SU.POL.FREE
2024-10-21 12:31:41 Adding sub-board (fidonetsusoftw ) to Area File with uplink 4:90/1, tag: SU.SOFTW
2024-10-21 12:31:41 Adding sub-board (fidonetsutolkien ) to Area File with uplink 4:90/1, tag: SU.TOLKIEN
2024-10-21 12:31:41 Adding sub-board (fidonetwest-vlaamsreg ) to Area File with uplink 4:90/1, tag: WEST-VLAAMS.REG
2024-10-21 12:31:41 Adding sub-board (fidonetwwiv ) to Area File with uplink 4:90/1, tag: WWIV

```

So, I'll pay more attention when it happens so I can see the log of that moment.
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/826#note_6026

I found some old lines but it seems to be unrelated to these dupes

```
2024-10-21 12:31:41 Adding sub-board (fidonetaarp_fraud ) to Area File with uplink 4:90/1, tag: AARP_FRAUD
2024-10-21 12:31:41 Adding sub-board (fidonetbbachconinfo ) to Area File with uplink 4:90/1, tag: BBACH.CON.INFO
2024-10-21 12:31:41 Adding sub-board (fidonetgecho_help ) to Area File with uplink 4:90/1, tag: GECHO_HELP
2024-10-21 12:31:41 Adding sub-board (fidonetmozillasupportfi ) to Area File with uplink 4:90/1, tag: MOZILLA.SUPPORT.FIREFOX
2024-10-21 12:31:41 Adding sub-board (fidonetnsksysop ) to Area File with uplink 4:90/1, tag: NSK.SYSOP
2024-10-21 12:31:41 Adding sub-board (fidonetrootest ) to Area File with uplink 4:90/1, tag: ROO.TEST
2024-10-21 12:31:41 Adding sub-board (fidonetrusnews ) to Area File with uplink 4:90/1, tag: RUS.NEWS
2024-10-21 12:31:41 Adding sub-board (fidonetsuancientlife ) to Area File with uplink 4:90/1, tag: SU.ANCIENT.LIFE
2024-10-21 12:31:41 Adding sub-board (fidonetsuastronomy ) to Area File with uplink 4:90/1, tag: SU.ASTRONOMY
2024-10-21 12:31:41 Adding sub-board (fidonetsuformula1 ) to Area File with uplink 4:90/1, tag: SU.FORMULA1
2024-10-21 12:31:41 Adding sub-board (fidonetsuhardw ) to Area File with uplink 4:90/1, tag: SU.HARDW
2024-10-21 12:31:41 Adding sub-board (fidonetsuhardwchainik ) to Area File with uplink 4:90/1, tag: SU.HARDW.CHAINIK
2024-10-21 12:31:41 Adding sub-board (fidonetsukaschenkogloba ) to Area File with uplink 4:90/1, tag: SU.KASCHENKO.GLOBAL
2024-10-21 12:31:41 Adding sub-board (fidonetsuphilosophy ) to Area File with uplink 4:90/1, tag: SU.PHILOSOPHY
2024-10-21 12:31:41 Adding sub-board (fidonetsupolfree ) to Area File with uplink 4:90/1, tag: SU.POL.FREE
2024-10-21 12:31:41 Adding sub-board (fidonetsusoftw ) to Area File with uplink 4:90/1, tag: SU.SOFTW
2024-10-21 12:31:41 Adding sub-board (fidonetsutolkien ) to Area File with uplink 4:90/1, tag: SU.TOLKIEN
2024-10-21 12:31:41 Adding sub-board (fidonetwest-vlaamsreg ) to Area File with uplink 4:90/1, tag: WEST-VLAAMS.REG
2024-10-21 12:31:41 Adding sub-board (fidonetwwiv ) to Area File with uplink 4:90/1, tag: WWIV

```

So, I'll pay more attention when it happens so I can see the log of that moment.
--- SBBSecho 3.22-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)