April 2023 - arrl-odv - reflector.arrl.org

[arrl-odv:34747] K5NA (SK)
by david davidsiddall-law.com 13 Apr '23

13 Apr '23

https://www.wrtc2022.it/en/news-11.asp?idnews=76 Sincere condolences to Susan, K5DU. Dave K3ZJ

1 0

[arrl-odv:34744] In Newsletter
by Middleton, Diane, W2DLM (CFO) 11 Apr '23

11 Apr '23

Please see this weeks In News.

1 0

[arrl-odv:34742] Letter of support
by Minster, David NA2AA (CEO) 11 Apr '23

11 Apr '23

I continue to receive very supportive feedback from members regarding the "tough decision" on a dues increase. Here's a letter from a QCWA chapter in Ohio. This is very much in line with the many emails I have been receiving. David [cid:ed6e5f51-ee67-4eec-8af7-41e594c2d8fd@namprd16.prod.outlook.com]

2 1

[arrl-odv:34730] Use of YL and OM as gender specific pronouns
by Michael Ritz 11 Apr '23

11 Apr '23

ODV; I have had a member ask me the following: Nicole Music wrote on 4/10/23 08:15: > >> .....YL means young lady and refers to all female > >> operators regardless of their age. OM means old man and refers to all > >> male operators. My question is for those that don't self-identify > >> with female or male what is that abbreviation? Is there a difference > >> for them or do we just refer to them as YL or OM regardless of their > >> gender? > >> > Given the current political climate are there any suggestion here? I guess the larger question is: Does the League need to think about working to eliminate the YL and OM as pronouns in amateur radio, since there will be some people that fall outside of those two defined categories? Is there a third pronoun that can be used for those that identify as neither a YL or an OM? 73; Mike W7VO

6 6

[arrl-odv:34735] Re: "WHEREAS, Bernstein rants..."
by Minster, David NA2AA (CEO) 11 Apr '23

11 Apr '23

I want to make a short comment on this latest rant from Dave Bernstein. He is wrong and his information is based on an incomplete picture of LoTW today. In fact, LoTW continues to process uploaded logs at about 40 QSOs per second. We did an upgrade recently that caused that performance to tick up slightly. Once the other upgrade is done, perhaps later this week, we will examine how the impact of a significant increase in horsepower affects performance. While this is going on, we are also doing all of the foundational work to move LoTW into the cloud at AWS. Dave is looking exclusively at uploaded logs being processed. He has completely ignored the download requests from LoTW by users. Increasingly, software authors are using LoTW as a way to supplement logbook information on the local computer by downloading it from LoTW. These requests that are processed at the same priority as uploaded logs cause processing gaps in handling uploaded logs so the metrics appear worse than they are. No one is lying. No one is hiding information. And no, we are NOT giving Dave access to anything internally at ARRL. Dave’s arrogant, angry, confrontational, and “know it all” approach – as demonstrated yet again by his message below – shows that he thinks he knows everything that is going on and knows how LoTW needs to be dealt with now and in the future. And in terms of the messaging Bob Naumann has been providing? It is truthful, timely, and clear. That Dave chooses to attack the facts that don’t fit into his narrative is yet another indication that he has problems – and that he is wrong. Dave is a retired programmer with generation++ old programming skills who writes single user software that he gives away. I cannot imagine how his ego would survive finding that no one would actually pay for it. His message, again largely based on opinion and not fact, is the kind of garbage he puts out on our LoTW groups.io forum that causes people to unsubscribe and move on. Bob Naumann can provide you with the details if you too are not a believer. I reiterate: it is not in our best interest to engage with Dave. He is uninformed. He is opinionated. He is a know it all. He will not collaborate with anyone. We’ve turned the page on Dave, and do not intend to engage with him. Thanks. David ======================================================= From: Dave AA6YQ <aa6yq(a)ambersoft.com<mailto:aa6yq@ambersoft.com>> To: w5ov(a)arrl.org<mailto:w5ov@arrl.org> Cc: K5UR(a)arrl.org<mailto:K5UR@arrl.org>; k1twf(a)arrl.org<mailto:k1twf@arrl.org>; W6RGG(a)arrl.org<mailto:W6RGG@arrl.org>; k3rf(a)arrl.org<mailto:k3rf@arrl.org>; k9la(a)arrl.org<mailto:k9la@arrl.org>; ac0w(a)arrl.org<mailto:ac0w@arrl.org>; k5uz(a)arrl.org<mailto:k5uz@arrl.org>; wa8efk(a)arrl.org<mailto:wa8efk@arrl.org>; np4h(a)arrl.org<mailto:np4h@arrl.org>; k0aiz(a)arrl.org<mailto:k0aiz@arrl.org>; ab1oc(a)arrl.org<mailto:ab1oc@arrl.org>; w7vo(a)arrl.org<mailto:w7vo@arrl.org>; k6wx(a)arrl.org<mailto:k6wx@arrl.org>; n2zz(a)arrl.org<mailto:n2zz@arrl.org>; k0rm(a)arrl.org<mailto:k0rm@arrl.org>; n4mb(a)arrl.org<mailto:n4mb@arrl.org>; n6aa(a)arrl.org<mailto:n6aa@arrl.org>; n5aus(a)n5aus.com<mailto:n5aus@n5aus.com>; Dave AA6YQ <aa6yq(a)ambersoft.com<mailto:aa6yq@ambersoft.com>> Sent: Fri, Apr 7, 2023 8:32 pm Subject: "WHEREAS, Logbook of the World (LoTW) has become one of the most popular and relied upon..." Since without warning or explanation, you have prevented me from posting on the ARRL-LoTW forum, we'll communicate directly. From 2017 through December 2022, LoTW consistently processed submitted QSOs at the rate of 40 per second while responding to download requests and award queries; surges of submissions after a popular weekend contest were processed within one day. In January 2023, this aggregate performance suddenly dropped to less than 10 QSOs per second. Your immediate reaction was to blame this on logging applications that can be configured to automatically submit QSOs to LoTW as they are logged - a convenience for users. You provided no evidence or analysis supporting this claim: "Many FT8 users upload after each QSO. This practice is totally unnecessary and the overhead of processing thousands of one QSO files is enormous. A daily upload, or maybe, every 10 to 25 QSOs, would be better and would greatly reduce processing overhead." https://groups.arrl.org/g/ARRL-LoTW/message/36950 The LoTW Server upgrade project, completed in 2017, had doubled LoTW's QSO processing performance, and made it straightforward to accomplish further increases when needed by replacing LoTW's database engine with a higher-performance alternative, of which several are available. At that time, ARRL management indicated that LoTW could accommodate single-QSO uploads. Most logging applications now provide that capability. When I pointed that out, you eventually responded: "Those developers who made that statement years ago never anticipated what we have going on today especially with FT8 and thousands of upload files per hour. They were wrong. Repeat: They were wrong!! No dancing around it, they should not have made such a foolish statement. Oh, and none of them are here any more. And, the people saddled with dealing with this mess now, were not part of that group of bad decision makers." (your emphasis) https://groups.arrl.org/g/ARRL-LoTW/message/37981 While it is certainly more efficient for LoTW to process one batch of 10 QSOs than 10 batches of one QSO, there are three things wrong with your response: 1. Without any subsequent performance improvement, LoTW performance consistently exceeded user expectations through December 2022, as summarized above. Then from one month to the next, its performance fell by a factor of four. You've presented no evidence showing that the number of single-QSO uploads increased dramatically enough from December to January to cause that large a sudden decrease in performance. 2. "The developers who made that statement years ago" did anticipate that the load on the LoTW Server would increase - due to support for additional awards, improved usability, and the increased participation that these improvements would drive. That's why the LoTW Server upgrade project made it straightforward to further increase performance with a higher-performance database engine - an opportunity that continues to exist. 3. Even if your assessment was correct, which it demonstrably is not, to denigrate ex-employees in a public forum is outrageously inappropriate. Have the ARRL's attorneys run out of work? Any software development candidate your organization seeks to hire will review your public posts and - on encountering this one - run the other way. Today, you announced "We have been having underlying server problems as reported for several weeks". (my emphasis). https://groups.arrl.org/g/ARRL-LoTW/message/38252 Then you proceeded to list 9 "culprits", with no data or analysis in support of your claims. You did provide statistics showing increases in DXCC award processing for each month of this year, but failed to include the same statistic for December 2022 - making it impossible to determine whether DXCC award processing was a significant contributor to the 4X degradation in aggregate performance from December to January. This is "Performance Analysis 101". Among the culprits, you list "As reported here, downloads also use processing power, and take away cycles from uploads" During the first week of January, users attempting to submit QSOs to LoTW were greeted with "Internal Server Error" messages, and LoTW's QSO processing performance dropped to zero. Your team spent a week discovering that a defect in the popular Grid Tracker application was continuously invoking the LoTW function that client applications can use to download confirmations. The Grid Tracker developers promptly corrected their defect, and you reported that you modified LoTW to protect itself against a repeat performance from Grid Tracker. As I and others pointed out, LoTW remains vulnerable to any other application that unintentionally hammers the LoTW Server by continuously invoking that LotW function; a popular application with tens of thousands of users could easily bring LoTW to its knees, as Grid Tracker inadvertently did. I suggested that you augment LoTW with a simple protective mechanism ("Client Keys") that would enable you and your staff to immediately identify any application responsible for a torrent of function invocations, and to immediately terminate the processing of those invocations by that application. Club Log has long protected itself with this mechanism. You declined: "These sorts of things will apply to the new LoTW when we get there. We will not be making the types of changes required to support things like Client Keys in the current system. It's just not going to happen despite the frequent suggestions made here." https://groups.arrl.org/g/ARRL-LoTW/message/37946 Leaving LoTW in this vulnerable state for years while "Project X" is staffed, designed, implemented, tested, and documented is an extraordinarily bad decision. We now know that at least two smartphone-hosted applications can be configured to continuously invoke LoTW's "report confirmations" function, which could generate tens of thousands of download requests each day - and could already be doing so. One of them is "open source", meaning that it can be modified to invoke this function as frequently as its user desires. Frankly, "It's just not going to happen" is a poor justification for not taking the few days of development time required to eliminate this serious vulnerability. Earlier today, you posted the message "LoTW Emergency Downtime - Today April 7", stating "At about 1900 UTC +/- we will be bringing the entire LoTW system down for maintenance. We have IT staff ready to begin to attempt to correct the underlying problems that we have been enduring as of the last few weeks." https://groups.arrl.org/g/ARRL-LoTW/message/38268 LoTW's performance has been severely degraded for the past 3 months, Bob. Soon after, you posted "We have been running now a little over 1 hour with our new platform for one of the servers in the LoTW system. We had hoped to move another, but there are DNS Issues and other networking concerns that need to be addressed. Even so, it appears that we have been able to make a huge improvement in performance. We are now almost 24 hours behind but making up more than one hour, per hour. This was not possible before. Thanks to our non-ham IT staff for determining how to make this possible." https://groups.arrl.org/g/ARRL-LoTW/message/38277 If it was possible to do this today, it was possible to do it back in January. I sincerely hope that whatever changes were made today will restore LoTW to the performance it provided from 2017 through December 2022. Without root cause analysis, however, we won't know for sure until the next popular contest. de AA6YQ - recipient, ARRL 2008 Technical Innovation Award - "one of the earliest logging-program authors to integrate functions for ARRL's Logbook of the World" https://ema.arrl.org/2008/08/02/aa6yq-wins-arrl-technical-innovation-award/ - author, "Using Logbook of the World" https://lotw.arrl.org/lotw-help/ - recipient, ARRL 2020 President's Award - "in recognition of "exemplary, outstanding, and continuing service" to ARRL and its members as part of the ARRL Logbook of The World team." http://www.arrl.org/news/arrl-board-grants-awards-and-recognitions

2 2

[arrl-odv:34720] A&F Agenda
by Ryan, Jeff, K0RM (Dir, RM) 10 Apr '23

10 Apr '23

All: Attached. 73, Jeff, K0RM

7 6

[arrl-odv:34726] Re: A&F Agenda
by Lee Cooper 10 Apr '23

10 Apr '23

Art, i would say it is more of not being able to hear and understand the thoughts and comments more so than lack of trust. There are several agenda items i would like to hear the discussion versus just a synopsis, especially- as it is always being pointed out- that i have fiscal responsibility to the league. Btw, as all meetings are open to all board members, can I assume that any Vice Director wishing to attend will have their travel expenses authorized? Lee, W5LHC On April 9, 2023, at 12:56, Art Zygielbaum <k0aiz(a)arrl.org> wrote: The problem is not, as I see it, the lack of transparency. It's the lack of trust. Taking a position that everyone on a committee is out to get the rest of us, to do dastardly deeds in the promotion of an untoward position is a sad state of affairs. I believe in the people on A&F. I will not attend their meeting unless they have a need for something I can offer. We will all see the outcomes of all of our board committee meetings. If they do not meet our expectations, let's talk about that at the board meetings. Let's change the committee composition if needed. Let's improve the rules and regulations if needed. Let's stop assuming the worst in fellow board members. 73, Art K0AIZ -- Arthur I. Zygielbaum, K0AIZ ARRL Midwest Division Director Member, Executive Committee Member, Programs and Services Committee Member, ARRL Foundation Board ARRL - The National Association for Amateur Radio® On 4/9/2023 6:39 AM, N5AUS wrote: I have raised this issue in the past. Starting with the EC in 2019 following the defeat of the egregious efforts to shield all Board activities from the scrutiny of both the Members and other Board Members it was decided that all Board Members - Directors and Vice-Directors - were entitled to both attend all Committee meetings and to speak to the matters before the respective Committee. That has been the rule, EXCEPT for A&F. It has insisted on conducting what amount to secret meetings by virtue of conducting meetings in locations that effectively prohibited the balance of this Board from attending. There have been discussions in some meetings in recent times that led to actions adverse to the interests of the League, the Members and good order. in a time when the League is facing millions in operational losses, the conceited insistence on remote in-person meetings costing thousands of dollars we don’t have and can’t justify is an affront to our Members and Donors. These effectively secret, financially irresponsible meetings need to cease. I second Vice President Raisbeck’s reasonable request - but I will extend his request to include that the remote meeting be cancelled and that A&F be bound by the operational rules of the other very important Standing Committees - it’s meetings be fully conducted by Zoom and the conceit of remote in-person meetings be ended. John Robert Stratton N5AUS West Gulf Division Director Sent from my iPad On Apr 9, 2023, at 6:02 AM, Mike Raisbeck via arrl-odv <arrl-odv(a)reflector.arrl.org> wrote: Thanks Jeff. I'll review. While we're on the subject of the A&F, I want to bring up again a matter that I had brought up some weeks ago. Most of our standing committee meetings are viewable through Zoom. This one, arguably one of the most important meetings, other than the Board meeting itself, is not. As it turns out, I will not be able to make the trip to Denver this time around. So, lack of Zoom access certainly affects me. But I imaging it affects others as well. Perhaps a straw poll of the Board is in order here. How many Board members feel that this meeting should be remotely accessible? I'll vote yes, of course. I think it should. Anyone else ?? Thanks, Mike K1TWF On Saturday, April 8, 2023 at 08:16:59 PM EDT, Ryan, Jeff, K0RM (Dir, RM) <k0rm(a)arrl.org> wrote: All: Attached. 73, Jeff, K0RM _______________________________________________ arrl-odv mailing list arrl-odv(a)reflector.arrl.org https://reflector.arrl.org/mailman/listinfo/arrl-odv _______________________________________________ arrl-odv mailing list arrl-odv(a)reflector.arrl.org https://reflector.arrl.org/mailman/listinfo/arrl-odv _______________________________________________ arrl-odv mailing list arrl-odv(a)reflector.arrl.org https://reflector.arrl.org/mailman/listinfo/arrl-odv

4 3

[arrl-odv:34721] Personal FB post
by Minster, David NA2AA (CEO) 09 Apr '23

09 Apr '23

I am connected to some of you on my private personal FB page. Today someone texted me with a post that Norm Fusaro had put up on FB taking shots at everything from LoTW, the Lab, the BoD, and even our work on STEM and with clubs. I was amazed he didn't include EmComm or HOA legislation as he has attacked that too in the past. I posted a statement of personal frustration along with Norms post on my private page. That post has now made its way to My ARRL Voice. I have heard from one Director of his displeasure regarding this. It was never my intention for it to be made public and I'm sorry someone shared it. That said, I stand by what I wrote. Thanks David Get Outlook for iOS<https://aka.ms/o0ukef>

1 0

[arrl-odv:34718] Fwd: Quarterly Logbook report
by Ryan, Jeff, K0RM (Dir, RM) 07 Apr '23

07 Apr '23

________________________________ From: G Widin <gpwidin(a)comcast.net> Sent: Thursday, April 6, 2023, 7:55 AM To: Ryan, Jeff, K0RM (Dir, RM) <K0RM(a)arrl.org> Subject: Quarterly Logbook report Jeff, Attached is our quarterly Logbook report. As always, I would be happy to answer questions, now or later. Take care es 73, Greg, K0GW

2 1

[arrl-odv:34717] CONFIDENTIAL
by Minster, David NA2AA (CEO) 05 Apr '23

05 Apr '23

[Note please follow the thread from the bottom up] Thanks Mickey. I am not responding to Dave's outburst. Dave is going to learn that his aggression, rhetoric, and false statements in our forums will not be tolerated. His personal attacks against me, Bob, and others including Director Stratton are just not what our forums are for. His latest statements are that the Board authorized "waterfall development" of a new "complete re-write" of LoTW. Where did he dream that up? I checked the minutes. Not present. Bob has personal emails from other forum members who Dave has attacked, and who he has even banned from his own DXLabs forum because he doesn't want to be challenged! Toxic? ARRL today is an environment of truth - not the ridiculous notion of transparency. There are people, and they very well know who they are, who are headed for a heart ache if they bring that non-sense up with me. And if it is in a public forum, as it has been where I've been questioned about these things, our members will get the full story - all the relevant and material facts - not just the headlines filtered through opinion, self-interest or other causes that creates a misunderstanding of what the truth is. Let me tell you about the interest in LoTW on the board. I wrote the Radiosport Working Group an email on March 13th just to get a read on WHO should be on the working group including experts from outside ARRL HQ. I received only one response from the entire group. One. No one seems to want to take this on and I am not going to drag people through it kicking and screaming. It is a huge project. LoTW works, and works just fine. There's only so many cars you can get over a multi-lane bridge at a time. I know that from commuting into NYC for years. Just because the response time is slow during peak loads does NOT mean it is BROKEN, does NOT mean it is a PROBLEM, and does NOT mean it must be replaced. The REASON WHY LoTW MUST BE REPLACED: it was not designed as a real-time system. It was designed to handle batches of confirmations with no expectation in turnaround time. Those are not the expectations of today's users. These people are uploading every contact, in real time, and expecting to see their awards totals change, instantly, as they upload. Can't do it. Period. Full stop. I'd also suggest - strongly - that if you think you're serving ARRL by communicating with Dave, you're hurting the organization. He will use your words against you and ARRL. I would encourage you to stop, as we did in November 2020. Thanks. David From: Baker, Mickey, N4MB (Dir, SE) <mbaker(a)arrl.org> Sent: Wednesday, April 5, 2023 1:08 PM To: Minster, David NA2AA (CEO) <dminster(a)arrl.org> Subject: Fwd: ARRL-LOTW forum FYI. I'm not responding, don't know if anyone else is. Mickey Get Outlook for iOS<https://aka.ms/o0ukef> ________________________________ From: Dave AA6YQ <aa6yq(a)ambersoft.com<mailto:aa6yq@ambersoft.com>> Sent: Tuesday, April 4, 2023 9:06:15 PM To: Fred Kemmerer <fkemmerer(a)anita-fred.net<mailto:fkemmerer@anita-fred.net>>; Norton, Richard N6AA (Dir, SW) <richardjnorton(a)yahoo.com<mailto:richardjnorton@yahoo.com>>; Mickey N4MB <n4mb(a)arrl.net<mailto:n4mb@arrl.net>>; G Widin <gpwidin(a)comcast.net<mailto:gpwidin@comcast.net>> Cc: Bernstein, Dave, AA6YQ <aa6yq(a)ambersoft.com<mailto:aa6yq@ambersoft.com>> Subject: ARRL-LOTW forum W5OV has placed me on moderated status - with no cause, and with no explanation. None of my posts have come close to breaking the forum's rules -- which I established when I negotiated the transfer of this group from its original founder to the ARRL and re-affirmed when the "Communications with Members" Committee created additional online forums in the image of ARRL-LoTW. Sadly, the descent of the ARRL's culture towards complete toxicity is accelerating. It's getting close to the point of no return. de AA6YQ

1 0