Hello Al!

** On Sunday 31.05.20 - 17:41, Al wrote to Ogg:

Today, the onus is on the sysop to do a little legwork/marketing to
promote the areas.

Are you sure? :)

I think it's upto the owner/creator of the area to first create and link interested nodes to the area and then it can grow from there into as wide
a distrubution as you'd like.

My original statement was addressed within the scope of fsxnet. It seems that in this net, the creation and rule of an echo are the same person
that maintains this othernet.

We agree that the "onus" to maintain the life/participation/activity of an echo is upon whoever spearheads the echo.

The above is the way echoes start in Fidonet at least. I'm not sure if that's true in fsxNet. In Fidonet there are a few steps that need to
be taken for elisting and backbone addition if that is desired but I
think that would be simpler in fsxNet.

In Fidonet, anyone can start an echo. Then, the trick is to get the word around. That is what the ELIST bot attempts to accomplish. Sysops then
pick and choose what they want to carry or what their users ask for.

I would be happy to add FSX_??? to my setup and link your node as a
start. Avon would need to add the area to fsxNet also and the hubs
would need to add the area also and let everyone know the area is available.

Technically, there would be nothing from stopping me from creating a new FSX_whatever echo area here, post to it and send it to you. But then, it would not be proper to just distribute it to the rest of the net without
some approval of the netcreator.

I recall seeing an FSX_JOKES echo (and it wasn't a file echo) at a BBS, somehwere. The echo was labelled "Local", so it didn't get distributed.

Likely a much simpler thing to do in fsxNet than Fido but in any case
let me know if I can help in any way.

FSXnet is very flexible and accomodating. Meanwhile, there are plenty of areas on othernets to explore too.


--- OpenXP 5.0.44
* Origin: (} Pointy McPointFace (21:4/106.21)