Login
You're viewing the gulp.cafe public feed.
  • Apr 23, 2026, 1:35 AM

    #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.

    💬 1🔄 0⭐ 0

Replies

  • 💬 0🔄 0⭐ 0
  • Apr 23, 2026, 1:41 AM

    I'm 100% out of ideas. Our servers cannot handle the load the AI/LLM web scraping bots place on #GitLab. #Radicle is turning out to still not be ready for prime-time. I refuse to use #GitHub beyond being a read-only mirror.

    Self-hosting our code repos is an absolute requirement in order to provide higher levels of OPSEC than what third-party hosted services can provide.

    So, at the hands of our oligarchic overlords, is this the death of HardenedBSD?

    Someone please provide me ideas. I have no idea what to try next and I'm desperate.

    💬 0🔄 1⭐ 0
  • Apr 23, 2026, 4:15 AM

    I've got things working! I now suspect the problem was my Framework16 laptop, not the server.

    Directing #Radicle to point to my other laptop for the initial seed fetch for both src and ports resulted in success!

    So we are officially on to the next step of the process: Integrate Radicle support into the #HardenedBSD ports tree.

    Now, time for sleep.

    💬 0🔄 0⭐ 0