[Dxspider-support] Seeing all your spots

Dirk Koopman djk at tobit.co.uk
Thu Aug 13 23:11:11 CEST 2020


Simon

Sorry, not now. It's not what I want to achieve. Whilst I can see that 
you (and others might find it useful, what comes out is so far away from 
the input that I would find it difficult (with the code as it is) to 
reconstitute some version of the input back into the output.  I can see 
your use case, but some might point out that you are "self-spotting" 
(BTW I have no views on this, one way or the other).

The thing I _may_ be able to offer, is for a user to flag their 
'account' on their preferred node and if (and only if) their callsign 
appears on the skimmers, a tranche of spots will be sent. But even that 
has to be rate limited. It will never send out a flush of skimmer spots 
every time a user sends CQ. If there is a general need for something 
that is more "real time", I could be persuaded to consider a separate 
system to filter skimmers to achieve this. But not now.

73 Dirk G1TLH

On 13/08/2020 21:07, Simon Ravnič via Dxspider-support wrote:
> I would like to ask you to please reconsider adding this feature 
> again. A must feature for a RBN cluster.
>
> To summarise, I would like to see all spots of my call, so when I call 
> CQ I can see the world lit up. Good for monitoring change in 
> propagation when running CQ.
>
> 73
> Simon, S53ZO
>
>> On 12 Jul 2020, at 02:56, Dirk Koopman via Dxspider-support 
>> <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk>> 
>> wrote:
>>
>> Within some pretty tight limits, yes. But you should be careful a) 
>> what you wish for because b) when I last looked I was receiving 
>> ~150,000 spots / hour, of which I was getting ~5500 useful spots 
>> (~3%). I will put it on the list. If the rate of bustedness is 
>> generally as bad as Lee suggests then we will chop that number of 
>> useful spots down  even more.
>>
>> But I have observed that the compression rate (if that is a 
>> reasonable way of describing it)  decreases from about 10% when spot 
>> rate is in the 5000/hour area  yielding around 500 deliverables, 
>> 50000 yields 3500, 100000 yields about 5000.
>>
>> I do wonder whether all this extra "diversity" is really the most 
>> efficient way of going about things. The returns diminish really 
>> quite quickly. There are a finite number of people contesting and one 
>> really doesn't need to send more rbn spots than is necessary to 
>> qualify any particular station.
>>
>> It will interesting to see the hourly stats after contest finishes.
>>
>> Dirk
>>
>> 11 Jul 2020 18:09:39 Simon Ravnič <s53zo at t-2.net <mailto:s53zo at t-2.net>>:
>>
>>     Great stuff, TNX.
>>
>>     S50DXS is up and running with new RBN feed. No big impact on CPU.
>>
>>     A request. When calling CQ it is very nice to see which skimmers
>>     in the world copy your signal. Would it be possible to add a
>>     bypass to all the great filtering you made and show all the spots
>>     from RBN feed for a chosen callsign?
>>
>>     TNX & 73
>>     Simon, S53ZO
>>
>>>     On 9 Jul 2020, at 23:38, Dirk Koopman via Dxspider-support <
>>>     dxspider-support at tobit.co.uk
>>>     <mailto:dxspider-support at tobit.co.uk>> wrote:
>>>
>>>     TL&DR
>>>
>>>     The Reverse Beacon Network DXSpider client is here!
>>>
>>>     If you want to see what it does: connect to gb7djk.dxcluster.net
>>>     <http://gb7djk.dxcluster.net/> 7300, login and then type 'help rbn'.
>>>
>>>     If you are a 'master' branch read UPGRADE.mojo, do what it says,
>>>     then read RBN.mojo for instructions and information about the
>>>     RBN interface. You will be able to read both documents in either
>>>     branch. You should stop the node before doing the 'git pull
>>>     --all; git checkout --track mojo origin/mojo'.
>>>
>>>     If you are on the 'mojo' branch, then read RBN.mojo and, if
>>>     necessary, do what it says and read UPGRADE.mojo. Particularly
>>>     if you have a build number under 276.
>>>
>>>     Have fun.
>>>
>>>     73 Dirk G1TLH
>>>     _______________________________________________
>>>     Dxspider-support mailing list
>>>     Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
>>>     https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20200813/c4ecc4d8/attachment-0001.htm>


More information about the Dxspider-support mailing list