Differences

This shows you the differences between two versions of the page.

--- blog:2026:1114_new_life_for_hamclock [2026/11/14 11:36] – created davek
+++ blog:2026:1114_new_life_for_hamclock [2026/11/14 16:21] (current) – davek
@@ Line 5: / Line 5: @@
 The HamClock connects to a backend server to get its data. Elwood had maintained a server at [[https://web.archive.org/web/20250407151450/https://www.clearskyinstitute.com/ham/HamClock/|clearskyinstitute.com/ham/HamClock]].
-Sadly, Elwood passed away in Jan of 2026. While the HamClock client was fully open source and MIT licensed, the backend server was not available. According to Elwood's post, clearskyinstitute.com would stop functioning in June 2026.
+Sadly, Elwood passed away in Jan of 2026. While the HamClock client was fully open source and MIT licensed, the backend server and source were not available. According to Elwood's post, clearskyinstitute.com would stop functioning in June 2026.
-I immediately wondered if I could create a backend. Boy, I didn't appreciate the complexity of that at first. I connected with Brian who had already made create progress creating source code for a back end. I jumped in to dockerize it and make it easier for people to host their own. It's fully open source and AGPLv3 licensed, and can be found here: https://github.com/openhamclock/open-hamclock-backend.
+====== ======
+I immediately wondered if I could create a backend. Boy, I didn't appreciate the complexity of that at first. I connected with Brian who had already made great progress creating source code for a back end. I jumped in to dockerize it and make it easier for people to host their own. It's fully open source and AGPLv3 licensed, and can be found here: https://github.com/openhamclock/open-hamclock-backend.
 By around April or so Chris, G1FEF, joined us and contributed servers in his data center to host https://ohb.hamclock.app. He also set up [[https://ohb.works|OHB Works]] where we can track the deployment of the backend, development of the backend and development of the client.
@@ Line 13: / Line 15: @@
 By May or so, Brian and I had OHB (Open HamClock Backend) feature complete and we had a few hundred users connecting to ohb.hamclock.app.
-Shortly after we started working on HamClock and created a GitHub for it at: https://github.com/openhamclock/hamclock
+Shortly after we started working on HamClock and created a GitHub for it at: https://github.com/openhamclock/hamclock.
-And Udo N0LSR joined in to rewrite and expand the user guide.
+Udo N0LSR joined in to rewrite and expand the user guide.
 At first it was in my GitHub account but then we set up a GitHub organization and have multiple other projects supporting HamClock: https://github.com/openhamclock