Hello All!

I do encourage submissions for echo's not currently listed that may be on the non-backbone backbone if they are active and/or some one will be promoting them
in one or more of the various advert echo's.

You may submit these in the the name of ElistMaint / elistmaint (text case immaterial to me as a email or netmail included (.ECO) type file content and I will include them as soon as I modify the elist sources to cater for this.

Using emlistmaint is a catch all without the requirement of having to take over
an echo area but allows any one interested in doing so to look after any such listings.

It would help if there is a system acting as an origin/source for a echo to specify it on the - wait for it, using the keyword ORIGin :)

The idea is to make elist have a more full view of echo's that are out there that can be made available to all via the 'backbone' Hub system.

For example Dallas Hinton has around 900+ areas (some of which are usegroup type areas but the rest look - well dead or should be as they relate to very dead software - where the vendors have long gone but the others might well come
back to life.

Small point, just because a echo is dead for a period say 12 months does not mean it cannot come back to life with a bit of promotion (adverts etc) how ever
may be 2 years, it should be considered DOA. Thoughts?

Don't forget the elist system can handle other nets other than Fido just add them in with the Network name defined as required and the three reporting files
will be generated at the same time as Fido and the current addition FSX.
Please use where ever possible the standard short designation for the network name, even more so if it has a long name. The software has a list of these other networks (that can be added too) that I list here showing the short and long names (note that one has a possible extra long name) :

--
"ADV" "ADVNET"
"FIDO" "FIDONET"
"FMLY" "FMLYNET"
"FSX" "FSXNET"
"GAMES" "GAMESNET"
"GATOR" "GATORNET"
"GMS" "GMSNET"
"JUSTAX" "JUSTAXNET"
"LEAGUE10" "LEAGUE10NET"
"LINUX" "LINUXNET"
"MICRO" "MICRONET"
"PASCAL" "PASCALNET"
"RMINI" "RMININET"
"SDS" "SDSNET"
"STN" "STNNET" "STNET"
"VIR" "VIRNET"
"XNET"
"ZENET"
"ZYXEL" "ZYXELNET".
--

If there is any missing send a netmail or email and advise.
Netmail to 2:25/21 or 2:250/1 or a email to vbcoen <at> gmail.com.

More the merrier. All helps to make the elist reports a more full and inclusive system for the benefit of all sysops / users.

Just a thought, or two.

For those that might be interested in the sources for the elist system the current version can always be found at :

http://www.applewoodbbs.linkpc.net/files/Elist/nightly-builds

They are updated automatically when ever there is a change - as far as I know.

Vincent
elist maintainer

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hello Vincent Coen!

** On Sunday 09.01.22 - 16:29, Vincent Coen wrote to All:

Don't forget the elist system can handle other nets other than Fido just add them in with the Network name defined as required..

--
"ADV" "ADVNET"
"FIDO" "FIDONET"
"FMLY" "FMLYNET"
"FSX" "FSXNET"

Does the ELIST system accomodate a tagname that bears exactly
the same tagname used in an othernet?

--
../|ug
--- OpenXP 5.0.51
* Origin: (2:221/1.58)

Hello August!

Sunday January 09 2022 14:34, you wrote to me:

Hello Vincent Coen!

** On Sunday 09.01.22 - 16:29, Vincent Coen wrote to All:

Don't forget the elist system can handle other nets other than
Fido just add them in with the Network name defined as required..

--
"ADV" "ADVNET"
"FIDO" "FIDONET"
"FMLY" "FMLYNET"
"FSX" "FSXNET"

Does the ELIST system accomodate a tagname that bears exactly
the same tagname used in an othernet?

Yes it should as the system stores the information in Tagname within network.

but let me know if it produces a error or anything else he says checking the code -

Snippit :

--
03 EList-Key. *> Alternate key
05 Elist-Group pic x(16). *> FIDO, other networks ?
05 Elist-TAG pic x(36). *> Echo tagname | KEY (Alternate)
--

Yes, they are unique.

That does not mean they are also within a specific bbs system though, in mbse it is valid as echos are controlled and processed echo within group and providing group is network or the equivalent.

For mbse and possibly other systems group valid echos are taken from a file containing lists of echo tags and descriptions i.e., backbone.na

Yes I know it is hardly up to date but it is all there is and I do manually update it.

Notice that the tagname is 36 characters and not as indicated in some other docs as 50 or so - most BB systems do not even allow for 36.

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)