I had been asked to remove one of my downlinks from a specific echo due
to rule violations, which I did. My question is can I keep him from resubscribing to that particular echo? I have used levels for like
sysop specific etc would I have to do that? like set a write level on
that echo that matches everyone but him or is there a simpler way?
* Forwarded from area 'FIDOSOFT.HUSKY'
On 03 Apr 2024, Rick Smith said the following...
I had been asked to remove one of my downlinks from a specific
echo due to rule violations, which I did. My question is can I
keep him from resubscribing to that particular echo? I have used
levels for like sysop specific etc would I have to do that? like
set a write level on that echo that matches everyone but him or
is there a simpler way?
Check out the ReadOnly token:
3.5.16 ReadOnly
---------------
Syntax:
'ReadOnly <addressMask> <areaMask>'
Example:
'ReadOnly 2:5021/19.* tver.sysop*'
'ReadOnly 1:234/567 fidotest'
'ReadOnly 21:3/110.1 fsx_*'
I had been asked to remove one of my downlinks from a specific
echo due to rule violations, which I did. My question is can I
keep him from resubscribing to that particular echo? I have
used levels for like sysop specific etc would I have to do that?
Check out the ReadOnly token:
3.5.16 ReadOnly
Thanks Jay, I put that in this nodes link entry and it seem to accept
it, ran tparser and it didnt error so I will see whaat happens...
* Forwarded from area 'FIDOSOFT.HUSKY'
On 03 Apr 2024, Rick Smith said the following...
3.5.16 ReadOnly
---------------
Syntax:
'ReadOnly <addressMask> <areaMask>'
Example:
'ReadOnly 2:5021/19.* tver.sysop*'
'ReadOnly 1:234/567 fidotest'
'ReadOnly 21:3/110.1 fsx_*'
Using this they could still see the echo with %LIST and re-subscribe,
but it would be read only for them.
Sysop: | Nitro |
---|---|
Location: | Portland, OR |
Users: | 4 |
Nodes: | 10 (0 / 10) |
Uptime: | 218:10:34 |
Calls: | 139 |
Files: | 752 |
Messages: | 87,385 |