Remove a bunch of articles because I don't really like how they're
written. I will be rewriting them at some point when I get the time.
This commit is contained in:
parent
bb8cafc340
commit
0a7ea8a3b3
|
|
@ -1,91 +0,0 @@
|
|||
Today I want to talk a bit about configuration files as well as their issues,
|
||||
and believe me, there are many issue with configuration files.
|
||||
|
||||
## The suckless approach
|
||||
|
||||
The suckless approach for those unaware is to never use config files. Instead,
|
||||
with suckless software you modify a `config.h` header which contains variables
|
||||
intentionally exposed to the user. Then you simply rebuild the software with
|
||||
the options chosen built into the binary.
|
||||
|
||||
Many issues with regular configuration files are not a problem here. We'll get
|
||||
into those problems in a bit, but doing it this way introduces many other
|
||||
potential problems. The most notable issue is having to recompile the program
|
||||
every time you want to change one small thing, such as the colorscheme or a
|
||||
keybind.
|
||||
|
||||
In any case, most of the problems with regular configuration files do not apply
|
||||
to suckless software, simply because of how it is designed.
|
||||
|
||||
## Problems with configuration files
|
||||
|
||||
- Options get deprecated
|
||||
|
||||
This is what compelled me to write this blog post. Although not a problem with
|
||||
configuration files directly, developers naturally often feel the need to
|
||||
deprecate options in their configuration files, but this is incredibly poorly
|
||||
handled most of the time leaving the user suffering.
|
||||
|
||||
Let's take Hyprland for instance. Hyprland wants to be this compositor which
|
||||
always implements the latest and greatest, and as a result they do not at all
|
||||
care if they drop support for options the user has in his or her
|
||||
configuration file. After updating Hyprland I received a warning because I had
|
||||
used a now deprecated option in my configuration file. This option is simply a
|
||||
toggle for blur.
|
||||
|
||||
A sensible developer would deprecate the feature and in case a replacement exists,
|
||||
simply rewrite the user's config file on runtime to use the new replacement.
|
||||
As a result, the user can use the old configuration file with the new program and
|
||||
everyone is happy. If a replacement option does not exist, you should probably
|
||||
simply ignore the line. In the rare case that a option MUST be removed, the major
|
||||
version should be bumped and users should be warned in advance.
|
||||
|
||||
A general rule is, if the configuration works right now, it should work in 10
|
||||
or 20 years with almost no maintainence necessary. This is one area where
|
||||
suckless software rocks. For the record, I can compile dwm 0.1 from July 2006
|
||||
on my computer and it will work EXACTLY like it did in 2006. No maintainence
|
||||
necessary.
|
||||
|
||||
- Not very extensible
|
||||
|
||||
Configuration files are not very extensible most of the time. Some config files
|
||||
are more hackable than others, but usually they simply modify variables in the
|
||||
program itself and nothing more, so writing new code or new functions is usually
|
||||
not at all trivial and config files usually are not designed around being hackable.
|
||||
|
||||
Some config files kind of support functions or similar, notably Waybar.
|
||||
|
||||
- Syntax
|
||||
|
||||
The syntax can vary. Some programs use Windows style `.ini` files which look something
|
||||
like this:
|
||||
|
||||
```
|
||||
[myProgram]
|
||||
Variable = 123
|
||||
```
|
||||
|
||||
While these aren't extensible at all, they make up for that in simplicity,
|
||||
which is very often desirable, especially if you don't need the program to be
|
||||
that extensible through a config file. But of course, this format isn't good
|
||||
for every single use case, so JSON style formats such as YAML are very popular.
|
||||
|
||||
That's where the syntax can be a problem. The syntax is usually very
|
||||
unpredictable and unless a "default" configuration is bundled with the program
|
||||
the user is likely to be very lost. To make matters even worse, the default
|
||||
configuration is usually hidden away so the user ends up having to use the
|
||||
internet to figure it out.
|
||||
|
||||
## Conclusion
|
||||
|
||||
Alright, so what do I think about configuration files? Contrary to what you
|
||||
might think, I am not against config files, at least not most of the time. I
|
||||
even use configuration files in a lot of my software.
|
||||
|
||||
However it's worth noting that config files are not without problems, and
|
||||
while a good developer can work around some of these issues, for example by
|
||||
simply not deprecating features like a madman, at the end of the day a config
|
||||
file is written after the program was initially compiled, and that's a big
|
||||
reason for all of its drawbacks.
|
||||
|
||||
That's it for today, have a good day!
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-08-18
|
||||
|
|
@ -1,51 +0,0 @@
|
|||
It is no secret that I can't stand the absolute state of the modern
|
||||
GNU/Linux desktop. Even putting all of that aside though, there are
|
||||
some other issues I want to talk about. I've talked a lot about
|
||||
package management, audio and more, but the biggest problem is how
|
||||
we (the community) approach the normies. Many of these easy
|
||||
distributions come with a graphical package manager. Fair enough if
|
||||
you're new, right? These package managers often have a "featured"
|
||||
section, I know PopOS has one, and that's where the problem lies.
|
||||
PopOS and likely other distributions are actively recommending
|
||||
nonfree software through the "featured" section.
|
||||
|
||||
That is a huge problem because by recommending nonfree software you are telling
|
||||
normies that they SHOULD continue to use nonfree software, and they should not
|
||||
adapt to our ideas and start using free software alternatives. I get that some
|
||||
nonfree software just does not have good free software replacements, but you
|
||||
as the distro maintainer need to be able to put your foot down, and stop
|
||||
recommending Google Chrome or Microsoft Office or LastPass or other nonfree
|
||||
software when there are clear free software alternatives that usually
|
||||
accomplish the same task, and usually does a better job at it too.
|
||||
|
||||
The solution: Nonfree software should not be recommended by the GNU/Linux
|
||||
community. There is no harm in keeping it available, if not intentionally
|
||||
making it a little bit harder to install, because some users just are not able
|
||||
to move away from it for many different reasons. But we should not make it as
|
||||
easy to install nonfree software as it is to install free software. When you
|
||||
install GNU/Linux, you should be encouraged to move away from nonfree software
|
||||
for the most part in favor of free software that respects the user's
|
||||
freedom and privacy. By recommending nonfree software, you are encouraging the
|
||||
user not to care about privacy, and use GNU/Linux
|
||||
because "it works better than Windows" rather than "I care about my privacy and security".
|
||||
|
||||
If you have read ploum.net's excellent article titled
|
||||
[We need more of Richard Stallman, not less](https://ploum.net/2023-06-19-more-rms.html)
|
||||
you're no doubt aware of this already, but the free software foundation has
|
||||
slowly been replaced by the more corporate friendly open source movement which
|
||||
doesn't care about your freedom, only the collaboration aspect of free software.
|
||||
These same people want Stallman and the Free Software Foundation gone, because
|
||||
they actively dislike free software. The thing is we NEED Stallman's extremist
|
||||
views on software. We need to go all out on free software, not just use SOME
|
||||
free software but mostly nonfree software, because if we don't we still have
|
||||
terribly privacy and security. And when a "faster" or "better" version of the
|
||||
free software comes out, why shouldn't we just use that instead?
|
||||
|
||||
The best way to spread free software and avoid spreading nonfree software is to promote
|
||||
free software, and shame nonfree software for not respecting users' freedom and
|
||||
privacy. Normies usually get into free software by using GNU/Linux, so there's an
|
||||
excellent opportunity to promote free software rather than nonfree software.
|
||||
|
||||
Let me know what you think. Do you think it's justified to promote nonfree software?
|
||||
Do you think we should be even more strict, maybe not even allow nonfree
|
||||
software in the main repositories? I'm interested to hear about it. Have a good day.
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-06-22
|
||||
|
|
@ -1,91 +0,0 @@
|
|||
Now, I would never go as far as to say Windows is better than GNU/Linux, but it
|
||||
still has the edge sometimes. Today I want to talk about one such case.
|
||||
|
||||
## The problem
|
||||
|
||||
File pickers on GNU/Linux are the absolute worst. We've been able to write a new
|
||||
display protocol, Wayland but we somehow still can't have a file picker that doesn't
|
||||
lack basic features or even works for that matter.
|
||||
|
||||
This is not a minimalist nitpick. In fact what I'm really complaining about
|
||||
is the *lack* of basic features that people need. Okay, so let's say you
|
||||
have a Chromium tab open and a website you're on requires you to upload
|
||||
an image. Fine right? Now what if you don't know what the filename is?
|
||||
|
||||
On Windows, what you would probably do is click on a bunch of them,
|
||||
look at the image and see if it's the correct image in the preview pane.
|
||||
On GNU/Linux you cannot do this, because our file pickers are so crap and don't allow
|
||||
you to preview images. In fact, the only file picker I know of that supports
|
||||
this feature is Gimp, and that has a custom file picker that only Gimp uses.
|
||||
And it's clear why it has a custom file picker, it's because all the
|
||||
other file pickers are useless.
|
||||
|
||||
## GTK file picker
|
||||
|
||||
|
||||
|
||||
This is what the GTK file picker looks like. GNOME and GTK has always had a
|
||||
minimalist design philosophy, not in terms of code or anything, but they've
|
||||
had simple UIs, just like Apple software. It's the Apple of the GNU/Linux
|
||||
space. There are multiple issues with this file picker, here are just a few:
|
||||
|
||||
- The aforementioned problem: Images don't have thumbnails, so you have
|
||||
no idea what you're uploading unless you know the filename.
|
||||
- You cannot enter a path to a file. You can only see the parent directories.
|
||||
- The pinned folders on the left are useless, and cannot be unpinned if
|
||||
those folders do not exist.
|
||||
- You can't pin symlinks. This is massive problem for me at least, because
|
||||
I have ~/Screenshots, ~/Music, ~/Recordings and ~/Downloads symlinked
|
||||
to another drive.
|
||||
|
||||
Oh wait, you *can* enter a path to a file. You have to press `/` for it
|
||||
to display. But when you press `/` the path to the current directory
|
||||
will be removed. That is some awesome design right there.
|
||||
|
||||
## QT file picker
|
||||
|
||||
|
||||
|
||||
Now, on the KDE side of things we have the QT picker. It looks a lot better.
|
||||
For one, it actually has a field for entering a path, which also shows the
|
||||
current directory. It has buttons for navigation and a "Filter" option.
|
||||
It also allows you to resize each pane, which is a basic feature that
|
||||
the GTK picker is lacking for some reason. A massive step in the right direction.
|
||||
|
||||
Only one small problem. Programs that use GTK, which are a lot of programs
|
||||
these days, including your web browser where you NEED a file picker that
|
||||
doesn't suck will still use the GTK file picker, which we've established
|
||||
sucks and is basically useless as a file picker.
|
||||
|
||||
This means you pretty much CAN'T escape the GTK file picker, because it's
|
||||
so tightly integrated with the whole GTK toolkit.
|
||||
|
||||
## Windows was right
|
||||
|
||||
|
||||
|
||||
As you're surely aware of at this point, I use free software and I don't
|
||||
support nonfree software. However regardless,
|
||||
Windows does file pickers right. Everything positive I said about the QT
|
||||
file picker Windows has done for decades. It may be absolutely
|
||||
proprietary, but it is functional, something the GTK
|
||||
picker cannot say about itself.
|
||||
|
||||
You may notice some similarities between the Windows file picker and the
|
||||
QT file picker. Regardless, they're both functional and get the job done.
|
||||
You get a list of your files with image previews, both in the form of icons
|
||||
if you increase the icon size and in the form of the preview pane you can
|
||||
open up. The Windows file picker is actually even better though, because
|
||||
it actually displays EVERYTHING, rather than a few folders that you manually
|
||||
go out of your way to pin. It also works with shortcuts (basically symlinks)
|
||||
and handles drives too.
|
||||
|
||||
## Conclusion
|
||||
|
||||
GTK and GNOME is about as useful as a painting. Cool to look at, but when
|
||||
you actually want to get stuff done, you're SOL. GNOME and GTK should
|
||||
take notes, quit designing a painting and instead think about what people
|
||||
ACTUALLY need out of their file pickers.
|
||||
|
||||
In the meantime, If you have a solution to this problem, please send me
|
||||
an email. In any case, that's it for me. Have a good day!
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-07-03
|
||||
|
|
@ -1,37 +0,0 @@
|
|||
Alright so I have a brief announcement or something today and that
|
||||
is, I have officially stopped using Gentoo. Yes that's right, the Gentoo elitist
|
||||
is now an Arch cuck. But why, why would you commit such a crime you might say?
|
||||
Well, Gentoo has actually been giving me more and more problems for months now,
|
||||
and it doesn't seem to get any better.
|
||||
|
||||
I've had so many dumb issues with Gentoo recently, such as Xft fonts being
|
||||
broken, packages failing to emerge, `--depclean` removing my entire system,
|
||||
and the final straw, gnome-keyring issues that just do not occur on
|
||||
other GNU/Linux distributions. In case you're not aware, I have been using
|
||||
Arch on my laptop for months now, and while Arch has some annoying issues
|
||||
such as GPG keys constantly breaking pacman when updating, I find that it
|
||||
works much better now.
|
||||
|
||||
To make matters worse for Gentoo, syncing the repositories takes a very
|
||||
long time, and it's valuable time that I do not want to spend just because a
|
||||
program is slow and written in Python. Moving over to Arch was not difficult
|
||||
though. I said 'fuck it' yesterday at around 04:00 in the morning, and
|
||||
started installing Arch over Gentoo. Thankfully, as you guys know I have
|
||||
an arch repository containing nearly the same programs as my Gentoo
|
||||
repository (overlay), and as such I was able to install my config files
|
||||
and all my programs using one command. It's super nice, otherwise I
|
||||
would've probably spent much more time on this.
|
||||
|
||||
Anyways, as for my overlay, I will probably update it every once in a
|
||||
while using maybe a docker container, but I'm going to be focusing on
|
||||
the arch repository because it's what I'm using. For those of you
|
||||
that actually use Arch, this might be good news for you because it means
|
||||
you will always be able to install my software using pacman. I know
|
||||
that some of you will probably be disappointed about this, because I'm
|
||||
kind of known as a Gentoo user at this point, but I just can't take
|
||||
Portage's stupidity anymore. If you need to however, feel free to remove
|
||||
my feed!
|
||||
|
||||
I also took the time to move /home to a separate partition,
|
||||
which is really nice if you want to reinstall quickly. Whatever, that's
|
||||
all I needed to say with this blog post. Have a good day!
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-03-26
|
||||
|
|
@ -1,104 +0,0 @@
|
|||
I talk a lot about freedom, privacy and free software on this blog, but today
|
||||
I want to talk about hosting your own services. But why should you host your
|
||||
own services? Isn't that really scary and difficult? Doesn't it require very
|
||||
powerful hardware? No, not really and I'm going to talk about some of
|
||||
the benefits here.
|
||||
|
||||
Alright so let's talk a bit about why you should host your own stuff and what
|
||||
you can host. There are many different services you can host. I'm hosting my
|
||||
website, some files, a Git server, wiki, email server and might host more in
|
||||
the future. But there are many cool things you can host, such as a Matrix
|
||||
homeserver, IRC network, SearX instance, PeerTube, NextCloud, it goes on
|
||||
and on. I won't be talking much about the specific services you can host today.
|
||||
But why should you host all of this stuff? Why not just use Gmail, or a
|
||||
public SearX instance, or GitHub, or any of these public services?
|
||||
|
||||
It's because as the sysadmin, you are very powerful and have a lot of power
|
||||
over your users and your services, and my site and services are no exception.
|
||||
You have power over everyone that uses your site and services. The ability to
|
||||
delete their accounts, look at what they're doing, all of these different
|
||||
things that you have no control over. When you host your own services though,
|
||||
the only one who is going to be able to see what you upload to your server is
|
||||
you (and your VPS provider if you're hosting using a VPS). Maybe other people
|
||||
can see it if they manage to compromise your server or you let your web server
|
||||
serve content that you don't want public. But in general, you're the only one
|
||||
who is going to be able to see that.
|
||||
|
||||
Let's take a public SearX instance for example. Let's say you visit
|
||||
searx.speedie.site and use it as your primary engine. Now, this search engine
|
||||
does not exist because I host my SearX instance locally but anyways, if you visit
|
||||
my SearX instance and use it to search for things, I have the power to log the
|
||||
search queries you search for, and I have the ability to see all the anime pornography
|
||||
you search for with great shame. Do you really trust me to not look at your
|
||||
search queries? No? So why should you trust any other SearX instance or hell,
|
||||
even Google for that matter. For this reason, you should take matters into your
|
||||
own hands and host your own services that you have control over. That way,
|
||||
you have the power to customize anything and everything about the service you're
|
||||
hosting, shut it down at any time to perform maintainence, set up logging,
|
||||
shred all logs and log absolutely nothing, etc.
|
||||
|
||||
But, doesn't hosting your own services require spending a lot of money? Doesn't
|
||||
it require a very powerful computer? No. If you want to host many, massive big
|
||||
files on a VPS or server that you rent, you may not have that much disk space.
|
||||
But even if that's the case you can host from home on a cheap old Dell Optiplex
|
||||
or maybe even a Raspberry Pi and just connect storage to it. I'm hosting a Git
|
||||
server using Gitea, and all the repositories Gitea handles combined only takes
|
||||
up approximately 870MB. And my public folder where I host downloads to all my
|
||||
software only takes up about 30MB. That really isn't much, and you can host
|
||||
that and much, much more on a cheap VPS. And the spmenu wiki I host takes up
|
||||
31MB. So unless you want to host many, massive files I think making the
|
||||
argument that you don't have space is ridiculous. Any desktop computer
|
||||
from.. say 2008 or later is going to be able to handle hosting your site,
|
||||
and the terrible hard drive it has is going to be able to hold all of
|
||||
your files as well.
|
||||
|
||||
You can get a cheap VPS from Vultr for $3.50, and you can get a domain for
|
||||
usually very cheap as well. I went with Namecheap for my domain name, and they
|
||||
seem quite reliable and not very expensive. If you want to get a VPS from
|
||||
Vultr, feel free to use [my referral link](https://www.vultr.com/?ref=9327892).
|
||||
There are other VPS companies though, and I still recommend hosting from home
|
||||
if you are able to, and your ISP reliably allows you to because it's likely still
|
||||
going to be a bit cheaper, but more importantly means you avoid the ability for
|
||||
your VPS provider to look at the contents of the virtual hard disk, and you are
|
||||
able to use more disk space. You have a lot more freedom that way. Still, a VPS
|
||||
is not a bad choice if you just want to host a few services and your personal
|
||||
site, but it's probably not the best option if you want to host NextCloud or a
|
||||
lot of big files or use it as a media server or anything like that. It also
|
||||
makes a lot more sense if you want to, for instance set up a VPN. Doing that
|
||||
on your own network doesn't make much sense unless you use the VPN away from home.
|
||||
|
||||
I won't get into hosting from home as that isn't something I'm familiar
|
||||
with (although I might try it at some point), and I also won't get into more
|
||||
complex setups or containers, just the basics. While I'm not a particularly big
|
||||
fan of Debian based GNU/Linux distributions, simply because of their old
|
||||
packages and the apt-get package manager, it's a fairly good choice if you want
|
||||
things to just work and serve your content all day every day. Despite not really
|
||||
liking Debian very much, it's what this website is hosted on, along with my
|
||||
other services I have.
|
||||
|
||||
When I'm using a VPS, I usually start by adding a new user and giving him a
|
||||
password. Then I usually install doas because it's smaller and has had fewer
|
||||
vulnerabilities than the more bloated sudo that people use. Then I will copy
|
||||
over my SSH keys to that user's `.ssh` directory. Finally, I **always** disable
|
||||
authentication using passwords for SSH, and more importantly I disable SSH as the
|
||||
root user. I do this because the root user is present on almost every machine, meaning
|
||||
if you want to gain access to someone's server by bruteforcing, a safe bet is to
|
||||
try to gain access using the root account. Then for extra security I will disable
|
||||
the actual root user, so the only way to gain superuser is to use `doas`
|
||||
Now you may have to open ports to be able to host anything on it. If you want to
|
||||
host websites you will have to open TCP port 80 for HTTP and 443 for HTTPS. On
|
||||
Vultr VPSes this is done using the `ufw` command, which is the firewall the VPS
|
||||
comes with. It should be noted though, that if you want to host an email server
|
||||
you will need to open port 25 used for SMTP, and should be done with the `ufw`
|
||||
command as well, but you also need to file a ticket on Vultr's website giving
|
||||
a valid reason for wanting the port to be opened. Usually they will accept your
|
||||
request, though.
|
||||
|
||||
Now that you've opened the ports you need, you can start hosting the services you
|
||||
wish to host. I would probably install Apache and php-fpm for PHP to get my
|
||||
website set up now. A VPS is going to function exactly like any GNU/Linux computer
|
||||
you're used to, although it will not have a graphical environment. Therefore you
|
||||
should expect to get familiar with Vim, it is your best friend. Anyways, you should
|
||||
host your own services, instead of using public services because it's more
|
||||
private, more secure, and you have much more control than with a public service
|
||||
that many people are going to use.
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-06-24
|
||||
|
|
@ -1,77 +0,0 @@
|
|||
Alright, just a short blog post for today. I am NOT an open source enthusiast.
|
||||
Every time someone calls me a "open source" enthusiast, I want to shoot someone.
|
||||
I do not support the open source movement and I do not support open source
|
||||
software, or as a lot of people will say "FOSS".
|
||||
|
||||
## Goal of open source software
|
||||
|
||||
The goal of open source is to provide the source code for ease of collaboration
|
||||
and for vulnerabilities to be discovered. Big companies can then take that project,
|
||||
which is almost always licenced under a [cuck license](https://speedie.site/blog/Swedish+man+rants+about+licenses+again),
|
||||
and release it in the form of nonfree software with additional spyware added on.
|
||||
The most notable example of this is the Google Chrome web browser, where Chromium
|
||||
is the "open source" variant of the software, only without the spyware and with
|
||||
the freedom to modify and distribute copies of the software.
|
||||
|
||||
## Goal of free software
|
||||
|
||||
The goal of free/libre software on the other hand is freedom for all users of the
|
||||
software. These are:
|
||||
|
||||
0. The freedom to run the program
|
||||
1. The freedom to study the program
|
||||
2. The freedom to distribute the program to help others
|
||||
3. The freedom to modify and distribute copies of the program
|
||||
|
||||
While free software is often copyleft, meaning you cannot fork the project
|
||||
and relicense it under a nonfree license, stripping away the freedom from
|
||||
the users of that fork, free software is not always copyleft. Therefore
|
||||
open source software is almost always compatible with free software. If you
|
||||
are using open source software you are most likely using free software.
|
||||
|
||||
## Ethics
|
||||
|
||||
Open source software that meets the free software freedom criteria is just
|
||||
as ethical as free software. The main problem is you're sending the wrong
|
||||
message to people. But the software is still free as in freedom.
|
||||
|
||||
To be clear, I *do* believe nonfree software (software that doesn't meet the
|
||||
four essential freedoms) is unethical. But I do not dislike anyone for using
|
||||
nonfree software. It's kind of difficult to avoid using nonfree software in
|
||||
this day and age. Respect to those who are able to use 100% free software
|
||||
(going as far as using a libre kernel and free BIOS) though.
|
||||
|
||||
You are not unethical for using nonfree software. The unethical practice
|
||||
is actually licensing that software under a nonfree license and releasing
|
||||
the software to people.
|
||||
|
||||
## Same thing?
|
||||
|
||||
A lot of people will say "what's the difference" or "who cares" when I
|
||||
mention I don't care for open source software. The reason it matters
|
||||
is because when you talk to people who may or may not care about freedom,
|
||||
you should be telling them that you care about freedom, not price.
|
||||
|
||||
FOSS stands for "Free and Open Source software" but I cannot stand this term,
|
||||
because it implies that the software is open source *and* free as in price,
|
||||
meaning you don't have to pay any money for it. Most people when they hear
|
||||
this term, both tech enthusiasts and normies think it means you get it for
|
||||
free. This is the problem. The message we should send is that the software
|
||||
is free as in freedom, not that it doesn't cost any money.
|
||||
|
||||
## Conclusion
|
||||
|
||||
I am not for the open source movement. I do not support open source software
|
||||
for the sake of collaboration or for security vulnerabilities to be discovered.
|
||||
I support free software because free software respects users' four essential
|
||||
freedoms. Everything open source provides free software also provides.
|
||||
The main difference is the goal of the movement. I do not care for the
|
||||
open source movement and their motives. I care about the FSF's definition
|
||||
of free software and freedom for all users.
|
||||
|
||||
The reason "open source" is more popular now is because it's more corporate-
|
||||
friendly. Companies do not care about your freedom, but they certainly do
|
||||
care about unpaid work and security audits. Companies are against free
|
||||
software because they are against user freedom.
|
||||
|
||||
That's it for today. Have a good rest of your day!
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-07-13
|
||||
|
|
@ -1,87 +0,0 @@
|
|||
As you guys may know if you have been a speedie.site reader for a while, I was a
|
||||
Gentoo user, and recently I switched to using Arch full time. However, I am yet
|
||||
again switching operating system because I just found out Windows is the best
|
||||
operating system ever made.
|
||||
|
||||
## Linux sucks, but Windows is awesome!
|
||||
|
||||
Now, most of you probably use some open source Linux distribution on your
|
||||
computer. But Linux is open source, and that's bad. That means Russian
|
||||
hackers can steal your porn collection because of course they can see all the
|
||||
source code and backdoor it. When you're using Microsoft Windows on the other
|
||||
hand, the only one who can access your data is Microsoft, who will send that
|
||||
data to the NSA. This also makes sure your data is safe, and that you're
|
||||
following the law like any good citizen. When I'm using Windows I feel safe
|
||||
and no malware has access to my data. The same cannot be said for Linux or
|
||||
any other open source operating system
|
||||
|
||||
These Linux users who never go outside or shower will say that this is malicious,
|
||||
or that it is spyware, or any other nonsense but the fact of the matter is the
|
||||
government already knows everything about you anyway. You should not care about
|
||||
privacy if you have nothing to hide, so of course Linux users have a lot to
|
||||
hide. The government would never do anything bad anyway, they only
|
||||
want the best for you.
|
||||
|
||||
## Tiling window managers suck
|
||||
|
||||
Why would you use a tiling window manager? Only hackers use those. Tiling
|
||||
window managers are also really hard to use, I mean think about all the keybinds
|
||||
you need to remember to get good at using one.
|
||||
|
||||
What about speedwm? I'm just kidding, I've been secretly using GNOME for years,
|
||||
and I was never using speedwm in the first place. Hating Wayland? Actually,
|
||||
I've been using a Wayland session on GNOME for a long time now. As we all
|
||||
know, X11 is old and slow, and it's not written in Rust so that makes it
|
||||
instantly bad. spmenu? It's just rofi with a theme.
|
||||
|
||||
C programming language? Hell no, it's so hard to learn and it's so old.
|
||||
Real programmers use JavaScript for the frontend and Rust for the backend. Recently
|
||||
though, I've started using C# which is superior to both of these in
|
||||
every way. We all love Micorsoft.
|
||||
|
||||
## Vim is only used by furries, neckbeards and weirdos
|
||||
|
||||
Vim is a meme Linux users force onto new users. In reality, Vim is hard to use and
|
||||
it's so slow, I can't even figure out how to exit it. If I can't even exit it,
|
||||
how can I use it to write code? Why wouldn't you just use a mouse anyway?
|
||||
It's not 1983 anymore, we have modern, proper computers for real people now.
|
||||
The only people who still use Vim are neckbeards who want to look cool on
|
||||
the internet but in reality don't have a life.
|
||||
|
||||
Visual Studio Code on the other hand is the greatest code editor ever and
|
||||
it's what I've been using for months now, while people were under the
|
||||
impression that I'm an avid Vim user. It's "open source" so that the
|
||||
Linux neckbeards will use it, but uses a mouse, because it's 2023
|
||||
and if you're not using a mouse for everything except typing, you're
|
||||
lost in the past. It also supports JavaScript plugins and has a lot
|
||||
of Microsoft telemetry, so they know you're doing a good job
|
||||
writing programs for the future.
|
||||
|
||||
## Installing programs
|
||||
|
||||
Linux users claim that using their terrible package managers is better
|
||||
than downloading executables from the internet directly. This is just
|
||||
not true, because the package managers can be hijacked remotely by Russia
|
||||
to spread propaganda to all of the users. This doesn't happen when you
|
||||
download random executables from the internet, because Microsoft Defender
|
||||
is guarding your computer, and has a 100% success rate. As soon as malware
|
||||
tries to attack your computer, Microsoft Defender is there to stop it.
|
||||
|
||||
## Software minimalism
|
||||
|
||||
Software minimalism is all a big joke. Why do you need your computer to
|
||||
use 100MB of system RAM idle? Unused RAM is wasted RAM. Microsoft makes sure
|
||||
to leave no RAM wasted, which makes it much better. Unlike suckless, Microsoft
|
||||
makes feature complete software that normal people can use. In fact,
|
||||
suckless is just a software project created by Microsoft's worst employees
|
||||
created to trick Linux users into thinking Linux is unusable, thus getting them
|
||||
to move over to Windows. Microsoft makes sure people join the beautiful land
|
||||
of Windows, where no one falls for memes, and everyone is secure.
|
||||
|
||||
Conclusion then. After I found out Windows is better than Linux, I have
|
||||
decided to stop working on my meme projects, and join Bill Gates in
|
||||
helping him build the best operating system for normal people. Linux
|
||||
furries and neckbeards, join the land of Microsoft today, stop using the
|
||||
Matrix meme, come back to Discord, assist Microsoft and the NSA in
|
||||
catching criminals, and become a real member of society today.
|
||||
It's only a $100 operating system.
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-04-01
|
||||
|
|
@ -1,60 +0,0 @@
|
|||
**Warning: If you are not willing to listen to me talk about people who are
|
||||
obsessed over identity politics, stop reading this blog post now!**
|
||||
|
||||
Today I'm going to say something I may come to regret in the future. Fuck it.
|
||||
This needs to be said. I may also lose more readers for this, or receive
|
||||
angry emails from people I dislike. That's not something that bothers me.
|
||||
|
||||
I'm sure if you follow my blog you're well aware of the [petition against
|
||||
Richard Stallman](https://rms-open-letter.github.io/) that big technology
|
||||
companies signed. Big names like Mozilla, GNOME Foundation, LineageOS, OBS,
|
||||
Tor, X.org Foundation and even Creative Commons all signed this petition.
|
||||
Even some GNU/Linux channels like The Linux Experiment.
|
||||
This petition calls for the removal of the entire board of the FSF, and
|
||||
that of course includes Richard Stallman. Even the GNU project, which is
|
||||
Stallman's project.
|
||||
|
||||
Whether or not you believe Richard Stallman is a good person is not something
|
||||
I care about in any way. I don't care about that, and I don't care about him
|
||||
as a person to be honest. But I value Richard Stallman's work more than
|
||||
I will ever value this petition or frankly anyone who signed this petition,
|
||||
because despite Stallman's possible ethical flaws, he is responsible for a lot
|
||||
of good free software, including the free software movement itself. This
|
||||
petition wants to shame Stallman over things that don't really matter all that
|
||||
much in the software space. When you develop or use software, the political
|
||||
views of the developer doesn't matter, the end product does. And for the most
|
||||
part, the software he has worked on is pretty good.
|
||||
|
||||
This is just one example of the awful political activism which has slowly but
|
||||
surely taken over many free software projects, such as the Linux kernel and
|
||||
many other projects that people depend on. It's no longer about writing a good
|
||||
program but rather political activism and identity politics, which doesn't at
|
||||
all matter to the end user. The end user, the average normie just wants a
|
||||
program that doesn't suck and gets the job done. While saying politics should
|
||||
stay out of software entirely is a bit far fetched, considering free software
|
||||
(or even open source) is a movement, when you're actually writing a program
|
||||
it doesn't matter. It doesn't matter if a contributor believes in X, Y or Z
|
||||
or is a part of group X, Y or Z. If the code is good, it's good. If it isn't,
|
||||
then it isn't.
|
||||
|
||||
These people who are absolutely obsessed over politics are called SJWs, or "woke".
|
||||
In my experience, they may not admit it themselves, but usually they
|
||||
fall into this category. These people don't care about the software, they only
|
||||
care about making sure everyone involved in the project has (usually) liberal
|
||||
political views. If someone has different views, they will group together to
|
||||
shame that individual for their ideas, calling them a bunch of different names
|
||||
that I'm sure all of you have heard in the past even if the contribution the
|
||||
individual made is excellent and improves the project in a meaningful way. It's
|
||||
kind of difficult to avoid these people nowadays, and I am sure everyone who is
|
||||
reading this blog post has either come across one of these people, or are part
|
||||
of this group of people.
|
||||
|
||||
Either way, if you are one of these people, you are free to contribute to
|
||||
my software repositories. Same for the complete opposite part of the spectrum.
|
||||
I value these contributions equally, because they both result in a better
|
||||
product. The activism should stay out of software, that's the important part.
|
||||
Whatever you do outside of my repositories is not my concern in any way.
|
||||
Do however know that I will say what I want, whether you like it or not.
|
||||
And regardless of Stallman's views on politics or any other individual,
|
||||
I value and support the software and the software development, no matter
|
||||
who contributes to it.
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-07-15
|
||||
|
|
@ -1,29 +0,0 @@
|
|||
I'm going to keep this one short and to the point. As some of you may know,
|
||||
my domain is going to expire. It is going to expire on the 31st of March
|
||||
2023, which is not far from today and that's what I'm going to talk about.
|
||||
For those of you that don't know, my website uses a "free" TLD (top level
|
||||
domain). This seemed like a good option last year, but as I want to
|
||||
continue this stuff, it presents a problem. Freenom is the company that
|
||||
provides the .gq TLD, along with a few more domains such as .tk. Freenom
|
||||
has shown themselves to be problematic, and they have done things like
|
||||
taking away domains from people after the websites have become too
|
||||
popular. Renewing their domains is also difficult and annoying, and even
|
||||
then doesn't work all the time for all people.
|
||||
|
||||
Because of this, I decided to write this blog post, and to make sure my
|
||||
readers have a place to keep up with me if my website does collapse, I've
|
||||
created a Matrix channel which I recommend you join. You can join it
|
||||
[here](https://matrix.speedie.site). You can start with Element, it's all
|
||||
free software unlike the previous Discord server. I don't plan on making
|
||||
this a big thing like Forwarder Factory was, and in fact I don't want that
|
||||
either. This is simply going to be a small place for me to talk to my
|
||||
readers, discuss the website and other things like that.
|
||||
Either way, my domain expires March 31st if I'm unable to renew it. If I
|
||||
manage to renew it, you can continue using the site like normal for an
|
||||
additional year. Otherwise, I'm simply going to purchase a new domain. I do not
|
||||
yet have another domain, which is why I recommend you join the Matrix channel.
|
||||
That's really all I wanted to say, as the writer here I think it is important
|
||||
that you are informed about everything. My website code is all available for
|
||||
free on Codeberg so you can still have that if you want.
|
||||
|
||||
Thanks for reading, have a good day!
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-03-15
|
||||
|
|
@ -1,24 +0,0 @@
|
|||
I will keep this one short so you can actually read through it. Yesterday
|
||||
(13/04/2023) I purchased a domain, because as we all know I do not trust
|
||||
Freenom to keep my site up. This domain is a lot more reliable, however it does
|
||||
mean you will have to swap out '.gq' for '.site'. I have redirected **some** parts
|
||||
of my site. I have redirected the main `speedie.gq` domain, and I have also
|
||||
redirected rss.xml so that RSS readers won't complain. You should still change
|
||||
the URL, however if you exclusively consume my website through RSS you will get
|
||||
the message anyway because of this. Finally I redirected the wiki.
|
||||
|
||||
Switching over is not hard. The page is identical, and although SSL was not
|
||||
functioning earlier today, I have resolved the issue. So to switch over, just
|
||||
replace 'speedie.gq' with 'speedie.site'. This is especially important if you
|
||||
use Arch and my repository. If you do, you must edit `/etc/pacman.conf` and
|
||||
replace the URL. There may be a few sharp edges as of now, as I simply ran a
|
||||
few `sed` commands on the old site without looking through it properly, if there
|
||||
are issues please [email me](mailto:speedie@speedie.site) so it gets fixed.
|
||||
I should also add I moved from Nginx to Apache a few days ago.
|
||||
|
||||
Anyway, that was just a short blog post about something relatively important.
|
||||
I will *probably* keep the speedie.gq domain updated as well, but I cannot
|
||||
guarantee it will work properly. If you have any questions, feel free to
|
||||
email me, or simply join the
|
||||
[Matrix space](https://matrix.to/#/#speedie:matrix.org). Either way, that's
|
||||
it, have a good rest of your day!
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-04-14
|
||||
|
|
@ -1,124 +0,0 @@
|
|||
So, because this blog post marks blog post number 50, and because the first
|
||||
blog post is 1 year old today, I thought to celebrate I'd do a rewrite of
|
||||
my first blog post, which still holds true, actually more so than when I
|
||||
intially wrote it. Granted, the original blog post is terrible, it was
|
||||
fueled out of frustration and nothing more so let's give the topic the
|
||||
chance it deserves.
|
||||
|
||||
As well all know, GNU/Linux is an operating system and it has always been
|
||||
the outcast, it has always been less popular than other operating
|
||||
systems like Windows and macOS. Out of the outcast operating systems like
|
||||
BSD, Haiku and more however, it's pretty popular and it's growing in
|
||||
popularity. While this may seem like a good thing at first, when you
|
||||
actually dig deeper into what that means for GNU/Linux, you'll find many
|
||||
problems and I want to talk about those today.
|
||||
So let's go back into the early days. Linus Torvalds developed the Linux
|
||||
kernel, which was used in combination with the GNU project. This means
|
||||
we now have a completely free software operating system. Great, now we
|
||||
don't have to use spyware nonfree software that doesn't respect your
|
||||
freedom anymore and everything is good for the small userbase.
|
||||
Previously GNU/Linux followed the UNIX philosophy rather closely, which
|
||||
is what made it so great. Of course there were exceptions to this rule,
|
||||
such as X11 (and today Wayland), however most software was minimal,
|
||||
and closely followed the UNIX philosophy like it was a religion,
|
||||
as that was expected out of software.
|
||||
|
||||
As GNU/Linux got more mainstream and normies got their hands on it,
|
||||
this freedom, this minimalism, all this stuff that made GNU/Linux so
|
||||
great started to disappear. When normies found this free operating system,
|
||||
naturally being normies they didn't want to actually learn anything about
|
||||
minimalism and free software, and certainly didn't want to enjoy any of
|
||||
the perks of it. Instead of that, they initially whined and complained
|
||||
about how it was different from what they're used to. And we, members
|
||||
of the GNU/Linux community in response did everything in our power to
|
||||
make the "Year of the GNU/Linux desktop" happen. Except..
|
||||
|
||||
We didn't. In response to normies complaining, we as a community at large
|
||||
started developing garbage, bloated software that throws everything that makes
|
||||
GNU/Linux and UNIX in general so great in the trash. We're no longer
|
||||
using text streams, we're no longer writing quality software with
|
||||
quality code, instead we're focusing on developing libraries on top of
|
||||
libraries that just add bloat to a project and create huge basically
|
||||
packages of software in an effort to please normies who refuse to
|
||||
appreciate the beauty of UNIX-like operating systems and just wanted to
|
||||
stick to what they're familiar with.
|
||||
|
||||
Here's the thing, If you're this kind of person who doesn't want
|
||||
to learn GNU/Linux, you don't want to learn about UNIX-like
|
||||
operating systems and you don't want to spend any time out of your day
|
||||
learning this stuff then why even bother using a new operating system
|
||||
in the first place? At that point, you might as well stick with Windows
|
||||
or macOS. But alright, fine. We can still have *our* section of the
|
||||
GNU/Linux community where traditional UNIX/Minimalist views are
|
||||
still appreciated, right? Well, no because eventually programmers
|
||||
start writing software which of course depends on all this normie
|
||||
software which is absolutely awful and now it becomes almost
|
||||
impossible to have a functioning system on GNU/Linux without
|
||||
this garbage software.
|
||||
|
||||
I haven't given any examples yet, but in my first version of this
|
||||
blog post I referred to Snaps, AppImages and Flatpaks, and while those
|
||||
do still meet the criteria here (although not in the present),
|
||||
I want to give some more examples which might make more sense.
|
||||
First, systemd. systemd is a collection of tools for GNU/Linux,
|
||||
and although many people hate systemd because it is "an init system",
|
||||
it is really a suite of tools. Therefore calling it bloated is not
|
||||
justified. However what is justified is valid criticism towards it.
|
||||
systemd provides a tool named "logind". So many programs depend
|
||||
on this, it is pretty much impossible to have a modern GNU/Linux
|
||||
system without this program installed on your computer. Now,
|
||||
that should be taken with a grain of salt because there
|
||||
are many different implementations of this tool, and those of
|
||||
you that use Gentoo may be familiar with one implementation
|
||||
called elogind. Still, I think this is an excellent example of
|
||||
dependencies that are used so much you cannot escape them.
|
||||
|
||||
But there are so many programs like these that we can't really
|
||||
escape, and the cause of these programs existing is usually
|
||||
the same. Normies want "easy" software, so in response we write
|
||||
terrible software which a normie will think is easy because
|
||||
Windows is terrible. However the worst of it came around the
|
||||
time Linus Tech Tips and all these other well known technology
|
||||
"entertainment" channels started covering GNU/Linux and giving
|
||||
it attention. When that happened and Windows/Mac users gave
|
||||
this OS a proper chance, developers around here scrambled to
|
||||
write as much normieware as possible to please these new users
|
||||
in the hopes of converting them into GNU/Linux users. Of course
|
||||
this failed, and just resulted in more terrible software.
|
||||
|
||||
I call this the "gaming wave", because suddenly all these gamers
|
||||
(often with NVIDIA graphics cards) came over here, because
|
||||
that's what Linus Tech Tips' fanbase is and wanted to play
|
||||
games. Of course, this failed because despite the effort from
|
||||
the people who play games around here, most GNU/Linux users
|
||||
don't really play games. In fact I barely play games myself
|
||||
anymore. I have nothing against people who play games, but
|
||||
the people who play games on GNU/Linux certainly have some
|
||||
blame to take here.
|
||||
|
||||
Lastly, before I end off this blog post I want to mention
|
||||
a few things regarding Wayland. In short, I'm definitely
|
||||
against it and that's for a few reasons. Wayland brings
|
||||
a lot of good things to the table, such as a cleaner
|
||||
codebase, less screen tearing, perhaps HDR support
|
||||
in the future, and so on and all that is fine by me.
|
||||
No complains there. Where the problem starts to show
|
||||
however is from a developer perspective. Yes, the
|
||||
Wayland display protocol *is* more minimal than X11
|
||||
(that's not really an achievement) but a lot of that is
|
||||
because the Wayland mess has been moved over to the
|
||||
compositor forcing any developers to write thousands of
|
||||
lines of just absolute junk. This is absolutely terrible,
|
||||
and until the developers of Wayland change direction
|
||||
(highly doubt they will), I'm sticking with X11 until
|
||||
it's no longer feasible to do so.
|
||||
|
||||
Either way, that's what I wanted to say, stop using
|
||||
all of this stupid software whenever possible, and
|
||||
become a based GNU/Linux minimalist. I plan on getting
|
||||
a page up on replacements for stupid software which
|
||||
will kind of act as a guide on how to get into GNU/Linux
|
||||
minimalism for those of you that fell for this stupid
|
||||
software. If you have any questions or thoughts,
|
||||
feel free to send me an email.. and have
|
||||
a good rest of your day.
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-03-09
|
||||
|
|
@ -1 +0,0 @@
|
|||
Normies are destroying GNU/Linux
|
||||
|
|
@ -1,71 +0,0 @@
|
|||
It is no secret that I strongly believe in copyleft licenses like the GNU
|
||||
General Public License (often shortened to GNU GPL or GPL) and the Mozilla
|
||||
Public License (MPL). Copyleft licenses as the name implies are the opposite
|
||||
of copyright licenses. With copyleft licenses, the user has the freedom to
|
||||
modify, study and distribute the software and source code. But unfortunately
|
||||
in recent years copyleft licenses have fallen out of favor thanks to tech
|
||||
companies like Microsoft heavily pushing too permissive licenses to developers.
|
||||
These licenses (which I will call 'cuck licenses' from now on) rob developers
|
||||
of their work. Now, it should probably be noted that I am not a lawyer, nor am
|
||||
I more experienced in any legal system that most people. I'm just here to
|
||||
talk about the best software license today.
|
||||
|
||||
With cuck licenses, the developer writes the code and puts it out on the
|
||||
internet like usual. The difference is there is nothing that prevents anyone
|
||||
from forking it and changing the license. You might ask why this matters.
|
||||
It matters because big tech companies like Microsoft, Google, Apple, Nvidia,
|
||||
Meta, and many more will take these free software projects, change the license
|
||||
to a nonfree license and no longer distribute the source code for the software.
|
||||
Most of these cuck licenses **only** require that the license notice is kept in
|
||||
every piece of code. However you're only distributing a binary though, the license
|
||||
isn't noticeable anyway.
|
||||
|
||||
I'm sure you can tell by now, but tech companies LOVE cuck licensers, because cuck
|
||||
licensers do the work for them and for free. The companies then just steal that
|
||||
source code and make their own proprietary variant. No attribution, no money,
|
||||
nothing. Some developer writes the code for free and a big tech company will steal
|
||||
it and make a nonfree spyware variant of it. When tech companies write software,
|
||||
they will usually license their own software too under the BSD licenses or more
|
||||
commonly, the MIT license. The MIT license is probably one of the worst
|
||||
licenses out there in terms of stripping the developer of his/her freedom. The
|
||||
user still has the freedom to use, study and modify the software. That is,
|
||||
until a tech company forks the project and changes the license to a nonfree one.
|
||||
|
||||
An example of a bad case of cuck licensing is MINIX, a portable UNIX like
|
||||
operating system. Because this project is cuck licensed, Intel decided to fork
|
||||
the project, apply some spyware modifications to it and relicense it under a
|
||||
proprietary license so no one knows what the code really does. Now all Intel users
|
||||
have this backdoor in their computer in what's called the Intel Management
|
||||
Engine (ME). Or take Google Chrome. Google forked the Webkit engine and made their
|
||||
own web engine called Blink. The Chromium browser which implements this engine
|
||||
is free software, but Google Chrome (which is very similar) is a nonfree program
|
||||
which does god knows what.
|
||||
|
||||
But you, the developer can fight back against this by licensing your software under
|
||||
a copyleft license. Copyleft licenses *usually* require that the forked software is
|
||||
licensed under the same license. So if you license your software under the GNU
|
||||
General Public License version 3, all copies of the software including forks are
|
||||
going to be licensed under that same license. This is great for developers
|
||||
because their code is always used for free software and not nonfree software.
|
||||
It's also great for users, as it means there will be less nonfree software to
|
||||
use and more free software to use instead.
|
||||
|
||||
I should note that I switched all software I've written from scratch to the
|
||||
GNU General Public License version 3 about a year ago or so from the MIT license
|
||||
and it gives me more freedom, and it also means everyone who uses my software or
|
||||
forks of my software is guaranteed freedom. It's a win for everybody, and it
|
||||
means together we're working towards a more free computing experience for everyone.
|
||||
It has its flaws though, which is why some may consider the LGPL or Lesser General
|
||||
Public License. This license unlike the regular GPL allows embedding the software
|
||||
in proprietary programs. This may actually be preferable in some cases, but in
|
||||
general you should stick to the regular GPL. I know there are more licenses than
|
||||
the GPL and MPL, but I'm not going to get into license specifics too much here.
|
||||
I'm mainly talking about the GPL because that's what I
|
||||
license all my software under.
|
||||
|
||||
Conclusion then. Cuck licensers write the software for big tech companies for free.
|
||||
They get nothing in return and users get a piece of crap proprietary program when
|
||||
the big company forks the originally free software program. With copyleft licenses
|
||||
on the other hand, the user is guaranteed the freedom to modify, study and distribute
|
||||
the source code or program. Switch to the GNU GPL today or any of the other GPL
|
||||
compatible copyleft licenses and truly become a free software computer programmer.
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-05-23
|
||||
|
|
@ -1,31 +0,0 @@
|
|||
Now that most of my issues regarding this site are resolved, I want to start
|
||||
writing about something. I have a lot of topics I want to talk about, however
|
||||
for many of these topics there's just not much content to them, so I apologize
|
||||
for the length of some of these.
|
||||
|
||||
Anyways what better topic to start with than this one. My blog isn't perfect,
|
||||
I post a lot of garbage here quite often, but what pisses me off is when people
|
||||
will write blog posts, have an RSS feed and then ruin it with one thing.
|
||||
They will put about 1/10 of the blog post in the `description` tag, and then
|
||||
they will have the blog post in full on their website.
|
||||
|
||||
This is extremely annoying, because it means I have to open up my bloated web
|
||||
browser just to view your blog post which could normally be read using my RSS
|
||||
reader, which is designed for reading blog posts. What if I want to read your
|
||||
blog post on the command line? Or what if I want to read your blog post when
|
||||
I don't have internet?
|
||||
|
||||
Good RSS readers like Newsboat and sfeed store the full feed locally, meaning
|
||||
you can actually read the articles even when you don't have any internet
|
||||
connection. But when you force me to go to your website, I can't just save it
|
||||
when I do have internet and read the blog post whenever I want to read it.
|
||||
Now, I know why you would do this. If you have a site, chances are you want
|
||||
people to visit it. RSS is convenient, very convenient and I'm going to admit I
|
||||
don't actually visit the sites for blogs I follow very often, usually I read the
|
||||
feeds every day and then very occasionally visit the websites. But I still think
|
||||
this is annoying.
|
||||
|
||||
So, if you're going to have a blog and you plan on using RSS, please provide the
|
||||
full blog post in the description tag. I know this can cause issues with
|
||||
paragraphs, but you can steal my feed as a base if you want. Thanks for
|
||||
reading, and have a good day.
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-04-19
|
||||
|
|
@ -1,53 +0,0 @@
|
|||
Wow, look at that. Even more junk to fill my catalog and make it look like I've
|
||||
done more writing than I actually have. Oh well. I'll get straight to the point.
|
||||
At approximately 02:32 I quickly made the decision to move from cgit to Gitea
|
||||
for hosting my Git repositories and projects. For this reason, links to the old
|
||||
Git repositories need to be changed. This mainly applies to those of you that are
|
||||
using speedie-aur, or speedie-overlay. I'm assuming that's quite few of you, but
|
||||
just in case I'm putting this out there.
|
||||
|
||||
If you're using speedie-aur, you'll need to edit `/etc/pacman.conf` and change
|
||||
the `Server` to
|
||||
`Server = https://git.speedie.site/speedie/speedie-aur/raw/branch/master/$arch`.
|
||||
If you're using speedie-overlay you'll want to remove the overlay and add it again.
|
||||
See [the repository](https://git.speedie.site/speedie/speedie-overlay) for more
|
||||
information. The Arch wiki article has been updated to reflect these changes as
|
||||
well, and so has the overlay.xml.
|
||||
|
||||
I have also moved over a lot of GitHub repositories to my Gitea instance, such
|
||||
as my Gentoo kernel for my ThinkPad and desktop, multiple OpenCore configurations,
|
||||
and more, but all Codeberg and GitHub repositories are still accessible. It
|
||||
should be noted though, that I plan on moving all website development to the
|
||||
Gitea instance rather than Codeberg.
|
||||
|
||||
What you may be screaming right now is WHY? I'll tell you why. Cgit is an
|
||||
excellent Git viewer, but that's all it is. A git viewer. It doesn't handle your
|
||||
repositories, no issue tracking, no pull requests, no users, nothing. This is fine
|
||||
when you're the only one working on a project, as you're going to do most work
|
||||
locally on your computer anyway, and then push using Git from the command line.
|
||||
The problem is when you want to have any kind of collaboration, which is something
|
||||
I realized today (and yesterday). As some of my projects are becoming increasingly
|
||||
complex, I need a way for people to submit bug reports and fix issues. Emailing isn't
|
||||
convenient for the user, and it isn't convenient for me either. Now that I'm using
|
||||
Gitea, any user may create an account and simply create an issue or pull request.
|
||||
There's not any more to it, just simple. If you're familiar with GitHub or even one
|
||||
of the public Gitea instances like Codeberg, this is likely nothing new to you.
|
||||
|
||||
Now, while I'm writing this blog post I also want to talk about some future changes.
|
||||
I want to slowly move from w2wiki to simply a static website that people can edit
|
||||
through issues and pull requests. In my opinion this is a lot better, not
|
||||
only for security but convenience and flexibility. W2wiki is pretty good, but
|
||||
it is definitely not designed with security in mind, and it isn't hard for anyone
|
||||
to simply remove the entire thing with minimal effort, as we saw with the old
|
||||
speedie.site wiki a while ago.
|
||||
|
||||
While it is a static site for the most part, I may still be using PHP if necessary,
|
||||
especially for maintainence. No JavaScript however, although it should be noted
|
||||
that the Gitea instance does use JavaScript. There is just no way around it as
|
||||
far as I know, so it will have to do. All the JavaScript is free as in freedom,
|
||||
which is the important part. I have no plans to put JavaScript anywhere else on
|
||||
my site though, as long as it's feasible.
|
||||
Anyways that's just a small site update. Have been busy with my spmenu Wayland
|
||||
port and other things like that, but now that it's complete I plan on posting
|
||||
more blog posts, as I have a lot of things I want to cover eventually. That's
|
||||
it for me, have a good day!
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-06-03
|
||||
|
|
@ -1,37 +0,0 @@
|
|||
I often hear people following my blog or just know me for one reason or
|
||||
another, and usually it goes something like this:
|
||||
|
||||
> Hello speedie I enjoy reading your blog.
|
||||
|
||||
Thanks!
|
||||
|
||||
> I’m using X nonfree software or Y desktop environment, sorry about that.
|
||||
|
||||
This is the problem. I see far too many people apologize for their choices
|
||||
in technology, but I want to make one thing clear. I am not here to judge your
|
||||
technology choices. If you want to read my blog on Windows and/or Mac, use
|
||||
nonfree programs, hate my software or ideas, or do something else I’m not
|
||||
*personally* a fan of then you are 100% free to do so. You don’t need to
|
||||
justify your use of software or hardware, that is a personal decision you are
|
||||
making. I am not going to make that for you, and while I may not agree with
|
||||
your decision, it is not mine to make.
|
||||
|
||||
I may **suggest** replacements for the software you’re using if I believe it’
|
||||
s something you would benefit from (such as learning Vim or getting into
|
||||
tiling window managers), but I’m never going to force you to use/do something,
|
||||
or shame you for using the nonfree software or software I simply don’t
|
||||
like. I am also never going to force you to believe the same thing as me, that’s
|
||||
idiotic, and the definition of an echo chamber, something I’m very against. I don’t
|
||||
want 15 speedie clones, you should have your own ideas, and I should have my own
|
||||
ideas. If we agree then we do, if we don’t, then we don’t. I make decisions
|
||||
you may find stupid, you make decisions I may find stupid, and if we don’t debate
|
||||
each other’s ideas, we lose the ability to think for ourselves.
|
||||
|
||||
That’s not to say it’s harmful to criticize the choices others make, but you need
|
||||
to be willing to see both sides of the coin, and like it or not you need to accept
|
||||
the choice the other person is making, whether you approve of it or not. That’s
|
||||
just a short blog post for today, as I see this far too often, and I think it’s
|
||||
important to say this. I’m probably going to talk about Wayland development,
|
||||
Wayland libraries, Wayland protocols and Wayland implementations next time now that
|
||||
I’ve truly given Wayland development a fighting chance to win me over.
|
||||
That’s it for me, have a good day!
|
||||
|
|
@ -1 +0,0 @@
|
|||
2023-06-08
|
||||
Reference in a new issue