With the pending June 2026 demise of HamClock (see my 1/30/26 post, "The End of HamClock: RIP WB0OEW") due to the untimely recent passing of its creator, Elwood Downey WB0OEW, efforts are underway in the ham community to recreate the backend server which powers the informational content carried by Hamclock. Keith specifically notes:
"I fully support Brian Wilkins (KO4AQF) with his work to reverse engineer the output from the HamClock server. I think this is the best method to try and keep HamClock functioning past June. If we can build another source for the data and replicate that at multiple places around the world we can be sure we won’t end up in this situation again.
https://github.com/BrianWilkinsFL/open-hamclock-backend
If you’re able to help with this project, or know anyone who can assist, please contact Brian directly.
Thank you."
I want to add that Austin Parsons, KN4LNB is also involved with the backend project. I wish I had the knowledge and skills to help out with this project, but unfortunately I don't. As it is, the ham community should be very grateful for the efforts of guys like Brian, Austin and Keith who care enough to save HamClock.
Brian stated:
HamClock relies on an internet backend to provide live space-weather, propagation, DX, and news data. With the passing of its original developer, that backend is no longer being maintained, which means many HamClocks will gradually lose live functionality even though the devices themselves still work.
An open-source replacement backend is now being developed that recreates the same data feeds HamClock expects, using publicly available sources such as NOAA, space-weather services, PSK Reporter, and DX information sites. From the HamClock’s point of view, nothing changes — it connects to the same paths and receives the same data formats, without any firmware modification. We are very close to replicating nearly every possible data source and making slight improvements along the way.
The system is free, open-source, and designed to run locally on a small Linux system, allowing individual hams or clubs to keep existing HamClocks fully operational. The goal is preservation, not reinvention — keeping HamClock working exactly as intended for years to come.
Currently, open-hamclock-backend is designed to be self-hosted, requiring any user wishing to extend HamClock’s usefulness beyond June to run the software themselves. However, options are being considered for a centralized version to be stood up for all HamClock users to take advantage of.
Source: open-hamclock-backend
No comments:
Post a Comment