[Skimmertalk] Number in suffix

[N4ZR]

  If a majority of nodes worldwide use DXSpider, and DXSpider doesn't 
block weird formats, then it would follow that a majority of node users 
will see the 8N3 spots, whether they come from RBN nodes or other spotters.

The node I checked on was running Spider and carrying RBN spots, which I 
didn't think would work, but maybe there have been improvements to 
Spider's code.

The Skimmer Server code doesn't *preclude* spotting stations that do not 
conform with a pattern in the pattern file, it just requires more 
repetitions in the decoder channel before accepting it as a callsign.  
Ten years ago, I worked with Alex to gin up and test the matrix of 
possible callsign formats and required repetitions.

I just looked on the RBN website, and while 8G3G20 hasn't been spotted, 
there are loads of spots of 8N324A, a call structure that is not 
currently covered by the pattern file either.

73, Pete N4ZR
Check out the Reverse Beacon Network
at <http://reversebeacon.net>, now
spotting RTTY activity worldwide.
For spots, please use your favorite
"retail" DX cluster.

On 5/13/2019 11:56 AM, Bob Wilson, N6TV wrote:
> On Mon, May 13, 2019 at 8:21 AM N4ZR <n4zr at comcast.net 
> <mailto:n4zr at comcast.net>> wrote:
>
>     I just tested spotting 8N3G20 on a DXSpider and a VE7CC cluster. 
>     DXSpider let it through, while VE7CC did not.  I just finished
>     updating N1MM+'s cluster list, and in the process discovered that
>     a majority of clusters worldwide are using DXSpider, That suggests
>     to me that the impact of *not* adding this pattern on spotting of
>     the station will be relatively small.
>
> As written, these statements seem to contradict each other.  If most 
> clusters use DXSpider, and DXSpider lets 8N3G20 through OK, then the 
> impact of *not* adding a pattern for the special callsigns will be 
> relatively LARGE, because then 8N3G20 and the others will NEVER be 
> spotted by /any/ skimmer cluster.  This doesn't seem right to me.
>
> 73,
> Bob, N6TV