TZUTC: -0500
MSGID: 26626.memoryln@1:2320/105 2c111125
REPLY: 1:153/757.21@fidonet 1d4989b0
PID: Synchronet 3.20a-Linux master/acc19483f Apr 26 202 GCC 12.2.0
TID: SBBSecho 3.20-Linux master/acc19483f Apr 26 2024 23:04 GCC 12.2.0
BBSID: CAPCITY2
CHRS: ASCII 1
>  >> Too bad there isn't a simple way to know what boards carry which echos.

>  MP> My way to know is if someone on that board posts in that echo.

> I mean, a way for a newbie exploring possible echos to know
> what boards carry it in the first place.

> Something akin to FILEFIND for files that probes participating
> BBSes, but instead ECHOFIND for echos and reports which BBSes
> carry a specific echo.

The GT Power Network (which used proprietary networking software) had a
third party add on that would report stats back to the NEC, who would
compile them once a month and distribute them.  It showed which boards
carried which echoes, although I do not believe it descerned between
"carried publicly" vs. skip/passthru.


 * SLMR 2.1a * Diagonally parked in a parallel universe.
--- SBBSecho 3.20-Linux
 * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
SEEN-BY: 50/22 103/705 104/119 105/81 106/201 120/302 616 124/5016
SEEN-BY: 128/187 129/305 153/757 7715 154/10 30 50 110 700 203/0 218/700
SEEN-BY: 220/20 90 221/0 6 226/18 30 44 50 227/114 229/110 114 206
SEEN-BY: 229/300 317 400 426 428 470 664 700 705 240/1120 5832 266/512
SEEN-BY: 280/464 5003 5006 291/111 292/854 301/1 310/31 320/219 322/757
SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 256 1124 467/888
SEEN-BY: 633/280 712/848 770/1 902/26 2320/0 105 3634/12 5020/400
SEEN-BY: 5020/8912 5054/30 5075/35
PATH: 2320/105 154/10 280/464 460/58 229/426