Most other licenses including the MIT allow anyone to fork the project and redistribute it just like the GPL but the problem is the license can be changed to whatever the fork author wants. This also includes a proprietary license which goes against what I want out of a license. I want to prevent non-free software, I don't want to help non-free software.
- How are you helping non-free software?
Essentially I'm writing their software for them, so then they can just fork it and make proprietary spyware out of it. This has happened to many different projects and you can thank these licenses that don't prevent a license change for proprietary firmware and other nasty stuff that (probably) runs on your GNU/Linux box. Some people may argue that the GPL is actually non-free because it doesn't let you fork under another license but I heavily disagree
-
At first it may seem like that but as soon as someone forks your software and changes the license to a non-free license you have MORE proprietary spyware so in the end you're causing more problems than you're solving. The GPL essentially tries to end proprietary software by providing a license which guarantees freedom like I stated in my previous post. which is something I support. So that begs the question. Should you switch to the GNU GPLv3 license?
+
At first it may seem like that but as soon as someone forks your software and changes the license to a non-free license you have MORE proprietary spyware so in the end you're causing more problems than you're solving. The GPL essentially tries to end proprietary software by providing a license which guarantees freedom like I stated in my previous post. which is something I support. So that begs the question. Should you switch to the GNU GPLv3 license?
Now, I would like to add that if you're heavily against the GNU project or the Free Software Foundation due to Richard Stallman, then you probably do not want to use the GPL. And most of the time the people who choose to NOT use the GPL for this reason cannot actually find a justifiable reason for their choice. I don't know about you and it's not my decision but either way the GPL is just a software license and therefore it really doesn't matter who wrote it. Just know that by using a license that doesn't prevent/stop non-free software, you're making the world a worse place.
If your goal in addition to providing users with freedom and a great piece of software then the GPL is probably for you. The GPLv3 license guarantees freedom for anyone who uses the software. Therefore in my opinion by using the GPLv3 license you are making the world a better place by stopping potential proprietary software.
Windows/macOS users often call me an elitist GNU/Linux user but is that really deserved? Well, I personally don't think or care too much about people's opinions on me. After all, I have better things to do and since it's so common to call GNU/Linux users 'elitist', it doesn't really mean anything to me.
However, since this is so common I wanted to find this out for myself. So let's think for a moment here? Why do I write blog posts just like the one you're reading?
-
Well, for me it's because it allows me to say exactly what I think whenever I want. It's a nice way to (sometimes) express your anger at something. However I don't really view myself as an elitist. After all, I write blog posts like this one and write guides like this one. I went out of my way to help new GNU/Linux users in this case install Arch.
+
Well, for me it's because it allows me to say exactly what I think whenever I want. It's a nice way to (sometimes) express your anger at something. However I don't really view myself as an elitist. After all, I write blog posts like this one and write guides like this one. I went out of my way to help new GNU/Linux users in this case install Arch.
If I was an elitist I'd tell you to 'RTFM' like every Arch user ever. Instead I went out of my way to help you get started with Arch.
What I'm not about to do however is read the 'FM' for you. If you aren't capable of reading plain English then I will call you exactly what I view you as, an idiot or a normie.
In addition to this, it ALWAYS seems like the people calling me an elitist are part of this group. People who will complain about something being difficult without having the patience to read and perform. They will call anyone who uses software that they view difficult to use (for example Gentoo, Arch, or suckless software) an elitist. They can't seem to find one reason why anyone would actually want to use said software except to look cool on the internet.
This might actually be my last blog post.. sort of. Now that I have your valuable attention, please read the rest of the blog post!
So, a few days ago I started working on a website redesign. However I quickly realized that it was more work than it was worth. So instead, I decided that it would be easier to straight up start from scratch. No, not completely from scratch, that would be ridiculously time consuming.
However I decided that it would be easier to create the HTML manually, from scratch and then copy over the text (such as blog posts) from the older page.
-
Anyways, let's get to the point of this blog post which is, I need suggestions regarding the redesign. Anything. What should I implement, what kind of design should I go for? This time, I am able to use PHP for the header, which I will likely end up doing however as always, speedie.gq will stay as an anti-JavaScript website and as such, I am not going to add a single line of it even if it makes my website look nicer.
+
Anyways, let's get to the point of this blog post which is, I need suggestions regarding the redesign. Anything. What should I implement, what kind of design should I go for? This time, I am able to use PHP for the header, which I will likely end up doing however as always, speedie.site will stay as an anti-JavaScript website and as such, I am not going to add a single line of it even if it makes my website look nicer.
Here are some ideas I've got myself:
About me page
About me page, which will contain information about me, and the software I use.
-
Separate 'Projects' category (for example, https://speedie.gq/projects/speedwm)
+
Separate 'Projects' category (for example, https://speedie.site/projects/speedwm)
Right now, project pages are all over the place and difficult to find. Therefore I think it would be much easier to have a projects category.
-
Separate 'Blog' category (for example, https://speedie.gq/blog/post01.html)
+
Separate 'Blog' category (for example, https://speedie.site/blog/post01.html)
There are now many blog posts, and the one you're reading only makes the problem worse. Because of this, I need a way to make them easier to sort and keep track of.
Header and Footer done using PHP
In my opinion, this is the most important part. Otherwise, If I want to change one thing in the header, I have to manually edit every single HTML file in the website. Doing so can take a very very long time.
If you are here for the Wii specific things such as my forwarders, consider joining the r/WiiHacks Discord server. They are essentially us done right, and stay on topic well.
Again, all Wii repositories will stay up. Any Discord specific content is also going to be uploaded to these repositories to make sure nothing gets lost. That's what we tried to prevent in the beginning, right?
-
Either way, with that being said, if you'd like to keep up with me and/or my projects, I have a website at speedie.gq where I post the current information. In fact I may post this on my website too! As for the staff members here, simply ask them!
+
Either way, with that being said, if you'd like to keep up with me and/or my projects, I have a website at speedie.site where I post the current information. In fact I may post this on my website too! As for the staff members here, simply ask them!
I would like to give a big thank you to:
Gabubu for being an awesome friend, moderator, forwarder creator and of course helping preserve rare forwarders.
We're back up better than ever! Right when the canonicucks thought I was gone for good, I rise from my grave and bring you a new website and blog post. Okay, okay on a serious note I have some very important news to share with the people who (still) follow my blog.
-
Solving the existing problem with speedie.gq
-
Maintaining the speedie.gq website has been a struggle and it only gets worse with every blog post and page I create.
+
Solving the existing problem with speedie.site
+
Maintaining the speedie.site website has been a struggle and it only gets worse with every blog post and page I create.
I thought about my alternatives for solving this or at least improving on it, things like using Markdown, writing a simple shell script to append text or even stupid static site generators, but in the end I decided to go with PHP. And it makes sense, PHP is a solid option and has been around for years.
It has a major flaw in what I am trying to accomplish with it and that is server-side code that the user can't see. Of course the source code for the PHP is public and available for everyone.
I have and will continue to publish all changes made to the PHP to the Codeberg repository but you have no way to verify that the code is identical to what is running on the server. I am not sure if there is any way to prove this to the users of my website but if there is, let me know and I'll gladly provide.
@@ -26,7 +26,7 @@
I installed OpenBSD on it because it is a great system for building secure servers but importantly it uses LibreSSL which was something I really wanted for this website.
Issues
OpenBSD works a little differently than the GNU/Linux I am used to so this took a bit of work to figure out. Most of my issues were PHP related because it's much harder to set up on BSD.
-
While the website still has a few flaws that I plan on fixing very soon (https://speedie.gq/projects doesn't lead to projects.php and instead results in an 'Access Denied.' from Apache), the website seems to be work fine.
+
While the website still has a few flaws that I plan on fixing very soon (https://speedie.site/projects doesn't lead to projects.php and instead results in an 'Access Denied.' from Apache), the website seems to be work fine.
Website rewrite
So, let's talk about the website itself.
First of all, just take a look around. The website has been rewritten from scratch, this time using PHP for the header and footer. This allows changes to be easily made to the header for every single document (there were a lot of them) saving time.
diff --git a/articles/post43.php b/articles/post43.php
index 1ee786f..1ce3701 100644
--- a/articles/post43.php
+++ b/articles/post43.php
@@ -2,23 +2,23 @@
-speedie.gq now has a wiki!
+speedie.site now has a wiki!
-
+
-
speedie.gq now has a wiki!
+
speedie.site now has a wiki!
2023-01-26
-
This is just a brief blog post regarding some new somewhat important news for this website! speedie.gq has received a wiki, which anyone may edit. No, this is not some bloated wiki solution, it's done using purely PHP and CSS, and articles are written in Markdown! This is great, because speedwm documentation is already written in Markdown and has been for a while. Not only that, but speedwm has it's own separate wiki, because a lot of information is speedwm related.
+
This is just a brief blog post regarding some new somewhat important news for this website! speedie.site has received a wiki, which anyone may edit. No, this is not some bloated wiki solution, it's done using purely PHP and CSS, and articles are written in Markdown! This is great, because speedwm documentation is already written in Markdown and has been for a while. Not only that, but speedwm has it's own separate wiki, because a lot of information is speedwm related.
Now, I want to get speedwm 1.9 out soon, especially since it has been two full months since the last release and over 100 commits since then, but I want to move some documentation over to the speedwm specific wiki first, as I think the man page is growing very, very big. That is not great, not to mention any documentation in a tarball cannot be updated as the release has already happened. Not ideal, is it?
Also, a speedwm wiki was pretty much necessary at this point. While you can pull request to the speediegq repository on Codeberg, there's a lot of delay and work involved in that, when all you want to do is say, fix a simple typo or something like that. However not only can you edit existing articles written by me, but you can also create new articles if you feel like something is missing. While this is speedwm documentation, a lot of it also applies to dwm, so if you're into hacking on dwm you might want to check out the wiki!
As for the more general wiki, it's far, FAR from complete so far. In fact there is only one article. But I plan on slowly expanding it as time goes on. With that said, you may be wondering what wiki solution I went with. Did I write my own? What wiki solutions are there that aren't absolutely massive and terrible?
-
Of course, w2wiki. w2wiki is written purely in PHP and CSS, and articles are written in Markdown as stated previously. I have to say I really like w2wiki and I have no plans to use something different. I will say, I don't really like the default CSS, however we're not soydevs here, so I changed that to fit the theme and minimalism of the regular speedie.gq website.
+
Of course, w2wiki. w2wiki is written purely in PHP and CSS, and articles are written in Markdown as stated previously. I have to say I really like w2wiki and I have no plans to use something different. I will say, I don't really like the default CSS, however we're not soydevs here, so I changed that to fit the theme and minimalism of the regular speedie.site website.
Anyways, that's just a small post for today, I have two more suckless related posts coming up relatively soon, but after that I hope to write some more classic blog posts. I have been relatively busy with real life of course, so I haven't had time to write anything proper, although I have a relatively good amount of ideas.
-
That's it for today, thank you for reading, check out the general wiki, as well as the speedwm wiki and have a nice day!
+
That's it for today, thank you for reading, check out the general wiki, as well as the speedwm wiki and have a nice day!