I agree with Steve. Like most old time (mature) hobbies the early pioneers are either SKs or nearing the time when they can no longer operate. We need young blood into the hobby. Not many, if any will build any more, so we must move a bit into their sphere. They are growing up in the “digital” times and are dragging us into the 21 century. They need an Elmer not a head master. If you are not willing to teach by setting example then stay away from the new and experimental modes and stick to SSB and CW. I do not know when they”lid” terminology originated, possibly it should be banned from our vocabulary and replaced with “how can I help “ Enjoy.
Regards and 73s VE3FBZ London Amateur Radio Club www.larc.ca > On Jul 29, 2019, at 02:03, Stephen Ireland <vk3...@hotmail.com> wrote: > > Hmmm ..... trying to stay out of this one but can’t.... > > Even a few minutes back on 20m minute I just had an op do just as Andy K3WYC > reported .. and then that very same station call CQ... > > The solution is as Bill and many others report to set “Hold Tx Freq” ... and > to ensure that this is set as default. > > At a technical level, perhaps any version upgrades (regardless of previous > state) should set this? > > Yet there is also an ethical aspect to this discussion.... it also highlights > the issue and concept of the arrogant term “LID”.... You see some ops now > sending (frustration) messages such as “LID <CALL>” ... > > Utilising this arrogant obnoxious term degrades all the Amateur community. > > Perhaps the greatest “LID” is actually the one identifying potential “LID’s”? > > Using the term “LID” in the first place is not helpful for the growth and > development of AR – with AR being a regulated place of education and > learning that should be safe (including bullying-free) for people of all ages > and ways of life. > > Many dominions are now permitting entry-level Licence classes to have digital > mode access, with more and more dominions (such as Australia) proposing and > granting these rights this every day. > > This opens the whole discussion internationally of whether entry-level ops > with entry-level qualifications, with potentially low competency levels, > should really have access to Digital modes – especially new and developmental > modes such as the relatively immature FT suites. This matter should be taken > up as a general discussion point with the IARU and perhaps a clear position > put forward for the guidance of all Amateur regulatory domains. > > Operators need to learn and will make what some perceive to be mistakes ... > and the only way they get better is through observation, practise and through > constructive guidance from others. > > Perhaps also a bit of tolerance (and massive discouragement of the use of the > term “LID”) is required ... and not just with the JT modes either? > > 73 > > Steve I > > Sent from Mail for Windows 10 > > From: rjai...@gmail.com <rjai...@gmail.com> > Sent: Monday, July 29, 2019 1:24:50 PM > To: WSJT software development <wsjt-devel@lists.sourceforge.net> > Subject: Re: [wsjt-devel] Lid operators or bad design? > > Are they in the same time slot? If they are on odd and you are on even, no > real harm. FT8 is operated primarily split anyway. > > I do know this used to be an issue when lock rx=tx was a thing that people > would work you then transmit in your frequency slot. > > 73, > Ria > N2RJ > >> On Sun, Jul 28, 2019 at 11:58 AM Andy Durbin <a.dur...@msn.com> wrote: >> Everyone who uses WSJT-X for FT8 must have noticed the number of operators >> who answer a CQ and then, when the QSO is complete, call CQ on the same >> frequency. Are all these operators really stupid or are they being trapped >> by a weakness in the user interface design? >> >> 73, >> Andy, k3wyc >> _______________________________________________ >> 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
