paritybit.ca

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit a1ec5f5b2d15d8eae43e96cc1b3a8849f633310e
parent 05adea25d4d6b9556b821f76ed17edf7e707a4fd
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Thu, 20 Jun 2019 23:36:09 -0400

Change Essays to Blogs and add new post

Diffstat:
Mbuild/header.html | 2+-
Mcreatepages.sh | 2++
Apages/blog.md | 19+++++++++++++++++++
Apages/blog/qutebrowser-to-firefox.md | 69+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Dpages/essays.md | 7-------
Mpages/home.md | 3+++
6 files changed, 94 insertions(+), 8 deletions(-)

diff --git a/build/header.html b/build/header.html @@ -18,7 +18,7 @@ <div id="side-bar"> <ul> <li><a href="/">Home<a/></li> - <li><a href="/essays">Essays</a></li> + <li><a href="/blog">Blog</a></li> <li><a href="/projects">Projects</a></li> <li><a href="/guides">Guides<a/></li> <li><a href="/about-me">About Me</a></li> diff --git a/createpages.sh b/createpages.sh @@ -72,6 +72,7 @@ for page in $@; do # Assumes first line of every markdown file is the header in the format: # "## Title of The Page" pagetitle=$(head -n 1 $filepath/$pagename.md | cut -f 2- -d " ") + echo " Setting page title..." sed -i "s/<title>.*<\/title>/<title>paritybit.ca – ${pagetitle//&/\\&}<\/title>/" \ $htmldir/$savepath/$pagename.html @@ -80,6 +81,7 @@ for page in $@; do metatext=$(sed '3!d' $filepath/$pagename.md | cut -d# -f 2) # Remove leading whitespace metatextclean=$(echo -e "${metatext}" | sed -e 's/^[[:space:]]*//') + echo " Setting meta tag..." sed -i "s/content=\"\"/content=${metatextclean//&/\\&}/" \ $htmldir/$savepath/$pagename.html diff --git a/pages/blog.md b/pages/blog.md @@ -0,0 +1,19 @@ +## Blog + +[//]: # "This is the place where I put all of my ramblings, rants, essays, and random thoughts and ideas." + +[//]: # "base.min.css" + +This is the place where I put all of my ramblings, rants, essays, and random thoughts and ideas. + +Below you can find links to things that I have posted: + +### Blogs +<ul> + <li><a href="blog/qutebrowser-to-firefox">Why I Switched Back to Firefox + from Qutebrowser</a></li> +</ul> + +### Essays + +None yet! diff --git a/pages/blog/qutebrowser-to-firefox.md b/pages/blog/qutebrowser-to-firefox.md @@ -0,0 +1,69 @@ +## Why I Switched Back to Firefox from Qutebrowser + +[//]: # "I've been using qutebrowser for about six months now but I found it really wasn't meeting my needs. In this post I explain the reasons why I switched back to using Firefox." + +[//]: # "base.min.css" + +<b>Written By:</b> Jake Bauer | + <b>Posted:</b> 2019-06-20 | + <b>Last Updated:</b> 2019-06-20 + +I've been using qutebrowser for about six months now as my primary browser after +switching to it from GNU/IceCat seeking a browsing experience with solid +vim-like controls. At first, I enjoyed the simplicity and shortcuts afforded by +qutebrowser but noticed more and more issues as time went on. Qutebrowser, while +very usable as a browser, falls short in some key areas that are important to +me. + +Privacy online is something that is very important to me and should be important +to everyone who uses the internet. It's one of the reasons I donate to the +<a href="https://www.eff.org">Electronic Frontier Foundation</a> and probably +the biggest reason I switched back to Firefox from qutebrowser. Although there +are limited things you can do in qutebrowser to block some trackers such as +changing your user agent string, it is still quite limited compared to Firefox. +You have to launch qutebrowser with a command line flag just to disable reading +from the HTML canvas and there isn't even an option to disable WebRTC. This is +in stark contrast to Firefox which—even ignoring the capabilities of extensions +such as <a href="https://addons.mozilla.org/en-US/firefox/addon/privacy-badger17/">Privacy Badger</a> +and <a href="https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/">uBlock Origin</a>—allows +you to enable privacy features like fingerprinting resistance and disable +potentially bad features like WebRTC from within the built-in configuration +window. + +Another big factor is that some sites which I would use would have elements that +wouldn't load or work properly in qutebrowser and I would have to switch over to +Firefox to use them. For example, I run a Proxmox virtualization host on my +server and any time I tried view my virtual machines using noVNC or Spice, the +screens would be black and it wouldn't work. Another issue happens when websites +update search suggestions live as you type. With the way some websites would do +this, I would get kicked out of insert mode in the middle of typing which would +usually result in the tab suddenly closing or me activating something I didn't +intend to activate since I was booted back to normal mode. This made for a very +frustrating browsing experience on those websites. This specific point isn't so +much a fault with qutebrowser and more a fault with some modern websites but, +alas, it made using Firefox feel that much smoother and better. + +I also found Firefox much easier to develop on compared to qutebrowser. It could +be because I'm just not used to the Chromium-family set of web development tools +but I find Firefox's set much more intuitive and the easy-to-use live stylesheet +editor makes it really easy for me to experiment with what my web pages look +like right in the browser. Plus I found the network-related tools easier to +understand and navigate in Firefox than in qutebrowser. + +Those are the big three reasons why I switched back to Firefox but I did have +some other very minor problems which, when put all together, pushed me over the +edge to switch. The first of which is that, since I use KeePassXC as my password +manager, the extension available for Firefox makes it much more convenient to +enter my credentials instead of having to copy-paste. The second is that Firefox +is using the Gecko web rendering engine which I feel better about using due to +Mozilla's commitment to a free and open web. The last minor reason for making me +switch is that Firefox has multiple extensions which enable vim-like controls. +Although these can't be as full-featured as a browser designed around those +controls, I have found the one I am using—<a +href="https://addons.mozilla.org/en-US/firefox/addon/vim-vixen/">Vim +Vixen</a>—to be good enough for my uses. + +Overall, qutebrowser still is a commendable browser and, if the reasons I listed +above don't really concern you that much, I would recommend checking it out. +Unfortunately it didn't fit well with what I wanted out of a browser and that's +why I switched from qutebrowser to Firefox. diff --git a/pages/essays.md b/pages/essays.md @@ -1,7 +0,0 @@ -## Essays - -[//]: # "Essays on computer science, life, software development, and more." - -[//]: # "base.min.css" - -There are no essays here yet but check back periodically for more! diff --git a/pages/home.md b/pages/home.md @@ -15,6 +15,9 @@ be something that interests you! ### Recently Updated +<a href="blog/qutebrowser-to-firefox">New Blog Post: Why I Switched Back to +Firefox from Qutebrowser</a> + <a href="projects/dnd/initiative">The D&D Initiative Tracker has just been released!</a> <a href="projects/dnd/roll">The D&D Dice Roller has been updated!</a>