[Skimmertalk] [cwops] CW Open and the RBN

[Douglas Zwiebel]

Steve,

Will be interesting to see how many busted callsigns made it into the
"other guys' " logs for your QSO's.  Hopefully, the vast majority of guys
are not RBN believers and would have heard you sending your callsign
perfectly spaced.  In CQWW, I am always amazed at many (most?) M/M entries
who blindly work and log an RBN busted call....even with the CT1BOH
filtering available.  Point and shoot...don't bother to listen.

de Doug KR2Q

On Sun, Sep 5, 2021 at 10:19 AM Steve London <n2ic at arrl.net> wrote:

> Please define "insufficient space".
>
> Here was the only CQ message I used: cq cwo n2ic
>
> Exactly one character space between each element. YCCC SO2R Box Winkey
> emulation used. Local, not remote operation.
>
> I was repeatedly spotted as ON2IC.
> Skimmer issue ?
>
> 73,
> Steve, not ON2IC
>
> On Sun, Sep 5, 2021 at 7:13 AM Pete Smith N4ZR <pete.n4zr at gmail.com>
> wrote:
>
>> I ran into an interesting phenomenon using RBN spots in the CWO. Several
>> stations were repeatedly mis-decoded by the RBN, and I think the cause
>> probably had to do with spacing.  I have BCC'd those I specifically noted,
>> to avoid embarrassment, but here's the story:
>>
>> Stations that left insufficient space in a CQ between "CWO" or "TEST" and
>> the start of their callsign were "rewarded" with spots for ON and OK or TN
>> (for example) instead of their real N and K prefixes.  Stations that
>> inserted slightly additional spaces between letters in their suffix (this
>> seems to have been particularly prevalent with last letters like "E" and
>> "I") found their callsigns truncated (with the last letter left off)'.
>>
>> If you think this might have been happening to you, you can test it by
>> searching on the beta RBN web site for possibly truncated or expanded
>> versions of your call.  You can even use a wildcard (*) at
>> beta.reversebeacon.net/main.php to search for all the possible additions
>> - some won't work because they result in imaginary prefixes.  Personally, I
>> was delighted to learn that despite a lot of running, my call was not
>> miscopied in this way by the RBN.  My CQs were all machine-sent, which may
>> explain it.
>>
>> --
>> 73, Pete N4ZR
>> Check out the new Reverse Beacon Network
>> web server at <http://beta.reversebeacon.net> <http://beta.reversebeacon.net>.
>> For spots, please use your favorite
>> "retail" DX cluster.
>>
>> _______________________________________________
>> Skimmertalk mailing list
>> Skimmertalk at contesting.com
>> http://lists.contesting.com/mailman/listinfo/skimmertalk
>>
> _._,_._,_
> ------------------------------
> Groups.io Links:
>
> You receive all messages sent to this group.
>
> View/Reply Online (#47354) <https://cwops.groups.io/g/main/message/47354>
> | Reply To Sender
> <n2ic at arrl.net?subject=Private:%20Re:%20Re%3A%20%5Bcwops%5D%20%5BSkimmertalk%5D%20CW%20Open%20and%20the%20RBN>
> | Reply To Group
> <main at cwops.groups.io?subject=Re:%20Re%3A%20%5Bcwops%5D%20%5BSkimmertalk%5D%20CW%20Open%20and%20the%20RBN>
> | Mute This Topic <https://groups.io/mt/85392321/5052658> | New Topic
> <https://cwops.groups.io/g/main/post>
> Your Subscription <https://cwops.groups.io/g/main/editsub/5052658> | Contact
> Group Owner <main+owner at cwops.groups.io> | Unsubscribe
> <https://cwops.groups.io/g/main/unsub> [dougzzz at gmail.com]
> _._,_._,_
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.contesting.com/pipermail/skimmertalk/attachments/20210905/2294eadf/attachment.html>