@MSGID: 1:105/81@fidonet 660eb05c
@REPLY: 1:229/664 0583bce4
@CHRS: UTF-8 2
@TZUTC: -0700
Hello Jay!

Thursday April 04 2024 08:57, you wrote to me:

 JH>  * Forwarded from area `FIDOSOFT.HUSKY`
 JH> On 03 Apr 2024, Rick Smith said the following...

 RS>> I had been asked to remove one of my downlinks from a specific
 RS>> echo due to rule violations, which I did.  My question is can I
 RS>> keep him from resubscribing to that particular echo?  I have used
 RS>> levels for like sysop specific etc would I have to do that? like
 RS>> set a write level on that echo that matches everyone but him or
 RS>> is there a simpler way?

 JH> Check out the ReadOnly token:

 JH> 3.5.16 ReadOnly
 JH> ---------------
 JH> Syntax:
 JH>      `ReadOnly  `
 JH> Example:
 JH>      `ReadOnly 2:5021/19.* tver.sysop*`
 JH>      `ReadOnly 1:234/567 fidotest`
 JH>      `ReadOnly 21:3/110.1 fsx_*`

 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...

Regards,

Rick

... Citation for slow BBSing:  Going v.32bis in a v.FC lane
--- GoldED+/LNX 1.1.5-b20180707
 * Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)
SEEN-BY: 1/120 15/0 18/0 50/109 90/1 104/117 105/7
10 11 44 81 85 500 106/201
SEEN-BY: 116/116 123/0 25 160 180 200 755 3001
128/260 135/115 220 225
SEEN-BY: 138/146 153/757 7715 154/10 218/700 221/6
222/2 226/30 227/114
SEEN-BY: 229/110 112 113 206 307 317 426 428 470
664 700 240/1120 250/1
SEEN-BY: 261/38 266/512 275/100 1000 282/1038
291/111 292/854 299/6 301/1
SEEN-BY: 320/219 322/757 342/11 200 396/45 452/28
166 460/58 463/68 467/888
SEEN-BY: 633/280 712/848 1321 1321 2320/105 3634/0
12 27 57 119 5000/111
SEEN-BY: 5005/49 5010/352 5015/46 5019/40 5020/715
828 846 848 1042 4441
SEEN-BY: 5020/12000 5030/49 1081 5053/51 5054/8
5061/133 5075/35 128 5083/444
@PATH: 105/81 229/426 153/7715 3634/12 5020/1042
4441