You might need to reboot after running a nixos-rebuild switch, or move/kill any process running on port 53 for this to work.
Custom DNS mapping
You can use blocky to map a domain of your choice to an IP of your choice - refer to the documentation for more information.
Here, I've used two upstream nameservers for blocky to forward valid DNS requests to (since blocky doesn't do any DNS resolution itself - except for custom mapping, detailed later). One is Cloudflare's DNS (1.1.1.1) and the other is Quad9 (9.9.9.9).
As indicated by lines 6 through 11, you need to add lists containing URLs you want to be filtered from your DNS requests.
The thing is, you'll need to set the IP address of the machine running blocky as a nameserver for all of your workstations - it just won't recieve any requests otherwise, so it won't be doing any adblocking if you don't do this.
Of course, if you've got a router worth keeping around, you should be able to set a network-wide DNS resolver, and you can point this to your blocky-running machine in your router's settings.
However, what if you wanted to have this work everywhere you go, perhaps on a portable laptop? Well, if you're using Tailscale or Headscale you can just can edit the nameservers you use in your VPN's settings and set it to the IP address of the device running blocky. This way, any device on your VPN can utilise blocky and have a functioning DNS-level adblocker no matter where you are.
With the existence of browser extensions doing the same thing adblockers like blocky and Pi-hole can, not everyone is going to need something this sophisticated. I think something like this is better suited to those looking for better coverage in their adblocking, or something that gives more control over DNS requests - for example, to easily setup custom DNS mappings or to restrict access to certain websites.
\ No newline at end of file
+
Why isn't it running?
You might need to reboot after running a nixos-rebuild switch, or move/kill any process running on port 53 for this to work.
Custom DNS mapping
You can use blocky to map a domain of your choice to an IP of your choice - refer to the documentation for more information.
Here, I've used two upstream nameservers for blocky to forward valid DNS requests to (since blocky doesn't do any DNS resolution itself - except for custom mapping, detailed later). One is Cloudflare's DNS (1.1.1.1) and the other is Quad9 (9.9.9.9).
As indicated by lines 6 through 11, you need to add lists containing URLs you want to be filtered from your DNS requests.
The thing is, you'll need to set the IP address of the machine running blocky as a nameserver for all of your workstations - it just won't recieve any requests otherwise, so it won't be doing any adblocking if you don't do this.
Of course, if you've got a router worth keeping around, you should be able to set a network-wide DNS resolver, and you can point this to your blocky-running machine in your router's settings.
However, what if you wanted to have this work everywhere you go, perhaps on a portable laptop? Well, if you're using Tailscale or Headscale you can just can edit the nameservers you use in your VPN's settings and set it to the IP address of the device running blocky. This way, any device on your VPN can utilise blocky and have a functioning DNS-level adblocker no matter where you are.
With the existence of browser extensions doing the same thing adblockers like blocky and Pi-hole can, not everyone is going to need something this sophisticated. I think something like this is better suited to those looking for better coverage in their adblocking, or something that gives more control over DNS requests - for example, to easily setup custom DNS mappings or to restrict access to certain websites.
\ No newline at end of file
diff --git a/public/blog/btrfs-raid-setup/index.html b/public/blog/btrfs-raid-setup/index.html
index b120c50..953aaa4 100644
--- a/public/blog/btrfs-raid-setup/index.html
+++ b/public/blog/btrfs-raid-setup/index.html
@@ -14,4 +14,4 @@
Btrfs also supports RAID10 (or RAID1+0) which is a combination of RAID1 and RAID0 as demonstrated by the following image:
However, as you can see, RAID10 requires n disks where n is an even number greater than or equal to 4. Furthermore, if you tried using devices of varying sizes, space would likely be wasted. So what would you do if you had 3 devices, with, for example, sizes of 1TB, 500GB, and 500GB?
A possible solution here would be to split the 1TB drive into two equal partitions of 500GB, and pass them to btrfs as independant drives.
Theoretically, you could also combine the two 500GB drives into a RAID0 partition and combine them through RAID1 with the 1TB drive (creating a nested RAID01/RAID0+1 array), but this seems to be unsupported by btrfs.
In general, setting up a RAID10 array with btrfs looks like this:
mkdir /mnt/raid10 # make the RAID10 pool
btrfs device add /dev/sdA1 /dev/sdB1 /dev/sdC1 /dev/sdD1 /mnt/raid10 # add the drives
btrfs balance start -dconvert=raid10 -mconvert=raid10 /mnt/raid10 # distribute data to get the array set up
-
\ No newline at end of file
diff --git a/public/blog/hoaxes-overview/index.html b/public/blog/hoaxes-overview/index.html
index ae6f105..684b8a8 100644
--- a/public/blog/hoaxes-overview/index.html
+++ b/public/blog/hoaxes-overview/index.html
@@ -1 +1 @@
-An overview on hoaxes
In recent times, hoaxes have become increasingly prevalent as the internet continues to expand and as more people use social media. Misinformation is on a rise - though this is information which isn't really new, the current state of things is horrible, and things really shouldn't be the way they are.
I aim for this to be a brief blog post detailing the effect of hoaxes on society, focusing on why they're so harmful.
Put simply, a hoax is made-up information, be it a story or something else. Hoaxes are created with the intent of spreading false information - for a immense variety of reasons, from jokes and causing embarrassment to provoking politic or social change1. I won't discuss the causes of hoaxes further in this blog post.
Hoaxes can cause significant damage to their targets if formulated cleverly. For example:
The stock price of Apple Inc. fell significantly in October 2008 after a hoax story was submitted to CNN's user-generated news site iReport.com claiming that company CEO Steve Jobs had suffered a major heart attack. The source of the story was traced back to 4chan.
With the incredible presence of social media in our lives, spreading harmful misinformation like that above can be as simple as making a few posts - they don't even need to be very convincing! What makes matters worse is how gullible the general population is, even those educated in this sort of thing - this shows just how much influence the internet and it's contents have on us.
I would like to clarify that I'm not suggesting that people should avoid using the internet to gather information - while its reliability is incredibly questionable, the accessibility and openness it provides far beats traditional methods of gathering information (books and such). My suggestion is that people should be much more careful with how they interpret information on the internet, and perform their due diligence in their research into whatever they're aiming to learn; people should make sure that what they're reading is accurate before absorbing any information (here's your tl;dr).
That's about it for this blog post, as it was meant to be a brief way of expressing my thoughts on the matter. Thanks for reading!
\ No newline at end of file
+An overview on hoaxes
In recent times, hoaxes have become increasingly prevalent as the internet continues to expand and as more people use social media. Misinformation is on a rise - though this is information which isn't really new, the current state of things is horrible, and things really shouldn't be the way they are.
I aim for this to be a brief blog post detailing the effect of hoaxes on society, focusing on why they're so harmful.
Put simply, a hoax is made-up information, be it a story or something else. Hoaxes are created with the intent of spreading false information - for a immense variety of reasons, from jokes and causing embarrassment to provoking politic or social change1. I won't discuss the causes of hoaxes further in this blog post.
Hoaxes can cause significant damage to their targets if formulated cleverly. For example:
The stock price of Apple Inc. fell significantly in October 2008 after a hoax story was submitted to CNN's user-generated news site iReport.com claiming that company CEO Steve Jobs had suffered a major heart attack. The source of the story was traced back to 4chan.
With the incredible presence of social media in our lives, spreading harmful misinformation like that above can be as simple as making a few posts - they don't even need to be very convincing! What makes matters worse is how gullible the general population is, even those educated in this sort of thing - this shows just how much influence the internet and it's contents have on us.
I would like to clarify that I'm not suggesting that people should avoid using the internet to gather information - while its reliability is incredibly questionable, the accessibility and openness it provides far beats traditional methods of gathering information (books and such). My suggestion is that people should be much more careful with how they interpret information on the internet, and perform their due diligence in their research into whatever they're aiming to learn; people should make sure that what they're reading is accurate before absorbing any information (here's your tl;dr).
That's about it for this blog post, as it was meant to be a brief way of expressing my thoughts on the matter. Thanks for reading!
\ No newline at end of file
diff --git a/public/blog/home-server-security/index.html b/public/blog/home-server-security/index.html
index 2412f75..ff24c89 100644
--- a/public/blog/home-server-security/index.html
+++ b/public/blog/home-server-security/index.html
@@ -19,4 +19,4 @@
};
};
};
-
This probably doesn't need to be said, but use strong passwords!
Host a fail2ban instance to ban hosts making bruteforce attempts.
I think that's all there is for almost everyone, and is basically the minimal amount of effort a home server administrator should do. Personally, I would prefer to enforce a VPN connection in order to access my personal services for that extra layer of security (because why'd they need to be exposed to the internet?). This can be done faily easily with tailscale, and for the slightly more paranoid - headscale is a viable...alternative? Anyways, I've got a blog post that explores headscale in a little more detail, which might be worth checking out.
Well, that's all I wanted to say. It's been a while since my last blog post, and the inspiration for this one came seemingly randomly - I hope someone finds this useful.
1
Naturally, you shouldn't just copy and paste the snippets into your own config. Do your research first!
\ No newline at end of file
+
This probably doesn't need to be said, but use strong passwords!
Host a fail2ban instance to ban hosts making bruteforce attempts.
I think that's all there is for almost everyone, and is basically the minimal amount of effort a home server administrator should do. Personally, I would prefer to enforce a VPN connection in order to access my personal services for that extra layer of security (because why'd they need to be exposed to the internet?). This can be done faily easily with tailscale, and for the slightly more paranoid - headscale is a viable...alternative? Anyways, I've got a blog post that explores headscale in a little more detail, which might be worth checking out.
Well, that's all I wanted to say. It's been a while since my last blog post, and the inspiration for this one came seemingly randomly - I hope someone finds this useful.
1
Naturally, you shouldn't just copy and paste the snippets into your own config. Do your research first!
\ No newline at end of file
diff --git a/public/blog/index.html b/public/blog/index.html
index fdd51ee..239749a 100644
--- a/public/blog/index.html
+++ b/public/blog/index.html
@@ -1 +1 @@
-Blog Posts
\ No newline at end of file
diff --git a/public/blog/nfc-misconceptions/index.html b/public/blog/nfc-misconceptions/index.html
index a5c1900..2b7e56f 100644
--- a/public/blog/nfc-misconceptions/index.html
+++ b/public/blog/nfc-misconceptions/index.html
@@ -1 +1 @@
-Misconceptions about NFC
I made a mistake while writing this blog post - somehow forgetting that security isn't unambiguous. You can actually skim NFC chips from a certain distance (having a limited distance is still an important factor though!), and though I think some of what I said below still applies you're better off ignoring it all.
There are, of course, a whole range of problems with skimming NFC chips from a distance so my point - don't be so worried - would still stand.
Either way, I recommend you take this with a grain of salt.
NFC (short for Near-Field Communication) is the set of communication protocols which allow for near-field communication between two electronic devices. One of the most prominent uses of this technology are contactless transactions - this includes services like Google and Apple Pay as well as all of your contactless-enabled cards.
It's been a while since my last blog past, but this one will be brief too - I'm writing here for the sake of clearing up some misconceptions people have about NFC.
While talking with a friend on a WhatsApp group chat a few days ago about a program I found on my jailbroken iOS device - Aemulo - I was informed of 'subway skimmers'; devices that could supposedly read data from contactless-enabled devices (via NFC) and would be able to emulate them.
The idea behind the above example was that someone with malicious intent could place such a device in a public location and take their contactless devices for their malicious purposes. When I heard of this, my first thought was: hoax, and I think that it was rightfully so.
Several things. I'm no expert in cybersecurity - everyone's a student in some way, but I was sure that NFC was, as it's name implies, for near-field communication. I'm repeating myself here, but that's kind of the point. Various reliable resources, including Wikipedia, show that NFC has a maximum range of only a few centimetres - which makes sense, no?
And yet, whatever source my friend had for 'subway skimmers' gave the impression, or otherwise stated, that it would work within a radius of a few feet, which is just impossible. Upon voicing my doubts, I was then told that 'with a powerful enough antenna, it's possible'. Hoaxes sure are convincing, aren't they? Unfortunately, I am not able to find the source of my friend's misinformation.
See, NFC only works within a few centimetres anyways. Even if it could magically work within a radius of a few feet, you've got to take in the electromagnetic interference that the clothes and wallets people have would bring to any malicious device. The point of electromagnetic interference is especially true over a huge area of a few feet (relatively), where you've got several NFC-enabled devices.
Of course, that isn't to say there aren't any issues with NFC and malicious readers - I'm just saying that the word getting around is horribly unrealistic. For example, a realistic example of a malicious NFC reader would be one placed on the card slots in cash machines - you get:
The short range (< ~20 cm)
Only one device
Lots of devices to read!
And so, you've got someone so much more realistic that poses an actual threat!
The information above, which I deem accurate, is there. What I suggest be taken away from this is pretty much the same as what is was for my blog post on hoaxes - do some fact-checking!
\ No newline at end of file
+Misconceptions about NFC
I made a mistake while writing this blog post - somehow forgetting that security isn't unambiguous. You can actually skim NFC chips from a certain distance (having a limited distance is still an important factor though!), and though I think some of what I said below still applies you're better off ignoring it all.
There are, of course, a whole range of problems with skimming NFC chips from a distance so my point - don't be so worried - would still stand.
Either way, I recommend you take this with a grain of salt.
NFC (short for Near-Field Communication) is the set of communication protocols which allow for near-field communication between two electronic devices. One of the most prominent uses of this technology are contactless transactions - this includes services like Google and Apple Pay as well as all of your contactless-enabled cards.
It's been a while since my last blog past, but this one will be brief too - I'm writing here for the sake of clearing up some misconceptions people have about NFC.
While talking with a friend on a WhatsApp group chat a few days ago about a program I found on my jailbroken iOS device - Aemulo - I was informed of 'subway skimmers'; devices that could supposedly read data from contactless-enabled devices (via NFC) and would be able to emulate them.
The idea behind the above example was that someone with malicious intent could place such a device in a public location and take their contactless devices for their malicious purposes. When I heard of this, my first thought was: hoax, and I think that it was rightfully so.
Several things. I'm no expert in cybersecurity - everyone's a student in some way, but I was sure that NFC was, as it's name implies, for near-field communication. I'm repeating myself here, but that's kind of the point. Various reliable resources, including Wikipedia, show that NFC has a maximum range of only a few centimetres - which makes sense, no?
And yet, whatever source my friend had for 'subway skimmers' gave the impression, or otherwise stated, that it would work within a radius of a few feet, which is just impossible. Upon voicing my doubts, I was then told that 'with a powerful enough antenna, it's possible'. Hoaxes sure are convincing, aren't they? Unfortunately, I am not able to find the source of my friend's misinformation.
See, NFC only works within a few centimetres anyways. Even if it could magically work within a radius of a few feet, you've got to take in the electromagnetic interference that the clothes and wallets people have would bring to any malicious device. The point of electromagnetic interference is especially true over a huge area of a few feet (relatively), where you've got several NFC-enabled devices.
Of course, that isn't to say there aren't any issues with NFC and malicious readers - I'm just saying that the word getting around is horribly unrealistic. For example, a realistic example of a malicious NFC reader would be one placed on the card slots in cash machines - you get:
The short range (< ~20 cm)
Only one device
Lots of devices to read!
And so, you've got someone so much more realistic that poses an actual threat!
The information above, which I deem accurate, is there. What I suggest be taken away from this is pretty much the same as what is was for my blog post on hoaxes - do some fact-checking!
\ No newline at end of file
diff --git a/public/blog/selfhost-search-engine/index.html b/public/blog/selfhost-search-engine/index.html
index ed49518..d3aaf3b 100644
--- a/public/blog/selfhost-search-engine/index.html
+++ b/public/blog/selfhost-search-engine/index.html
@@ -33,4 +33,4 @@
18
};
19
# ...
20
}
-
Note
The expression highlighted above is used to dynamically adjust the location NGINX will forward requests to, depending on your searx config
After saving your changes and rebuilding your server's system configuration (as usual), you should have a working private instance of SearXNG that you can access using the serverName you've given it.
Set your browser to use this as your search engine using the relevant documentation (with Firefox this is as easy as right-clicking on the URL after opening up the page and clicking a button). Enjoy!
\ No newline at end of file
+
Note
The expression highlighted above is used to dynamically adjust the location NGINX will forward requests to, depending on your searx config
After saving your changes and rebuilding your server's system configuration (as usual), you should have a working private instance of SearXNG that you can access using the serverName you've given it.
Set your browser to use this as your search engine using the relevant documentation (with Firefox this is as easy as right-clicking on the URL after opening up the page and clicking a button). Enjoy!
\ No newline at end of file
diff --git a/public/blog/selfhost-tailscale/index.html b/public/blog/selfhost-tailscale/index.html
index 6fceee2..2f41b5d 100644
--- a/public/blog/selfhost-tailscale/index.html
+++ b/public/blog/selfhost-tailscale/index.html
@@ -31,4 +31,4 @@
};
};
}
-
And that's it. A self-hosted, truly open-source Wireguard®-based VPN is now at your fingertips. Enjoy! Oh, but please read the conclusion before doing that:
For those of you who wish to have access to something like Tailscale but value your privacy above all, you would genuinely be greatful for Headscale. However, I've found that some are fine with what Tailscale does provide in regards to FOSS, and are satisfied by the raw convenience and simplicity of a non-selfhosted Tailscale control server - exactly what it hopes to provide, as shown by their self-description on their website: 'a zero-config, no-fuss VPN [provider]'.
Or you could just settle with bare Wireguard®.
\ No newline at end of file
+
And that's it. A self-hosted, truly open-source Wireguard®-based VPN is now at your fingertips. Enjoy! Oh, but please read the conclusion before doing that:
For those of you who wish to have access to something like Tailscale but value your privacy above all, you would genuinely be greatful for Headscale. However, I've found that some are fine with what Tailscale does provide in regards to FOSS, and are satisfied by the raw convenience and simplicity of a non-selfhosted Tailscale control server - exactly what it hopes to provide, as shown by their self-description on their website: 'a zero-config, no-fuss VPN [provider]'.
Or you could just settle with bare Wireguard®.
\ No newline at end of file
diff --git a/public/blog/server-hardware-selection/index.html b/public/blog/server-hardware-selection/index.html
index 6092437..5712ef4 100644
--- a/public/blog/server-hardware-selection/index.html
+++ b/public/blog/server-hardware-selection/index.html
@@ -1 +1 @@
-Selecting hardware for a (home) server
I see a lot of people worryingly mistaken about what a server needs (specifically, a home server). Some think that a bland and incredibly ignorant '20% budget for CPU, 30% for GPU, and the rest for the rest' plan for selecting hardware is good enough (at least, before choosing specific items) - you can't exactly be wrong when choosing hardware, but this is very, very far from right.
Server hardware needs to be low-power and resource-efficient - so as not to waste any money unnessarily, obviously. Your budget will strongly impact the specifications you can get your hands on, but I would think that even $200 is enough for a decent home server - depending on what you want to do with it. Keep in mind that you could always repurpose an old laptop or desktop lying around; it's cheap, and you get what may be a surprisingly decent machine.
The difference between low peak and low idle power should be noted in particular. Running costs can get very high if you don't work to moderate power consumption, and probably wouldn't be something you would ignore when it comes to home servers.
Naturally, how a server will be used will affect pretty much everything about the hardware chosen for it. For example, if you're looking to stream games remotely, you'd go for a (perhaps powerful) dedicated GPU and would likely invest in some high-speed internet solution. As indicated by the above example of the GPU, you need to be very specific with what you choose - do you need a powerful GPU or do you not? After all, one of the last things you would want, ever, is money going to waste on something you don't need, or failing to buy something that meets your expectations.
I only gave two points of interest when selecting a server - looking at the numbers alone, this might seem like hardly anything to consider at all. My reasons for this are:
Power comumption is one factor that people often forego thinking about, and an extremely important one at that.
Building on top of the previous point, you (probably) aren't stupid. Knowing (albeit at a very basic level) what to look out for should be enough.
It would be extremely difficult for me, or anyone else for that matter, to provide a truly complete solution to everyone's needs for a home server.
Well, that's it. I wish you luck in selecting your hardware.
\ No newline at end of file
+Selecting hardware for a (home) server
I see a lot of people worryingly mistaken about what a server needs (specifically, a home server). Some think that a bland and incredibly ignorant '20% budget for CPU, 30% for GPU, and the rest for the rest' plan for selecting hardware is good enough (at least, before choosing specific items) - you can't exactly be wrong when choosing hardware, but this is very, very far from right.
Server hardware needs to be low-power and resource-efficient - so as not to waste any money unnessarily, obviously. Your budget will strongly impact the specifications you can get your hands on, but I would think that even $200 is enough for a decent home server - depending on what you want to do with it. Keep in mind that you could always repurpose an old laptop or desktop lying around; it's cheap, and you get what may be a surprisingly decent machine.
The difference between low peak and low idle power should be noted in particular. Running costs can get very high if you don't work to moderate power consumption, and probably wouldn't be something you would ignore when it comes to home servers.
Naturally, how a server will be used will affect pretty much everything about the hardware chosen for it. For example, if you're looking to stream games remotely, you'd go for a (perhaps powerful) dedicated GPU and would likely invest in some high-speed internet solution. As indicated by the above example of the GPU, you need to be very specific with what you choose - do you need a powerful GPU or do you not? After all, one of the last things you would want, ever, is money going to waste on something you don't need, or failing to buy something that meets your expectations.
I only gave two points of interest when selecting a server - looking at the numbers alone, this might seem like hardly anything to consider at all. My reasons for this are:
Power comumption is one factor that people often forego thinking about, and an extremely important one at that.
Building on top of the previous point, you (probably) aren't stupid. Knowing (albeit at a very basic level) what to look out for should be enough.
It would be extremely difficult for me, or anyone else for that matter, to provide a truly complete solution to everyone's needs for a home server.
Well, that's it. I wish you luck in selecting your hardware.
\ No newline at end of file
diff --git a/public/blog/setting-up-zola-nixos/index.html b/public/blog/setting-up-zola-nixos/index.html
index b0eb94b..4d4e1f3 100644
--- a/public/blog/setting-up-zola-nixos/index.html
+++ b/public/blog/setting-up-zola-nixos/index.html
@@ -27,4 +27,4 @@
};
# ...
}
-
Hosting documentation (check out this Zola theme, for example)
Help, my changes aren't sticking!
When you make new markdown files (or any other changes to the structure of your site), remember to run zola build in your site directory (/var/lib/blog) for the changes to build into the actual site.
Hosting documentation (check out this Zola theme, for example)
Help, my changes aren't sticking!
When you make new markdown files (or any other changes to the structure of your site), remember to run zola build in your site directory (/var/lib/blog) for the changes to build into the actual site.
\ No newline at end of file
diff --git a/public/projects/index.html b/public/projects/index.html
index 748fa96..7661112 100644
--- a/public/projects/index.html
+++ b/public/projects/index.html
@@ -1 +1 @@
-Projects
\ No newline at end of file
diff --git a/public/tags/adblock/index.html b/public/tags/adblock/index.html
index 76f4783..81c5ed2 100644
--- a/public/tags/adblock/index.html
+++ b/public/tags/adblock/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/blocky/index.html b/public/tags/blocky/index.html
index 694e1e3..c2d0627 100644
--- a/public/tags/blocky/index.html
+++ b/public/tags/blocky/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/btrfs/index.html b/public/tags/btrfs/index.html
index d48e74c..b69d602 100644
--- a/public/tags/btrfs/index.html
+++ b/public/tags/btrfs/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/hacking/index.html b/public/tags/hacking/index.html
index 7cbf003..c34dbca 100644
--- a/public/tags/hacking/index.html
+++ b/public/tags/hacking/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/hardening/index.html b/public/tags/hardening/index.html
index 9cff730..ac326c0 100644
--- a/public/tags/hardening/index.html
+++ b/public/tags/hardening/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/hardware/index.html b/public/tags/hardware/index.html
index 96beab8..4b8de00 100644
--- a/public/tags/hardware/index.html
+++ b/public/tags/hardware/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/headscale/index.html b/public/tags/headscale/index.html
index d84ef0a..5e695fa 100644
--- a/public/tags/headscale/index.html
+++ b/public/tags/headscale/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/hoax/index.html b/public/tags/hoax/index.html
index 933d548..8a91c56 100644
--- a/public/tags/hoax/index.html
+++ b/public/tags/hoax/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/home-lab/index.html b/public/tags/home-lab/index.html
index a049d20..2c3c933 100644
--- a/public/tags/home-lab/index.html
+++ b/public/tags/home-lab/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/homelab/index.html b/public/tags/homelab/index.html
index d15c82b..2dbe86f 100644
--- a/public/tags/homelab/index.html
+++ b/public/tags/homelab/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/index.html b/public/tags/index.html
index ff52b88..1b35d23 100644
--- a/public/tags/index.html
+++ b/public/tags/index.html
@@ -1,3 +1,3 @@
Tags
\ No newline at end of file
diff --git a/public/tags/nas/index.html b/public/tags/nas/index.html
index 32361d7..d35f47d 100644
--- a/public/tags/nas/index.html
+++ b/public/tags/nas/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/nfc/index.html b/public/tags/nfc/index.html
index 7a3d043..c1f3960 100644
--- a/public/tags/nfc/index.html
+++ b/public/tags/nfc/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/nixos/index.html b/public/tags/nixos/index.html
index eac2b64..2267952 100644
--- a/public/tags/nixos/index.html
+++ b/public/tags/nixos/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/privacy/index.html b/public/tags/privacy/index.html
index e7ded9d..764a1d7 100644
--- a/public/tags/privacy/index.html
+++ b/public/tags/privacy/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/raid/index.html b/public/tags/raid/index.html
index af84122..1a1b5d1 100644
--- a/public/tags/raid/index.html
+++ b/public/tags/raid/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/raid0/index.html b/public/tags/raid0/index.html
index 3f6b449..063a945 100644
--- a/public/tags/raid0/index.html
+++ b/public/tags/raid0/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/raid1/index.html b/public/tags/raid1/index.html
index 9a112ee..0513985 100644
--- a/public/tags/raid1/index.html
+++ b/public/tags/raid1/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/raid10/index.html b/public/tags/raid10/index.html
index 6d0723f..97ffd2c 100644
--- a/public/tags/raid10/index.html
+++ b/public/tags/raid10/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/searxng/index.html b/public/tags/searxng/index.html
index 1891048..38c45c4 100644
--- a/public/tags/searxng/index.html
+++ b/public/tags/searxng/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/selfhosted/index.html b/public/tags/selfhosted/index.html
index 50b6bfe..a6617c2 100644
--- a/public/tags/selfhosted/index.html
+++ b/public/tags/selfhosted/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/social-engineering/index.html b/public/tags/social-engineering/index.html
index 7a299f9..3ac34ee 100644
--- a/public/tags/social-engineering/index.html
+++ b/public/tags/social-engineering/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/sysadmin/index.html b/public/tags/sysadmin/index.html
index 751e250..a1fcb3c 100644
--- a/public/tags/sysadmin/index.html
+++ b/public/tags/sysadmin/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/tailscale/index.html b/public/tags/tailscale/index.html
index b9f7b3d..b3d5127 100644
--- a/public/tags/tailscale/index.html
+++ b/public/tags/tailscale/index.html
@@ -1,3 +1,3 @@
Blog Posts
\ No newline at end of file
diff --git a/public/tags/zola/index.html b/public/tags/zola/index.html
index c28a7df..ae6f0fa 100644
--- a/public/tags/zola/index.html
+++ b/public/tags/zola/index.html
@@ -1,3 +1,3 @@
Blog Posts
