Subj : Re: Weekly nodelist report on noteworthy changes (059)
To   : Dan Clough
From : Wilfred van Velzen
Date : Sat Mar 08 2025 17:38:03

Hi Dan,

On 2025-03-08 08:55:03, you wrote to me:

 WvV>> I think most people don't know the details, and just put XA in the
 WvV>> list. :-(

 WvV>> In the Z2 nodelist epilog
 WvV>> (http://many-glacier.dyndns.org/nodelist/NODELIST.066), there is a nice
 WvV>> table for these flags.

 WvV>> And you should know, when a node is IBN only it can only support the
 WvV>> WaZOO protocol. That narrows it down a lot! And leaves only XW and XX,
 WvV>> and the choice comes down to the implementation details of the freq
 WvV>> processor used by a node.

 DC> Thank you for this information, as I am thinking about adding FREQ
 DC> capability to my system (running Synchronet).

Ok.

 DC> Can you tell me how you know that IBN-only can only use the WaZOO
 DC> protocol?

I educated myself when I was wondering about these flags. ;-)

Bark is an extension to the FTS-0001 (modem) protocol. Binkp is a completely different protocol, so by definition it can not speak bark.

Bark is described in this document: http://ftsc.org/docs/fts-0008.003

 DC> I'm unable to find any info on that.

I started on the ftsc website, and searched for 'bark'...

Btw: Wazoo file requests are described in: http://ftsc.org/docs/fts-0006.002

And that basically is sending .req files. And as any mailer can send files, binkd can support file request, if you install a (external) file request processor.

 DC> Also how can we tell that BinkIT/FreqIT cannot do update requests
 DC> (XX)?

I tested this, and later confirmed it with Rob.

 DC> General info on Bark/WaZOO would also be nice to read about.

See above...


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
 * Origin: NPC Station (2:280/464)

.