Hi there

This echoarea FSX_NET was created on 3 December 2019 in fsxNet

[snip]

Created FSX_NET - fsxNet is now just over 4 years old. This echoarea has been
created as a space for discussions about the network, its
current operations, plans for the future and how best to
implement them. Suggested topics include decentralization,
collaboration, promotion, membership, encrypted connectivity
mesh networking, new protocol development + implementation
etc.

[snip]

Best, Paul

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: fsxNet HUB (21:1/100)

On 03 Dec 2019 at 12:15p, Avon pondered and said...

On 02 Dec 2019 at 11:24a, Oli pondered and said...

Could we create a dedicated echomail area for this (and all the thing that were mentioned in the thread)? FSX_NETWORK, FSX_OPS, FSX_META or FSX_FTN, ...?

I find it hard to follow the discussions in FSX_GEN and I really woul prefer a low-traffic area. It also would work much better as an archi

More than happy to do this, and good idea. I'll work on something over
the next 24 hours. Once set up I'll forward the older messages from this thread into the new echo. Hopefully that will set us up nicely to
discuss, plan and expand on the topics being mooted.

Hi guys

From HISTORY.TXT

[snip]

2019-12-03
Created FSX_NET - fsxNet is now just over 4 years old. This echoarea has been
created as a space for discussions about the network, its
current operations, plans for the future and how best to
implement them. Suggested topics include decentralization,
collaboration, promotion, membership, encrypted connectivity
mesh networking, new protocol development + implementation
etc.

[snip]

This echoarea has just been created and should have auto created at the other HUBs. If not, sing out and let me know so I can chase things up.

The infopack etc. will be updated and changes reflected in the coming days
when it is next hatched.

If you want this echo you will need to link to it.

Best, Paul

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: fsxNet HUB (21:1/100)

This echoarea has just been created and should have auto created at
the other HUBs. If not, sing out and let me know so I can chase
things up.

Thanks Paul for creating the area.

10 minutes ago it was not available at 3/100.

---
* Origin: (21:1/151)

On 03 Dec 2019 at 09:45a, Oli pondered and said...

@SEEN-BY: 1/1 100 101 126 151 2/100 3/100 4/100 5/100
@PATH: 1/151 100

This echoarea has just been created and should have auto created at the other HUBs. If not, sing out and let me know so I can chase
things up.

Thanks Paul for creating the area.
10 minutes ago it was not available at 3/100.

You're most welcome Oli.

I'm a bit torn between letting everyone opt in or just linking everyone and letting folks opt out.

Sounds like Deon will sort NET 3 in the coming days.

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 03 Dec 2019, Avon said the following...

This echoarea has just been created and should have auto created at the other HUBs. If not, sing out and let me know so I can chase things up.

Hub 4 auto-created the area, and now that netmail is working, nodes can
areafix to connect to it.

Also 1/186 is connected. ;)

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)

On 12-04-19 12:48, Avon wrote to Oli <=-

I'm a bit torn between letting everyone opt in or just linking everyone and letting folks opt out.

I'm glad you made it opt in. That allowed me to have the area setup, then I could issue the Areafix and rescan. Doing it the other way would have meant that I missed messages, because attempting to rescan them would result in older mail being seen as dupes.


... Useless Invention: Reduced calorie water.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)