From 6b9bcf8096963abb0a3de7748ebeaa8d5fb4aeb60713a6771099b173ce89c9c3 Mon Sep 17 00:00:00 2001 From: Nicholas Johnson Date: Wed, 5 Feb 2025 00:00:00 +0000 Subject: Replace instances of 'Gitlab' with 'GitLab' 'GitLab' is the correct spelling. --- content/entry/dont-use-github.md | 4 ++-- content/entry/journal-update-018.md | 2 +- content/entry/shouting-into-the-void.md | 2 +- content/entry/site-update-008.md | 2 +- content/entry/site-update-009.md | 2 +- content/entry/site-update-011.md | 2 +- content/entry/site-update-012.md | 2 +- content/entry/site-update-013.md | 2 +- 8 files changed, 9 insertions(+), 9 deletions(-) (limited to 'content') diff --git a/content/entry/dont-use-github.md b/content/entry/dont-use-github.md index 896d8f0..80c4247 100644 --- a/content/entry/dont-use-github.md +++ b/content/entry/dont-use-github.md @@ -10,12 +10,12 @@ Free software being hosted on GitHub as its main repository is a downright embar You can see more criticism of GitHub here: [Tom Ryder's Blog](https://sanctum.geek.nz/why-not-github.html) -As a user of software and someone that occasionally writes software, I have a lot more respect for your project if it's not hosted on GitHub. There are so many other code hosting platforms out there! There's Gitlab, Gitea, Gogs, Cgit and Gitweb. Hell, you don't even need a code hosting repository! If you can't self-host and don't want to trust third-party platforms, just use Git's git-format-patch command and submit changes by email. +As a user of software and someone that occasionally writes software, I have a lot more respect for your project if it's not hosted on GitHub. There are so many other code hosting platforms out there! There's GitLab, Gitea, Gogs, Cgit and Gitweb. Hell, you don't even need a code hosting repository! If you can't self-host and don't want to trust third-party platforms, just use Git's git-format-patch command and submit changes by email. Having a single large megacorp whose primary business model is diametrically opposed to free software being the largest code host for free software is almost too dumb. Micro$oft is the worst possible entity to entrust to run the platform where you manage development of your free software projects. If you're using GitHub to host your code, migrate elsewhere immediately. # Other Code Repositories -If you choose to migrate to Gitlab.com, that's still pretty centralized since it's one of the largest code hosting platforms. But at least Gitlab doesn't require non-free JavaScript, its backend is fully free and it's not owned by Micro$oft. Also, self-hosting is very easy if you have the resources. I recommend reading the GNU repo criteria evaluation page before you make your choice where to migrate: +If you choose to migrate to GitLab.com, that's still pretty centralized since it's one of the largest code hosting platforms. But at least GitLab doesn't require non-free JavaScript, its backend is fully free and it's not owned by Micro$oft. Also, self-hosting is very easy if you have the resources. I recommend reading the GNU repo criteria evaluation page before you make your choice where to migrate: [https://www.gnu.org/software/repo-criteria-evaluation.html](https://www.gnu.org/software/repo-criteria-evaluation.html) # Harm Reduction diff --git a/content/entry/journal-update-018.md b/content/entry/journal-update-018.md index 5900762..0f93982 100644 --- a/content/entry/journal-update-018.md +++ b/content/entry/journal-update-018.md @@ -9,7 +9,7 @@ draft: false * Stopped accepting cryptocurrency donations. Proof-of-work cryptocurrencies waste obscene amounts of energy. Existing cryptocurrencies don't scale well. Their main use is crime and speculation on crime. The market is full of scams and false promises. No one really knows how to value them. They are potentially a systemic risk to the economy. So I do not wish to be involved any more. It's not like this journal costs much to run anyways. * Entry summaries have been removed. I believe the title alone should be sufficient to communicate an entry's subject matter. * Pagination and read time have been removed to simplify the journal layout. These features may be added back later after the scripts rewrite if I decide they further journal design goals. The goal of the design of this journal is to be minimally distracting and respect reader attention. -* Replaced Gitlab mirror with [SourceHut](https://sourcehut.org/). SourceHut has many benefits over Gitlab. It doesn't [assist ICE](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/30656). It doesn't require JavaScript unlike Gitlab. It's fast and resource efficient. It also supports Gemini, so all three journal mirrors now support both Gemini and the Web. +* Replaced GitLab mirror with [SourceHut](https://sourcehut.org/). SourceHut has many benefits over GitLab. It doesn't [assist ICE](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/30656). It doesn't require JavaScript unlike GitLab. It's fast and resource efficient. It also supports Gemini, so all three journal mirrors now support both Gemini and the Web. * Added [I2P support](http://nick5la4gcv6tzdjk2pf55p5vi24pcxseioyko24ffd4x3uijdca.b32.i2p) for CGit instance. * Added [I2P](gemini://nick6w7lwwzwli57czw5glh3sm2qhnyzbhtq3nohbcnc7j3wqmqq.b32.i2p) and [Tor support](gemini://nick6gsepvtmkcpibpid6dqtqroxt62u6ab4ep65vxrenffruumj6jad.onion) on Gemini's main mirror. Readers can now browse the Nicksphere privately and without a Web Browser. * Replaced nicksphere-gmi's Gemini to HTML Go library with [my own](https://archive.softwareheritage.org/swh:1:snp:a993794ad9e5e68d1d6319d7d735de3c62f66b18;origin=https://git.nicholasjohnson.ch/gemini2html), written in C. Journal generation is now much faster. diff --git a/content/entry/shouting-into-the-void.md b/content/entry/shouting-into-the-void.md index 337b7bf..e9fbfe4 100644 --- a/content/entry/shouting-into-the-void.md +++ b/content/entry/shouting-into-the-void.md @@ -13,7 +13,7 @@ I want to reach a wide audience. I want my ideas to make a difference in the wor I plan to start keeping track of how many site requests are made. Right now, my only metric for estimating read count is the occasional email I receive. If you would, please [email me](/about/) letting me know how often you read this journal, which platform you're using to access it, and any other demographic information you're comfortable providing so I get an idea of my audience. -I have no way to collect analytics for Flounder, Gitlab, Gemini, Freenet, or Zeronet. I'm against adding tracking scripts on the web version of this journal. Page views don't necessarily translate into interested readers and that's about all I can see. So if you're reading this, I'm counting on your input. But I digress. +I have no way to collect analytics for Flounder, GitLab, Gemini, Freenet, or Zeronet. I'm against adding tracking scripts on the web version of this journal. Page views don't necessarily translate into interested readers and that's about all I can see. So if you're reading this, I'm counting on your input. But I digress. I've been thinking it would be nice if I had a way to monetize my writing. Donations aren't working but I'm uncomfortable with my ideas being restricted from people just because they don't have enough funds. So I'll always make my thoughts available through my writing on a "pay what you want" basis, even if that payment is zero. If I decide to try my hand at writing ebooks rather than online journal entries, I'll give the ebooks away for free with the option of payment. diff --git a/content/entry/site-update-008.md b/content/entry/site-update-008.md index 9e53e70..9eccc74 100644 --- a/content/entry/site-update-008.md +++ b/content/entry/site-update-008.md @@ -8,7 +8,7 @@ draft: false It seems I'm making update posts more often than I imagined, but it's fine. I'm going to try out a list format for this one. * Change "recommendation" tag to more specific tags. (e.g., "books", "videos") -* Sign commits on GitHub/Gitlab so users can [TOFU](https://en.wikipedia.org/wiki/Trust_on_first_use) this blog +* Sign commits on GitHub/GitLab so users can [TOFU](https://en.wikipedia.org/wiki/Trust_on_first_use) this blog * Minify HTML and CSS # Future Plans diff --git a/content/entry/site-update-009.md b/content/entry/site-update-009.md index 7614e5a..718f932 100644 --- a/content/entry/site-update-009.md +++ b/content/entry/site-update-009.md @@ -9,7 +9,7 @@ I haven't posted anything for a while and I've been working behind the scenes to * Output RSS content as full post content rather than mere content summaries for better accessibility to RSS users. * Move the custom inline CSS to the external stylesheet. -* The site's GitHub and Gitlab CI workflows that host the site mirrors have been fixed. Before, I was locally generating files and uploading them as a single commit. Now, I upload the source files and let the remote servers do the work. +* The site's GitHub and GitLab CI workflows that host the site mirrors have been fixed. Before, I was locally generating files and uploading them as a single commit. Now, I upload the source files and let the remote servers do the work. * Launch Gitea server on new subdomain (https://git.0gitnick.xyz) to host site content and theme for better organization and transparency in generating the site. The reason I did not go with Savannah as I planned in my last site update is because Savannah has very strict licensing requirements. Since my site is forked and I might fork more projects in the future, I'd rather not spend hours fixing license text before I can even upload the project. I have no problem with meticulously licensing my own work. It would just be too demotivating to do that for someone else's work. * Write content summaries for every post. This was very tedious but worth it. It makes the site more aesthetically pleasing and much easier to follow. It's my own fault for not doing this from the beginning. * Add Ethereum address and tokens for more donation options. diff --git a/content/entry/site-update-011.md b/content/entry/site-update-011.md index f1cb5cf..c2636a7 100644 --- a/content/entry/site-update-011.md +++ b/content/entry/site-update-011.md @@ -16,7 +16,7 @@ I paused posts because I've been busy migrating my blog to [Gemini](Gemini speci * All tags and separate feeds are gone. I don't feel like the tagging system was very valuable. I often didn't know what to tag my posts or whether to create a new tag for them or remove a tag. Now I don't have to think about it. I can get on with just doing what I like which is writing posts. As for you readers of my blog, I have doubts that anyone much uses the tags anyway. Reading the title and summary probably does more to help readers make a judgment if they want to read that post than tags. I would've had to reimplement them in my content management system and it didn't seem worth the work. # Future Plans -* Write configuration files for CI pipelines so the GitHub and Gitlab site mirrors work again. Since I'm using a content management system I wrote myself, I also have to write the CI pipeline configuration for generating the site myself and I haven't gotten to it yet. +* Write configuration files for CI pipelines so the GitHub and GitLab site mirrors work again. Since I'm using a content management system I wrote myself, I also have to write the CI pipeline configuration for generating the site myself and I haven't gotten to it yet. Ignore what site update 10 says about the repos. It only makes sense to have 1 repo to maintain content on Gemini and the Web. The repo nicksphere-www is deprecated. It will no longer be used at all. The canonical repo for my content is now nicksphere-gmi. It contains generator scripts for Gemini and the web as well. It still needs work such as the CI pipelines, but it's close enough to use for my capsule and my site now. diff --git a/content/entry/site-update-012.md b/content/entry/site-update-012.md index 45f4c94..b16e0bf 100644 --- a/content/entry/site-update-012.md +++ b/content/entry/site-update-012.md @@ -6,7 +6,7 @@ draft: false --- # What's New * The wonky CSS is fixed. The result is the site is much more presentable and easy to read on mobile and desktop. Specifically, the spacing is more consistent. -* Gitlab pages now correctly generates my website using .gitlab-ci.yml. I deleted my GitHub mirror since I didn't want to write a CI script to support the proprietary GitHub pages system. +* GitLab pages now correctly generates my website using .gitlab-ci.yml. I deleted my GitHub mirror since I didn't want to write a CI script to support the proprietary GitHub pages system. * New Privatebin instance on the bin subdomain # Future Plans diff --git a/content/entry/site-update-013.md b/content/entry/site-update-013.md index 56ac314..796e991 100644 --- a/content/entry/site-update-013.md +++ b/content/entry/site-update-013.md @@ -8,7 +8,7 @@ draft: false * Full content [Atom feeds](/atom.xml) have returned. Before Gemini, I had a full content web feed, not just the summaries. After Gemini, I changed it to summaries only. Now, full content is supported again along with summaries. It was a mistake adding Gemini without full content web feed support. I shouldn't have taken that feature away from readers without warning. I was just so focused on getting Gemini that I ditched the web feed to roll that out early. Apologies to anyone using it. I don't really care how readers access my blog as long as they're reading it and I want to make it as accessible as possible for everyone. * New [content submodule](https://archive.softwareheritage.org/swh:1:snp:14fb224d5e13136ac433bb459e3803aed63a0bb7;origin=https://git.nicholasjohnson.ch/nicksphere-gmi-content). This almost entirely separates the text on my blog from everything else, significantly reducing the number of files in the main repository. I did this to create a logical separation between the text on the blog and everything used to generate/display that text. * Clearer licensing. The licensing was unclear before because I didn't clearly indicate which licenses went with which files. Now that content and scripts live in separate repositories, the main repo can use GPLv3 exclusively and the content CC BY-SA 4.0 exclusively. -* Gitlab pages is fixed as of [this commit](https://archive.softwareheritage.org/swh:1:rev:3ea0615f72fcae2d345f239569019429c5d5d168;origin=https://git.nicholasjohnson.ch/nicksphere-gmi;visit=swh:1:snp:fb9bef300f9b939382f5656232d95377c8630a10#swh-revision-changes). Before, it wasn't recursively cloning the new content submodule, so the generation process was failing and the mirror was down for a while. +* GitLab pages is fixed as of [this commit](https://archive.softwareheritage.org/swh:1:rev:3ea0615f72fcae2d345f239569019429c5d5d168;origin=https://git.nicholasjohnson.ch/nicksphere-gmi;visit=swh:1:snp:fb9bef300f9b939382f5656232d95377c8630a10#swh-revision-changes). Before, it wasn't recursively cloning the new content submodule, so the generation process was failing and the mirror was down for a while. * GNU Audio Video mirror link added. I'm now mirroring all the GNU audios and videos. Before I had the A/V on the mirrors subdomain and A/V links weren't working that way. I realized that particular mirror requires its own domain to display properly, so now it has one. # Future Plans -- cgit v1.2.3