From 1b93880d9738a5cd70ed1e7c5ce90c0dafce61ab Mon Sep 17 00:00:00 2001 From: KOTP Date: Wed, 29 Jan 2025 20:49:18 -0500 Subject: Spelling "Fore" -> "For" Also attends to some trailing white space that seems atypical. --- posts/New_Domain_and_Code_Forge.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/posts/New_Domain_and_Code_Forge.md b/posts/New_Domain_and_Code_Forge.md index f02db18..c008a76 100644 --- a/posts/New_Domain_and_Code_Forge.md +++ b/posts/New_Domain_and_Code_Forge.md @@ -10,7 +10,7 @@ But enough introductions, let's get into it! I've abandoned `bt.ht`. Well, kind of. That domain doesn't expire until 2025, which works out nicely since I can keep a complete web forward active for the entire year. This will avoid such a radical switch, similar to what I did years ago with my "uglyduck" domain[^1]. Hopefully anyone who follows my dumb ramblings will have more than enough time to become familiar with the new URL. -For reference, those interested in updating their RSS will need to use the latest URLs: +For reference, those interested in updating their RSS will need to use the latest URLs: - [RSS](https://btxx.org/index.rss) - [Atom](https://btxx.org/index.atom) @@ -32,7 +32,7 @@ So that's what I've done. ## My Own Code Forge -As some people in the open source community might already be aware, [sourcehut](https://sourcehut.org) had a major outage a couple weeks back. It lasted a few days and all services were impacted. This meant that all publicly hosted websites, build processes and `git` repositories were unavailable. It was no fault of sourcehut of course, they were viciously attacked for no *real* reason. +As some people in the open source community might already be aware, [sourcehut](https://sourcehut.org) had a major outage a couple weeks back. It lasted a few days and all services were impacted. This meant that all publicly hosted websites, build processes and `git` repositories were unavailable. It was no fault of sourcehut of course, they were viciously attacked for no *real* reason. But this outage did get me thinking about what it means to "control" my own code. I always liked the idea of hosting my own git projects but relied on third-party services since they were more convenient. The problem with entrusting anything, not just code storage, to third-party services is lack of oversight. You really have no idea what is happening behind the scenes. You don't control your own backups. You don't have the freedom to tweak UI or user flow of your project views (which I understand is certainly an edge-case). @@ -46,7 +46,7 @@ I'll save you the suspense: I went with cgit. Getting GitWeb configured properly I still need to go through most of the existing projects on sourcehut and update their READMEs and purge the contents. The last thing I want to do is have users confused about which repo is the "real" one. -Fore reference the my repos are now located here: [git.btxx.org](https://git.btxx.org) +For reference the my repos are now located here: [git.btxx.org](https://git.btxx.org) (I plan to place this in the main navigation soon...) @@ -59,4 +59,4 @@ I'm aware that to have extra protection from "downtime" that I should also mirro My code forge is far from perfect. Mobile view is lacking, there is no dark mode support and things could be slightly more intuitive. But I love it. The beauty of hosting everything on my own is that I can improve these things myself. For now, I'm happy with the outcome! -[^1]: Someone oddly picked up that domain and piggybacked off the back-links. They happen to also be a designer...Guess the naming was that cool? +[^1]: Someone oddly picked up that domain and piggybacked off the back-links. They happen to also be a designer...Guess the naming was that cool? -- cgit v1.2.3-70-g09d2