[Dxspider-support] FYI: 4 new nodes added to ROS Auto-Spotting function.

Dirk Koopman djk at tobit.co.uk
Wed Jul 14 08:39:37 BST 2010


On 12/07/10 21:51, VK3AMA wrote:
> FYI
>
> The latest release of ROS software has added 4 new nodes to
> auto-spotting function.
>
> BG2RVL-9 dx.5iyou.cn:7373
> BD5RV dxc.jsdxc.net:7300
> BA2IA-2 spot.ba2ia.com:7300
> 9H1LO-1 dx.9h1lo.net:7300
>
> At time of this email, of the last 150 ROS cluster spots,
> 148 were auto-generated (98.7%).
>

If all major nodes were to do a "set/badword ros" then it probably does 
not matter that he keeps adding to the list, as the spots won't 
propagate very far.

On an other tack: I have been wondering for a while what to do with all 
the programs (of which the ROS stuff is but one) that insist on logging 
in, doing one or two things (eg send a spot or sh/dx), then immediately 
logging out.

Now, the code already does not bother (in most cases) to send out 
routing information for these in/out merchants, but I am now thinking 
that I ought perhaps to be a bit more brutal.

It would be a fairly simple job to have some kind of averaging or pump 
up timer that has the effect going into "cripple" mode if the last n 
connections were less than m seconds long.

"Cripple" mode would something like pretending to be a nice cooperative 
cluster that accepts spots, but does not send them on, and/or returns a 
*very* limited view of data such as spots (maybe only two or three spots 
else spots that are an hour or so old).

If the user starts to behave like a real person and connects p times for 
more than m seconds, it automatically comes out of "cripple" mode. While 
in "cripple" mode for more than (say) 2*m+random amount seconds then 
de-cripples that user for that session. This behaviour persists until 
they have behaved for p sessions.

"Misbehaviour" puts the user back into "cripple" mode.

Views anyone?

Dirk G1TLH




More information about the Dxspider-support mailing list