[Dxspider-support] Self spotting - More

[Michael J. Tubby B.Sc (Hons) G8TIC]

Hmmm... whats's the big deal mwith self spotting then?

Okay, in some contests its against the rules - in which case report the person (with evidence) to the contest adjudicator.

At other times, like working meter scatter, self spotting is VERY USEFUL in letting people know who's where.

Darren... would you like me to fit one of my company's GPS based tracking boxes to your car... I'm sure I could get it to report you directly to the Police each time you went over the speed limit and generate a "you silly git you need to drive slower or get a smaller engine" message along with having you sent three points :o)

Mike 'tic

  ----- Original Message ----- 
  From: Darren G0TSM 
  To: The DXSpider Support list 
  Sent: Friday, November 05, 2004 8:21 PM
  Subject: Re: [Dxspider-support] Self spotting - More




2) "Ground" incoming remote self-spots:

- Backup the file /spider/perl/DXProt.pm
- Edit this file
- Look for the line:
   # bash down the list of bands until a valid one is reached
- Just BEFORE this line, copy/paste the 4 lines below:

        if (($_[2]
=~ $_[6]) || ($_[6] =~ $_[2])) {
                dbg("PC11:
self: $_[6] attempted to spot $_[2]");
                return;
        }


Well done Robert, I can't see where to add the above 4 lines into the DXProt.pm file for build 58.304


  Darren


  At 19:46 05/11/2004, you wrote:

    Darren G0TSM wrote:


      Was there ever a conclusion to the self spotting saga?..
      I wonder if self spotters could have their spot stopped and be sent a message..

    That's exactly what I've been doing for over one year on my node
    HB9IAC-8 and the trick to do so that was posted on this list on
    May 7th, 2004 (it can be seen in the DXspider-support archive).

    Both local and distant self-spots are stopped and local offenders
    receive an appropriate warning message.

    This requires adding a few lines in 2 files in the source code:
    dx.pl (for local spots) and DXProt.pm (for distant spots).
    I did that for DXSpider 1.51 build 57.245 (a bit old now)
    but the same code should be applicable to other versions.

    BUT it would be much better if Dirk would change one day his mind
    about this problem and allow us to set a variable at program start
    so that each sysop can choose if he (and his users) want this kind
    of information or not...

    Greetings from Geneva,                  Robert - HB9BZA

    -- 
    Robert CHALMAS, PO Box 1225, CH-1227 Carouge/GE, SWITZERLAND
       email:        rchalmas at users.ch    AX-25: HB9BZA @ HB9IAP
    homepage: http://rchalmas.users.ch

    _______________________________________________
    Dxspider-support mailing list
    Dxspider-support at dxcluster.org
    http://www.tobit.co.uk/mailman/listinfo/dxspider-support



------------------------------------------------------------------------------


  _______________________________________________
  Dxspider-support mailing list
  Dxspider-support at dxcluster.org
  http://www.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.tobit.co.uk/pipermail/dxspider-support/attachments/20041108/c5a6d771/attachment.html