On 2017 Nov 06 19:55:48, you wrote to me:

 MR>>> Makes sense. We could also create a dedicated public echo for
 MR>>> technical discussions (read-only by default, read-write for FTSC
 MR>>> members)

 ml>> how is it proposed to enforce RO status on non-FTSC members? you do
 ml>> remember the mess(es) in FIDONEWS, FIDO_SYSOP and FN_SYSOP, right?

 MR> Who would be interested in watching the FTSC members? Mostly RCs, I'd
 MR> guess. That should be managaable. Or am I too optimistic?

it comes down to distribution... RO /might/ be possible with private
distribution but you're talking about creating another public echo... you'd
have to rely on all systems carrying the area to set it properly to preserve RO
status... even then you can't really rely on that as long as there are systems
blindly setting up their areas by importing .NA files without regard to certain
areas' distribution status...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... If croutons are stale bread, why do they come in airtight packages?
---