@HankB @sutaio I see a problem that these notes often contain information how to recover from hard disk failure, kernel failure or PC hardware failure.

I assume Markdown, Mkdocs and a Forgejo Git server don't work when PC fails to boot up, hard disk fails or the PCI bus fails (which happened to me twice due to corrosion of the RPi motherboard which I successfully solved by copious washing in vinegar, tap water and many hours drying in front of a fan). I fixed several hard disk failures successfully by overwriting the area with faulty recording with fresh signal, but for this the writes have to be properly aligned and manually entered.

I doubt they will be able to do changes into Markdown, Mkdocs and a Forgejo Git server so that they would work even when the PCI bus or hard disk fails or the PC fails to boot, so I will stay with a biro and paper notebooks. They are more robust, resilient and reliable.

#complexity #unreliability #failure #robustness #resilient #resiliency #durability

Hi @JulianOliver,
frankly I am not at all surprised. When github.com got bought, I felt this wasn't a place to stay and looked around where to go in the longer run. gitlab.com wasn't a safe bet already back then - the smell of #enterprise/ #corporate & #VC #money was strong.
I took the indie & mirror route and never regret it: https://blog.mro.name/2024/10/scaling-infrastructure/#:~:text=gitlab%2Ecom

Be #vulnerable!
Be #resilient!
Practise #solidarity