Not sure why you come to these conclusions, the website is not slow, it is not
abandoned and the spots enter the database nicely.
The map issue is explained in the wsprnet org forum with the appropriate
solution as well.
Users are managed steadily albeit sometimes slowly as I am probably the onl
Is the current MacOS build of WSJT-X v2.1.0 64-bit that is compatible with
MacOS Catalina (v10.15)? When I run a system report on my Mac with OS 10.14.6
installed, the report shows WSJT-X v2.1.0 is a 64-bit (Intel) app. But the
discussions I have seen indicate there is a build tool issue related
On 14/10/2019 21:44, Robert Rearden wrote:
Is the current MacOS build of WSJT-X v2.1.0 64-bit that is compatible
with MacOS Catalina (v10.15)? When I run a system report on my Mac
with OS 10.14.6 installed, the report shows WSJT-X v2.1.0 is a 64-bit
(Intel) app. But the discussions I have seen
This kind of ignorant response is frankly infuriating and in itself
shows why wsprnet.org is going to hell to put it kindly
I am very active in the LF/MF community and WSPR is heavily used for
propagation studies, realtime band opening indication, etc. Ask anyone
in at least the US and VK
Eric, the frustration in your email is visceral and leads me to one
question:
When did you last pay for an SLA in relation to wsprnet?
--
finger painting on glass is an inexact art - apologies for any errors in
this scra^Hibble
()/)/)() ..ASCII for Onno..
On Tue., 15 Oct. 2019, 08:37 Eric NO3M
Onno
My frustration is specifically with the seeming unwillingness of the
admin team to recognize the serious system issues that have plagued the
site for the last two years (at least). If this assumption is
inaccurate, then my apologies, as it is based on the comments made by
the admin that
I've been playing around with the UDP server capability in wsjt-x, and I
think I've got most of the lower level details figured out. However, I got
blocked on the schema negotiation part, which raised a deeper question.
I have been assuming wsjt-x is a server, and my code is a client. So I
sent
The description in the WSJT-X source is using the terminology of WSJT-X as the
server and anybody talking to it as clients.
There are simply messages from and to wsjt-x.
You'll note that every message described shows Out/In capability.Out means from
wsjt-xIn means to wsjt-x.
The heartbeat is
