More email updates.

n0mn0m · n0mn0m · commit 4ddf9ac840be · 2025-08-31T20:35:29.000-04:00
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -49,7 +49,7 @@ This is an overview of the contribution workflow:
 - Test
 - If applicable make sure formatting rules are applied
 - [Email](https://www.devroom.io/2009/10/26/how-to-create-and-apply-a-patch-with-git/) a [patchset](https://www.devroom.io/2009/10/26/how-to-create-and-apply-a-patch-with-git/)
-  to n0mn0m@burningdaylight.io
+  to alexander.hagerman@icloud.com
 
 ## Verified commits with GPG
 
diff --git a/content/blog/posts/2018-06-29-recursive-search-with-python.md b/content/blog/posts/2018-06-29-recursive-search-with-python.md
@@ -96,4 +96,4 @@ For more information documentation on copy and future you can check out the docu
 
 I’m sure others will have different ideas and approaches to something like this. Or you might have suggestions on
 something that could be done to make this faster or easier to read. If you have feedback or suggestion feel free to send
-them my way via up via [email](mailto:n0mn0m@burningdaylight.io).
+them my way via up via [email](mailto:alexander.hagerman@icloud.com).
diff --git a/content/blog/posts/2018-12-22-docker-airflow.md b/content/blog/posts/2018-12-22-docker-airflow.md
@@ -207,4 +207,4 @@ The experience hasn’t been without it’s issues. The highlights are:
 Hopefully this post helps you get started with [docker-airflow](https://github.com/puckel/docker-airflow). If you have
 questions or want to share something cool that you end up doing feel free to open up
 an [issue](https://todo.sr.ht/%7En0mn0m/Airflow-Bugs) on Sourcehut or reach out to
-me [n0mn0m@burningdaylight.io](mailto:n0mn0m@burningdaylight.io).
+me [alexander.hagerman@icloud.com](mailto:alexander.hagerman@icloud.com).
diff --git a/content/blog/posts/2019-03-31-what-is-odbc-part-1-of-3.md b/content/blog/posts/2019-03-31-what-is-odbc-part-1-of-3.md
@@ -50,7 +50,7 @@ driver layer with Python and pyodbc looking to trace internals and see exactly h
 ### Contact
 
 If you have experience with ODBC internals, want to correct something I’ve written or just want to reach out feel free
-to follow up via [email](mailto:n0mn0m@burningdaylight.io) or on .
+to follow up via [email](mailto:alexander.hagerman@icloud.com) or on .
 
 I also have a [repo](https://github.com/n0mn0m/presentations) with the material I used for a presentation on this at
 the [Louisville DerbyPy](https://www.meetup.com/derbypy/) meetup in March of 2019.
diff --git a/content/blog/posts/2019-05-18-what-is-odbc-part-2-of-3.md b/content/blog/posts/2019-05-18-what-is-odbc-part-2-of-3.md
@@ -41,7 +41,7 @@ to trace internals and see exactly how and where different layers connect.
 ### Contact
 
 If you have experience with ODBC internals, want to correct something I’ve written or just want to reach out feel free
-to follow up via [email](mailto:n0mn0m@burningdaylight.io) or on .
+to follow up via [email](mailto:alexander.hagerman@icloud.com) or on .
 
 I also have a [repo](https://github.com/n0mn0m/presentations) with the material I used for a presentation on this at
 the [Louisville DerbyPy](https://www.meetup.com/derbypy/) meetup in March of 2019.
diff --git a/content/blog/posts/2019-05-24-what-is-odbc-part-3-of-3.md b/content/blog/posts/2019-05-24-what-is-odbc-part-3-of-3.md
@@ -60,7 +60,7 @@ breakpoint set --file getdata.cpp --line 776runIn case it is helpful you can fin
 ### Contact
 
 If you have experience with ODBC internals, want to correct something I’ve written or just want to reach out feel free
-to follow up via [email](mailto:n0mn0m@burningdaylight.io) or on .
+to follow up via [email](mailto:alexander.hagerman@icloud.com) or on .
 
 I also have a [repo](https://github.com/n0mn0m/presentations) with the material I used for a presentation on this at
 the [Louisville DerbyPy](https://www.meetup.com/derbypy/) meetup in March of 2019.
diff --git a/content/blog/posts/2019-07-14-creating-a-con-badge-with-pyportal.md b/content/blog/posts/2019-07-14-creating-a-con-badge-with-pyportal.md
@@ -116,7 +116,7 @@ many people have been incredibly patient and helpful as I learn and ask question
 ### Contact
 
 I've really enjoyed working on this project. If you want to reach out feel free to follow up
-via [email](mailto:n0mn0m@burningdaylight.io) or on.
+via [email](mailto:alexander.hagerman@icloud.com) or on.
 
 You can find out more about the badge and source code in the [repo](https://github.com/n0mn0m/gencon-portal)
 
diff --git a/content/blog/posts/2019-08-04-connected-roomba---wrapping-up.md b/content/blog/posts/2019-08-04-connected-roomba---wrapping-up.md
@@ -61,4 +61,4 @@ books and boards I am sure I will be busy expanding my understanding for the nex
 ### Contact
 
 I really enjoyed working on this project. If you want to reach out feel free to follow up
-via [email](mailto:n0mn0m@burningdaylight.io) or on .
+via [email](mailto:alexander.hagerman@icloud.com) or on .
diff --git a/content/blog/posts/2019-09-27-hackaday-connected-world-follow-up.md b/content/blog/posts/2019-09-27-hackaday-connected-world-follow-up.md
@@ -33,5 +33,5 @@ you Hackaday, DigiKey and OSHPark for kick starting this new learning path :).
 
 ### Contact
 
-If you want to chat feel free to follow up via [email](mailto:n0mn0m@burningdaylight.io) or
+If you want to chat feel free to follow up via [email](mailto:alexander.hagerman@icloud.com) or
 on [Sourcehut](https://github.com/n0mn0m/gencon-portal).
diff --git a/content/blog/posts/2019-10-18-edgerouter-x-home-vpn-setup-pt-1.md b/content/blog/posts/2019-10-18-edgerouter-x-home-vpn-setup-pt-1.md
@@ -11,7 +11,7 @@ home setup isn’t too complicated, but it’s a bit different from other setups
 **Network Components: Arris Surfboard SB6141, Ubiquiti EdgeRouter X, Ubiquiti AmplifiHD**
 
 \*\*I am not a network or sysadmin by day. This is something I’m actively learning on and figuring out. If you see
-something wrong or have suggestions I would love to hear about it. \*\*[**Reach out.**](mailto:n0mn0m@burningdaylight.io)
+something wrong or have suggestions I would love to hear about it. \*\*[**Reach out.**](mailto:alexander.hagerman@icloud.com)
 
 ### Preparing the network
 
diff --git a/content/blog/posts/2019-10-18-edgerouter-x-home-vpn-setup-pt-2.md b/content/blog/posts/2019-10-18-edgerouter-x-home-vpn-setup-pt-2.md
@@ -6,7 +6,7 @@ page.meta.categories: programming
 ---
 
 **I am not a network or sysadmin by day. This is something I’m actively learning on and figuring out. If you see
-something wrong or have suggestions I would love to **[**hear about it**](mailto:n0mn0m@burningdaylight.io)**.**
+something wrong or have suggestions I would love to **[**hear about it**](mailto:alexander.hagerman@icloud.com)**.**
 
 In [part one](https://burningdaylight.io/posts/edgerouter-x-vpn-setup-prt-one/) we configured the network. Now we are
 ready to install Wireguard and create our interface. Before I jumped into doing this I referenced these post and docs.
diff --git a/content/blog/posts/2020-01-24-connected-roomba---managing-state.md b/content/blog/posts/2020-01-24-connected-roomba---managing-state.md
@@ -111,4 +111,4 @@ our.
 
 By observing and understanding the ways in which the prototyped system failed I was able to identify areas where
 behavior and functionality could be simplified resulting in an overall more reliable system. If you have any other tips
-to share [reach out](mailto:n0mn0m@burningdaylight.io) and good luck hacking.
+to share [reach out](mailto:alexander.hagerman@icloud.com) and good luck hacking.
diff --git a/content/blog/posts/2020-02-08-train-all-the-things---planning.md b/content/blog/posts/2020-02-08-train-all-the-things---planning.md
@@ -43,4 +43,4 @@ a status update before they ever come down.
 
 The code, docs, images etc for the project can be found [here](https://github.com/n0mn0m/on-air) and I’ll be posting
 updates as I continue along to [HackadayIO](https://hackaday.io/project/170228-on-air) and this blog. If you have any
-questions or ideas reach [out](mailto:n0mn0m@burningdaylight.io).
+questions or ideas reach [out](mailto:alexander.hagerman@icloud.com).
diff --git a/content/blog/posts/2020-02-18-a-simple-status-page.md b/content/blog/posts/2020-02-18-a-simple-status-page.md
@@ -129,4 +129,4 @@ ergonomic at this time. Other than that my experience with Workers and K/V has b
 ideas for future experiments.
 
 The code, docs, etc for the project can be found [here](https://github.com/n0mn0m/system-status). If you have any
-questions or ideas reach [out](mailto:n0mn0m@burningdaylight.io).
+questions or ideas reach [out](mailto:alexander.hagerman@icloud.com).
diff --git a/content/blog/posts/2020-03-01-train-all-the-things---signaling.md b/content/blog/posts/2020-03-01-train-all-the-things---signaling.md
@@ -58,4 +58,4 @@ move on to the [display](https://burningdaylight.io/posts/train-all-the-things-d
 
 The code, docs, images etc for the project can be found [here](https://github.com/n0mn0m/on-air) and I’ll be posting
 updates as I continue along to [HackadayIO](https://hackaday.io/project/170228-on-air) and this blog. If you have any
-questions or ideas reach [out](mailto:n0mn0m@burningdaylight.io).
+questions or ideas reach [out](mailto:alexander.hagerman@icloud.com).
diff --git a/content/blog/posts/2020-03-05-train-all-the-things---display.md b/content/blog/posts/2020-03-05-train-all-the-things---display.md
@@ -80,4 +80,4 @@ FreeRTOS.
 
 The code, docs, images etc for the project can be found [here](https://github.com/n0mn0m/on-air) and I’ll be posting
 updates as I continue along to [HackadayIO](https://hackaday.io/project/170228-on-air) and this blog. If you have any
-questions or ideas reach [out](mailto:n0mn0m@burningdaylight.io).
+questions or ideas reach [out](mailto:alexander.hagerman@icloud.com).
diff --git a/content/blog/posts/2020-03-19-train-all-the-things---synthetic-generation.md b/content/blog/posts/2020-03-19-train-all-the-things---synthetic-generation.md
@@ -82,4 +82,4 @@ ideas on how to use those. If it does work the ability to generate training data
 Next up, training the model and loading to the ESP-EYE. The code, docs, images etc for the project can be
 found [here](https://github.com/n0mn0m/on-air) and I’ll be posting updates as I continue along
 to [HackadayIO](https://hackaday.io/project/170228-on-air) and this blog. If you have any questions or ideas
-reach [out](mailto:n0mn0m@burningdaylight.io).
+reach [out](mailto:alexander.hagerman@icloud.com).
diff --git a/content/blog/posts/2020-03-24-train-all-the-things---model-training.md b/content/blog/posts/2020-03-24-train-all-the-things---model-training.md
@@ -78,4 +78,4 @@ I (45634) HTTPSHANDLING: HTTPEVENTDISCONNECTEDThis was an educational experiment
 
 The code, docs, images etc for the project can be found [here](https://github.com/n0mn0m/on-air) and I’ll be posting
 updates as I continue along to [HackadayIO](https://hackaday.io/project/170228-on-air) and this blog. If you have any
-questions or ideas reach [out](mailto:n0mn0m@burningdaylight.io).
+questions or ideas reach [out](mailto:alexander.hagerman@icloud.com).
diff --git a/content/blog/posts/2020-03-28-train-all-the-things---version-0-1.md b/content/blog/posts/2020-03-28-train-all-the-things---version-0-1.md
@@ -28,7 +28,7 @@ The code, docs, images etc for the project can be found [here](https://github.co
 further updates to [HackadayIO](https://hackaday.io/project/170228-on-air). For anybody that might be interested in
 building this the instructions below provide a brief outline. Updated versions will be hosted in
 the [repo](https://github.com/n0mn0m/on-air/tree/main/docs). If you have any questions or ideas
-reach [out](mailto:n0mn0m@burningdaylight.io).
+reach [out](mailto:alexander.hagerman@icloud.com).
 
 **Required Hardware:**
 
diff --git a/content/blog/posts/2020-03-30-train-all-the-things---speed-bumps.md b/content/blog/posts/2020-03-30-train-all-the-things---speed-bumps.md
@@ -102,4 +102,4 @@ Approaching the end of this project it’s been a larger undertaking than I expe
 definitely generated a few new project ideas. The code, docs, images etc for the project can be
 found [here](https://github.com/n0mn0m/on-air) and I’ll be posting updates as I continue along
 to [HackadayIO](https://hackaday.io/project/170228-on-air) and this blog. If you have any questions or ideas
-reach [out](mailto:n0mn0m@burningdaylight.io).
+reach [out](mailto:alexander.hagerman@icloud.com).
diff --git a/content/blog/posts/2020-11-21-self-hosting.md b/content/blog/posts/2020-11-21-self-hosting.md
@@ -60,5 +60,5 @@ The service management can be found [here](https://github.com/n0mn0m/arcade.git/
 I’ve started to self host a few times in the past and backed away. This time I think it’s here to stay. With my current
 setup I’m not worried about what happens when something crashes, certificate management is automated away and everything
 just works. I’ve linked to my orchestration code above, but if you have any questions, or suggestions send
-them [my way](mailto:contact@burningdaylight.io). If you are starting out on your own self hosted setup, good luck, have
+them [my way](mailto:alexander.hagerman@icloud.com). If you are starting out on your own self hosted setup, good luck, have
 fun it’s easier now than ever and I imagine it will continue to get better.
