#hardenedbsd

#Radicle is working fine for #HardenedBSD src and ports between two laptops on the same physical network. But, it's not working in the slightest on the HardenedBSD infrastructure. I cannot get the seed node fully fetching the repos. Radicle just times out. The biggest issue is that it will try to restart the fetch from the very beginning upon failure. So we're transmitting the same exact data many, many, many, many, many, many times only to end up failing again. Radicle should probably archive the data at the point of failure, then when restarting the fetch, it can start from where it left off. Otherwise, we're experiencing first-hand the populist definition of insanity: doing the same thing over and over and over again but expecting different results.

#HardenedBSD HEADS UP: Our oligarchic overlords with their legion of AI bots have decided that our GitLab isn't powerful enough to line their pockets with our code. I've now powered off our self-hosted GitLab and disabled the autosync. I'll pull an all-nighter tonight to see if we can switch to Radicle. If that fails, I'm not sure what to do. It's evident that we need a whole new fleet of servers just to handle the load and ain't nobody got funds for that.