[Dxspider-support] VarAC Beacon spots

[Joaquin]

I have sent a couple of emails to the Spanish developer EA5HVK and to 
the Israeli 4Z1AC indicating that the VarAC software is making improper 
use of the spots and the possible discomfort of the network sysops, and 
advising them to use the cluster chat.
So far I have not received a response from any.
We will wait for news...

Kin EA3CV


El 06/12/2022 a las 23:27, Laurie, VK3AMA via Dxspider-support escribió:
> A brief history lesson on ROSMODEM and its developer.
>
>   * The ROS software would post spots to DXSpider nodes pretending to
>     be a human using a number of different inbuilt message types to
>     give the impression the spots were human originating. The volume
>     of spots and the repeated spot formats gave that away.
>   * While running the software, monitoring activity only, no QSOs, the
>     software would be posting spots giving the impression that the
>     spot was for an actual QSO when there was no QSO.
>   * As nodes started to implement registration to block this behavior
>     the ROS software would be updated with differing lists of
>     unsecured nodes to auto-spot to.
>   * When the ROS author was called out about the auto-spotting he
>     started to include hard-coded list of the callsigns reporting this
>     behavior, a blacklist of callsigns that were prevented from
>     running the software. I know because I ended up on the blacklist
>     because of calling him out about his software activity. It was
>     easy to see the hard-coded blacklist, DXSpider nodes and auto-spot
>     message formats by simply doing a hex-dump of the ROS executable.
>
> Just a warning.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20221207/3362d88f/attachment.htm>