sprite1741
Member
- Joined
- Jun 22, 2006
- Messages
- 198
- Reaction score
- 2
Timeline of events here in the mega thread. https://www.reddit.com/r/amateurradio/comments/5jf4i2/ham_radio_deluxe_mega_thread/
I haven't read it either but I don't suspect that it would apply in this circumstance since it doesn't involve a clause in a contract. Someone who actually reads the specific law would know for sure.
"With the new law in effect, any contract that attempts to tie in a clause calling for a fine or penalty for a review would be rendered void and legally unenforceable."
https://www.congress.gov/bill/114th-congress/house-bill/5111
Timeline of events here in the mega thread. https://www.reddit.com/r/amateurradio/comments/5jf4i2/ham_radio_deluxe_mega_thread/
I read it. Definitely iron clad evidence presented. My wife is diabetic. Low blood sugar doesn't make you an *******. It makes you shake and weak.....you get some sugar fast....you don't busily type an email and revoke someone's access! Definite attempt at damage control..... They didn't expect this incident to go viral.Did anyone else here read the "ticket" (PDF linked above by the OP)?
HRD basically admits to vindictive actions by telling the guy to download software which maliciously removed the existing software he had paid for (to use via the license, etc.). It's one thing to be honest and tell a customer up front that they are implementing section xyz from their contract, but to pull a stunt like that is amazingly STUPID for any business that expects to have customers. Wow.
Diabetes.....right.
73 HRD !
Actually, I recollect, this same thing happened to someone else before. Thus isn't the first time HRD screwed someone.
I never had any issues with HRD's tech support during the time that I used the program. I knew that there was some discontent out there about HRD even before I started using it. But, in my situation, I paid my money for a year of support and eventually stopped using it on technical grounds...not because I had heard of some guy who had talked to a guy who knew of a guy who had issues with HRD.
Note that synonyms for "rumor" are "gossip", "hearsay", "speculation", "scuttlebutt". In my book, first-hand experiences are a lot more valuable than rumors. If you haven't used the program yourself, are you reporting facts or just spreading rumors? As a moderator here, I'd prefer to see discussions of fact in the forums.
My point was that the OP was second-hand information. It seemed that the OP's intent was to just spread around reports from other social media....everything in the OP is accurate.
Not that I know of. And, it wouldn't make any difference to me if they did.Does HRD advertise on RR?
I'm really glad you decided not to moderate this thread with the heavy hand that you clearly would have preferred.
To all JTAlert / HRD V6 users.
I will no longer be providing support for HRD V6 logging within JTAlert.
This comes into effect with the next public release of JTAlert (2.9.0).
Affected HRD users can continue to use the current version of JTAlert (2.8.7) for as long as they want.
I will not be able to provide any support for that version, however, if a future HRD release breaks the JTAlert/HRD integration.
The free V5 of HRD will continue to be supported.
Moving forward, all future JTAlert versions will not support HRD V6 logging.
I will not be participating in any public or private discussions regarding the reasons for this decision".
I sincerely apologise to the affected HRD users.
After some "soul-searching", I now feel I owe the community an explanation, even if brief, regarding my decision to abandon HRD V6 logging support in JTAlert, especially to those users directly affected by this decision.
"Bottom-Line", I don't want myself or my software to have any sort of association with HRDLLC the company, their policies or their products.
This decision was a long time coming. The draft for the announcement had been sitting in my email draft folder for over 12 months. I came close to making the announcement on two other occasions in that time, but chose to "back-off", primarily because I knew this would affect a large number of JTAlert users and I felt uncomfortable with that.
The "die was cast" when HRDLLC released HRD ver 6.3.0.435 in October 2015. That releasecontained malicious code that deliberately shutdown JTAlert on a users PC without warning or message to the user that HRD had performed this unauthorised act. Details of this are publicly available within this groups message archives.
There have been several other events and interactions with HRDLLC over that time that are not publicly known, contributing to this decision, and I will not be discussing them here or privately.
While the association with HRDLLC was simply that my software had a feature that extended the functionality of HRD in providing a JT65/JT9 logging bridge, I am no longer comfortable supporting (by association) HRDLLC the Company, their policies or their products.
Again, I sincerely apologise to the affected HRD users.
de Laurie VK3AMA