Content update: user.js-notify.sh script for Firefox

I made a few small changes to my user.js-notify.sh script. This bash (Linux) script checks for updates to the 'arkenfox' user.js, my user-overrides.js, and also checks the last updated dates of my Firefox configuration guides.

The intention of this script is to automatically check for updates rather than running the 'arkenfox' updater script manually, plus it checks other stuff as mentioned.

The script can be download here and changes are here, however those already running the script will be notified automatically of the update.

Update: user-overrides.js for Firefox

I updated my user-overrides.js config file for Firefox to align with the release of Firefox v84 and the 'arkenfox' user.js. The file can be downloaded here and the changes can be found here. Remember to run the 'arkenfox' prefsCleaner script after updating.

If this all Greek to you but you're curious, see either of my Firefox config guides.

And now back to our regularly scheduled program...

Content update: Firefox Configuration Guide for Privacy Freaks and Performance Buffs

I made a few changes to the Firefox Configuration Guide for Privacy Freaks and Performance Buffs...

  • updated info for the privacy settings for uMatrix
  • removed HTTPZ add-on and associated info - no longer needed since Firefox v83 as long as dom.security.https_only_mode is enabled
  • minor clarifications, edits

Firefox 83 alleviates need for HTTP to HTTPS add-ons

Firefox 83 alleviates the need for HTTP to HTTPS redirect add-ons such as HTTPS Everywhere and HTTPZ, however the feature is not enabled by default. Here's how to enable it...

If you're not running a custom user.js file (if you don't know what that is, you're probably not), enter about:config in the address bar and in the filter field at the top enter dom.security.https_only_mode . Set that preference to 'true' and you're done.

If you are running the 'arkenfox' user.js, you should have a user-overrides.js where you keep your personal preferences. In this case, just add the dom.security.https_only_mode preference to it:

user_pref("dom.security.https_only_mode", true);

If you use your own user.js, you already know what to do.

This preference will force all websites to use an encrypted connection (HTTPS). In the case where that isn't possible, Firefox will display a warning from which you can temporarily override the redirect and load the website without using encryption. If you always want to allow the unencrypted connection, you can add an exception for the site by clicking the lock icon in the address bar.

While the new functionality isn't as transparent as with the HTTPZ add-on, it's a welcome and overdue addition in my opinion.