From a251967bec8f769a04e2b752b3bb132123dd3f94 Mon Sep 17 00:00:00 2001
From: Nyx <me@everypizza.im>
Date: Tue, 15 Apr 2025 22:26:06 -0500
Subject: [PATCH] hkgvujghdujch

---
 .../dont-use-chromium/dont-use-chromium.md    | 30 +++++++++++++++++--
 .../hosting-nadeko-invidious.md               | 18 +++++++++++
 2 files changed, 45 insertions(+), 3 deletions(-)
 create mode 100644 content/blog/hosting-nadeko-invidious/hosting-nadeko-invidious.md

diff --git a/content/blog/dont-use-chromium/dont-use-chromium.md b/content/blog/dont-use-chromium/dont-use-chromium.md
index ff62836..491dc8f 100644
--- a/content/blog/dont-use-chromium/dont-use-chromium.md
+++ b/content/blog/dont-use-chromium/dont-use-chromium.md
@@ -11,12 +11,36 @@ Chromium, the most popular browser. Over 60% of the Internet
 uses Chromium. The 3rd most popular browser is Microsoft Edge,
 based on Chromium, at 5%. 
 
-# Monopolies
+## "Vanilla" Chromium
+
+### Monopolies
 
 As stated above, Chrome has a monopoly in web browsers. Not much
 more needs to be said here, other than that obviously monopolies
 are bad.
 
-# Privacy
+### Privacy
 
-Google is the largest tracking company in the world. 
\ No newline at end of file
+Google is the largest tracking company in the world. They have
+billions of dollars, and a lot of that is invested into tracking
+users. Something like ungoogled-chromium can't possibly remove
+_every_ single tracker in Chromium, it's just too big of a
+codebase.
+
+### Security
+
+Using Chrome would provide more security than a fork, but that
+would significantly decrease privacy. Forks of Chromium like
+Thorium etc have delayed updates, so it takes longer to get
+critical security fixes.
+
+## Microsoft Edge
+
+It's in the title.
+
+## Other forks
+
+Most other forks are irrelavant in the grand scheme of things.
+The above applies.
+
+<small>this one is tired awawawawawawawawawa</small>
\ No newline at end of file
diff --git a/content/blog/hosting-nadeko-invidious/hosting-nadeko-invidious.md b/content/blog/hosting-nadeko-invidious/hosting-nadeko-invidious.md
new file mode 100644
index 0000000..2d8ef9e
--- /dev/null
+++ b/content/blog/hosting-nadeko-invidious/hosting-nadeko-invidious.md
@@ -0,0 +1,18 @@
+---js
+const title = "Hosting a Invidious instance with the nadeko.net fork";
+const date = "2025-04-10";
+const draft = true;
+const tags = ["proxies", "everypizza.im", "hosting"];
+---
+
+So, this one tried to set up an Invidious instance. It somehow broke after
+a few minutes. So, it decided to try setting up one with the nadeko.net fork.
+In the end, that was a lot harder, but it works a lot better.
+
+### Getting the compose files
+
+This one's compose file is [here](https://git.everypizza.im/everypizza.im/compose-files/src/branch/main/invidious.yml).
+It's modified from 
+[Fijxu's compose](https://git.nadeko.net/Fijxu/docker-compose-configs/src/branch/master/invidious/invidious-all/docker-compose.yml),
+although the Nyx one will probably be a lot easier to manage. However, you still
+need to get the configs from Fijxu.
\ No newline at end of file