It was probably a robot! 

73 -- Larry -- W1DYJ



From: Ron WV4P 
Sent: Monday, December 02, 2019 20:26
To: WSJT software development 
Subject: Re: [wsjt-devel] Callsign lockout

There are Many reasons to block a caller, they may be a Lid, they may be 
disrupting a QSO, they may just be Very annoying. As it stands we have No way 
to deal with them. We need a way. Just last night I had a PA station I had 
never worked send me RR73 over and over for 30 min. Ron, WV4P

On Mon, Dec 2, 2019, 7:19 PM Gary Kohtala - K7EK via wsjt-devel 
<wsjt-devel@lists.sourceforge.net> wrote:

  I agree. I believe a lockout feature could be abused. Case in point was
  during the heyday of packet radio (I call it the Packet Radio Wars).
  If you did not march to 'their' drum you were locked out of all nodes, BBS'
  gateways, etc. Such a thing should be banned. If it is there, someone
  will use it to push their agenda. That's not in the spirit of amateur radio.

  Best regards

  Gary, K7EK


  ---


  On Monday, December 2, 2019, 04:39:31 PM EST, David Gilbert 
<xda...@cis-broadband.com> wrote: 



  I have the same opinion.  I almost never use "Call 1st" and I find it 
  trivial to operate without it no matter how many callers I get.

  Even FT8 should be able to handle some degree of operator proficiency.

  73,
  Dave AB7E




  On 12/2/2019 1:00 PM, Jim Brown wrote:
  > On 12/2/2019 2:54 AM, Martin Davies G0HDB wrote:
  >> In summary, I don't see any need whatsoever for any modification of 
  >> the 'Call 1st' capability
  >> to include any forms of queuing or callsign lockout
  >
  > Agreed. This is an operator issue, not a software one.
  >
  > 73, Jim K9YC
  >



  _______________________________________________
  wsjt-devel mailing list
  wsjt-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wsjt-devel

  _______________________________________________
  wsjt-devel mailing list
  wsjt-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wsjt-devel



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



--------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to