I think with more outdoor activities, it's important to know what is waiting you in a few hour. For cycling example wind and rain information is rather good to know.
xz most likely wasn't the only library that was targeted, there could be other similar projects as well which we haven't discovered yet. From the timeline you can see the social engineering part was quite big part.
Just thinking out loud, would it possible to go over with LLM and analyse existing OSS mailing lists and issues to classify such sentiment from the users?
I am using a similar structure a single text file usually split by each day, which also gives a good start to writing my standup notes.
I tried to avoid bringing in some strange formatting rules etc, quite free form. With a single file, it's effortless to go back and find out maybe why something was done in that way or why it wasn't done at all.
Looks kind of like a work diary to me, I have seen people trying to do a similar thing by bringing too much structure/org modes etc and making it so complicated that they forgot at first why they are doing it.
Here is my ~75euros ESP32 eink panel experiment: https://github.com/riston/eink-assist-screen/tree/main