REPLY: 1:229/426 63575177
MSGID: 1:3634/12.73 61d34a8d
PID: GED+LNX 1.1.5-b20180707
CHRS: CP437 2
TZUTC: -0500
TID: hpt/lnx 1.9.0-cur 17-02-17
 On 2022 Jan 03 12:06:02, you wrote to me:

 ML>> Z1_BACKBONE is the public facing echo where moderators request cartage
 ML>> or removal of their echo(s) on/from the backbone stars as part of the
 ML>> backbone traffic... when a cartage request is accepted, the area is
 ML>> then added to th

 NA> I thought the purpose of the Elist was for adding some new area that the
 NA> star systems automatically add... or remove when expired?

yes and no... the backbone doesn't automatically add areas to its
distribution... the moderators need to request cartage of their echo if they
want it on the/a backbone... this is because some moderators prefer to be more
in control over the distribution of their echo... the echolist, itself, is
simply a tool that backbones can use... it is a central database of echotags
and their related data... any FTNs and moderators that desire to use it can do
so... it is separate and distinct from any/all backbone(s)...

the backbone(s) use the elist as a tool for a couple of things...

  1. the backbone(s) require echos /on/ the backbone (aka
     listed in backbone.na) to be echolisted and the
     moderator of record to make a request for cartage as
     per #2... if an echo falls off the echolist, it is
     removed from the backbone after a grace period has
     elapsed... this gives the moderator a chance to get
     the echo updated or readded to the echolist...

  2. the request for cartage on the backbone is done by the
     moderator of record posting the echolist's *reply* to
     their MOD-ADD or MOD-UPD post in the echolist...
     for this particular backbone, this is done in the
     Z1_BACKBONE echo... other backbones had their own
     echos and procedures but many use(d) these same
     methods...

  3. to determine, when necessary, who the moderator of an
     echo really is... generally this is when the backbone
     has received an elevated feed cut request in an attempt
     to remove an individual from an echo... this generally
     only happens when the feed cut requests to lower level
     feeding systems in the PATH are not honored...

somewhere around here i still have a copy of the backbone operations and
procedures document... i haven't laid my hands on it in a quick five minute
search, though...

 NA> In any case, thanks for your feedback on the rest of my message.

you're welcome...

)\/(ark

"The soul of a small kitten in the body of a mighty dragon. Look on my
majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a
shiny thing!"
... Hocks.... it's like pig candy.
---
 * Origin:  (1:3634/12.73)
SEEN-BY: 1/120 18/0 123/0 153/7715 229/426 250/1 275/100 640/1321
SEEN-BY: 3634/0 12
PATH: 3634/12 153/7715 229/426