I guess you can use X forwarding
On Wednesday, February 28 2024, 09:59:11, William Smith via
wsjt-devel wrote:
I get what you were trying to do, and it is not a perfect
solution,
but many people use VNC or some other kind of remote desktop
protocol
to remotely control the computer that is
While I do agree, there aren't too many clues for the operator who
is listening apart of not trusting any rare DX.
I saw that NK call yesterday in 10m mixed with the Aruba one. I
answered to both, once or twice. Both looked like legit grids and
feasible callsigns.
In the last weeks I'm
I have the exact same problem, I operate from IM89AW and IN70HD
with same callsign. I haven't had complains, but saw the issue.
On Tuesday, February 13 2024, 10:29:02, Ed Stokes via wsjt-devel
wrote:
1. ( ) text/plain (*) text/html
Laurie & Uwe,
As a ham who operates from
I guess it'll be easier to use the arrl certificate and do not
reinvent the wheel. Yeah I can foresee people not wanting to
register with the arrl, but everything has to start somewhere.
On Thursday, October 05 2023, 18:33:52, Adrian via wsjt-devel
wrote:
[1. text/plain]
As a victim of
On Monday, September 04 2023, 17:57:03, Jim Brown via wsjt-devel
wrote:
SSB), and for at least 50 years, rigs have a button labeled
"split."
... which you can use [in the same sense than any other mode] with
wsjt-x providing your hamlib driver implements it. The only thing
that really
I've noticed that - at least in FT4/8 - if you enable TX towards
the end of a cycle TX starts inmediately despite it won't have the
time to transmit something useable.
I think it would be helpful if - optionally or not - TX is
prevented to start until the next turn when there isn't enough
