TZUTC: -0500
MSGID: 74352.sync@723:320/1 2d770f35
REPLY: 55251.sync@1:103/705 2d75fbdd
PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0
TID: SBBSecho 3.31-Linux master/d39e01091 Nov 03 2025 GCC 12.2.0
BBSID: CAPCITY2
CHRS: CP437 2
FORMAT: flowed
>  > >  > Regards, Nick

>  > > too bad he didnt post the system pass, i could have fixed some stuff.

>  > Just because *you* don't like it doesn't make it broken.

> yeah ooookay.  i just dont like broken things.

As I said, just because you don't like it doesn't make it broken.

As you are the only one whose ever complained, I would suggest the problem
is elsewhere -- and very much not mine.

OTOH, I originally had Synchronet set up so that all the message areas were
grouped by network -- which is how you like it -- and users (plural) did
complain because they couldn't find the "echoes about (subject)" that they
were used to participating in on the predecessor BBS.

When a user isn't either pissed at the network admins, or banned by then,
which networks you want/need to avoid isn't an issue.


 * SLMR 2.1a * Light at end of tunnel temporarily out of order.
---
 þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 129/14 153/757 7715
SEEN-BY: 154/10 30 110 203/0 218/700 221/0 226/30 227/114 229/110
SEEN-BY: 229/112 206 317 400 426 428 470 700 705 240/1120 5832 263/1
SEEN-BY: 266/512 280/464 5003 5006 291/111 292/8125 301/1 310/31 320/219
SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124
SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 8912 5054/30 5075/35
PATH: 103/705 280/464 460/58 229/426