TZUTC: -0700
MSGID: 58748.sync_sys@1:103/705 2d60da3f
PID: Synchronet 3.21a-Linux master/88b423313 Sep 29 2025 GCC 12.2.0
TID: SBBSecho 3.30-Linux master/88b423313 Sep 29 2025 GCC 12.2.0
BBSID: VERT
CHRS: UTF-8 4
FORMAT: flowed
https://gitlab.synchro.net/main/sbbs/-/issues/995#note_7770

> It customary for the BBS software to identify itself during connection which
I think is also a useful diagnostic.

My point is that even of those three lines were removed, the BBS would still
identify itself during the connection. It currently identifies itself twice.

> Most Synchronet sysops want their systems listed in the Synchronet BBS
lists, so I’m not in favor of giving them a foot gun to defeat that nor hide
or disguise what BBS software is in use.

Again, the VERSION_NOTICE, COPYRIGHT_NOTICE in answer.cpp would still be there.

> I’m not in favor of giving them a foot gun to defeat that nor hide or
disguise what BBS software is in use.

I'm not requesting either of those things. It's pretty clear from the BBS list
page that the scanning process gets past the second version message.
--- SBBSecho 3.30-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 10/0 1 102/401 103/1 13 17 705 105/81 106/201 124/5016 128/187
SEEN-BY: 129/14 153/7715 154/110 214/22 218/0 1 215 601 610 700 840
SEEN-BY: 218/860 880 226/30 227/114 229/110 206 317 400 426 428 470
SEEN-BY: 229/700 705 266/512 280/464 291/111 301/1 320/219 322/757
SEEN-BY: 342/200 396/45 460/58 633/280 712/848 902/26 5075/35
PATH: 103/705 218/700 229/426