9 files changed, 61 insertions, 61 deletions

diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml
index 879864ac3..61f2df4e4 100644
--- a/.github/FUNDING.yml
+++ b/.github/FUNDING.yml
@@ -1,2 +1,2 @@
-github: getferdi
-open_collective: getferdi
+github: ferdium
+open_collective: ferdium
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
index dfb24d8fa..7b377c331 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -1,5 +1,5 @@
 name: Bug report
-description: Report a bug in Ferdi
+description: Report a bug in Ferdium
 title: "Describe your bug"
 labels: ["bug :beetle:"]
 body:
@@ -8,7 +8,7 @@ body:
     label: Avoid duplicates
     description: Please ensure you've completed the following
     options:
-      - label: I have searched the [issues tracker](https://github.com/getferdi/ferdi/issues) for a bug report similar to mine, in vain
+      - label: I have searched the [issues tracker](https://github.com/ferdium/ferdium-app/issues) for a bug report similar to mine, in vain
         required: true
 - type: textarea
   attributes:
@@ -24,7 +24,7 @@ body:
 - type: textarea
   attributes:
     label: Debug link
-    description: Get your debug link via Ferdi's "Help" > "Publish Debug Information", then share your link with us
+    description: Get your debug link via Ferdium's "Help" > "Publish Debug Information", then share your link with us
   validations:
     required: true
 - type: textarea
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index 26833093e..faf53ba74 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,5 +1,5 @@
 # blank_issues_enabled: false
 contact_links:
   - name: Frequently Asked Questions
-    url: https://getferdi.com/faq/
-    about: The FAQ answers the most frequently asked questions on Ferdi
+    url: https://ferdium.org/faq/
+    about: The FAQ answers the most frequently asked questions on Ferdium
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
index 679e007c3..89dde7dbf 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.yml
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -1,28 +1,28 @@
 name: Feature Request
-description: Suggest an idea for Ferdi
+description: Suggest an idea for Ferdium
 title: ""
 labels: ["enhancement :sparkles:"]
 body:
 - type: markdown
   attributes:
     value: |
-      1. Please remember that if you are logging a bug for some service that has *stopped working*, please log the bug [here](https://github.com/getferdi/recipes/issues)
-      2. If you are requesting support for a new service in Ferdi, please log it [here](https://github.com/getferdi/recipes/pulls)
-      3. Please remember to read the [self-help documentation](https://github.com/getferdi/ferdi#troubleshooting-recipes-self-help) - in case it helps you unblock yourself for issues related to old recipes.
+      1. Please remember that if you are logging a bug for some service that has *stopped working*, please log the bug [here](https://github.com/ferdium/recipes/issues)
+      2. If you are requesting support for a new service in Ferdium, please log it [here](https://github.com/ferdium/recipes/pulls)
+      3. Please remember to read the [self-help documentation](https://github.com/ferdium/ferdium#troubleshooting-recipes-self-help) - in case it helps you unblock yourself for issues related to old recipes.
       4. Please fill our form below, this way we can analyse and fix the problem as fast as possible.
-      5. Please consider supporting Ferdi!
-        👉  https://github.com/sponsors/getferdi
-        👉  https://opencollective.com/getferdi/donate
+      5. Please consider supporting Ferdium!
+        👉  https://github.com/sponsors/ferdium
+        👉  https://opencollective.com/ferdium/donate
 - type: checkboxes
   attributes:
     label: Preflight Checklist
     description: Please ensure you've completed all of the following.
     options:
-      - label: I have read the [Contributing Guidelines](https://github.com/getferdi/ferdi/blob/develop/CONTRIBUTING.md) for this project.
+      - label: I have read the [Contributing Guidelines](https://github.com/ferdium/ferdium-app/blob/develop/CONTRIBUTING.md) for this project.
         required: true
-      - label: I agree to follow the [Code of Conduct](https://github.com/getferdi/ferdi/blob/develop/CODE_OF_CONDUCT.md) that this project adheres to.
+      - label: I agree to follow the [Code of Conduct](https://github.com/ferdium/ferdium-app/blob/develop/CODE_OF_CONDUCT.md) that this project adheres to.
         required: true
-      - label: I have searched the [issue tracker](https://github.com/getferdi/ferdi/issues) for a feature request that matches the one I want to file, without success.
+      - label: I have searched the [issue tracker](https://github.com/ferdium/ferdium-app/issues) for a feature request that matches the one I want to file, without success.
         required: true
 - type: textarea
   attributes:
diff --git a/.github/ISSUE_TEMPLATE/open_issue.yml b/.github/ISSUE_TEMPLATE/open_issue.yml
index a7771be59..c6ab381e3 100644
--- a/.github/ISSUE_TEMPLATE/open_issue.yml
+++ b/.github/ISSUE_TEMPLATE/open_issue.yml
@@ -4,10 +4,10 @@ body:
 - type: markdown
   attributes:
     value: |
-      1. Please remember that if you are logging a bug for some service that has *stopped working*, please log the bug [here](https://github.com/getferdi/recipes/issues)
-      2. If you are requesting support for a new service in Ferdi, please log it [here](https://github.com/getferdi/recipes/pulls)
-      3. Please remember to read the [self-help documentation](https://github.com/getferdi/ferdi#troubleshooting-recipes-self-help) - in case it helps you unblock yourself for issues related to old recipes.
+      1. Please remember that if you are logging a bug for some service that has *stopped working*, please log the bug [here](https://github.com/ferdium/recipes/issues)
+      2. If you are requesting support for a new service in Ferdium, please log it [here](https://github.com/ferdium/recipes/pulls)
+      3. Please remember to read the [self-help documentation](https://github.com/ferdium/ferdium#troubleshooting-recipes-self-help) - in case it helps you unblock yourself for issues related to old recipes.
       4. Please fill our form below, this way we can analyse and fix the problem as fast as possible.
-      5. Please consider supporting Ferdi!
-        👉  https://github.com/sponsors/getferdi
-        👉  https://opencollective.com/getferdi/donate
+      5. Please consider supporting Ferdium!
+        👉  https://github.com/sponsors/ferdium
+        👉  https://opencollective.com/ferdium/donate
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index a777079a8..52b5abc09 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -5,17 +5,17 @@
 
 #### Pre-flight Checklist
 
-1. Please remember that if you are logging a bug for some service that has _stopped working_ or is _working incorrectly_, please log the bug [here](https://github.com/getferdi/recipes/issues)
-2. If you are requesting support for a **new service** in Ferdi, please log it [here](https://github.com/getferdi/recipes/pulls)
-3. Please remember to read the [self-help documentation](https://github.com/getferdi/ferdi#troubleshooting-recipes-self-help) - in case it helps you unblock yourself for issues related to older versions of recipes that were installed on your machine. (These will get automatically upgraded when you upgrade to the newer versions of Ferdi, but to get new recipes between Ferdi releases, this documentation is quite useful.)
-4. Please consider supporting Ferdi!
-  👉 https://github.com/sponsors/getferdi
-  👉 https://opencollective.com/getferdi/donate
+1. Please remember that if you are logging a bug for some service that has _stopped working_ or is _working incorrectly_, please log the bug [here](https://github.com/ferdium/recipes/issues)
+2. If you are requesting support for a **new service** in Ferdium, please log it [here](https://github.com/ferdium/recipes/pulls)
+3. Please remember to read the [self-help documentation](https://github.com/ferdium/ferdium#troubleshooting-recipes-self-help) - in case it helps you unblock yourself for issues related to older versions of recipes that were installed on your machine. (These will get automatically upgraded when you upgrade to the newer versions of Ferdium, but to get new recipes between Ferdium releases, this documentation is quite useful.)
+4. Please consider supporting Ferdium!
+  👉 https://github.com/sponsors/ferdium
+  👉 https://opencollective.com/ferdium/donate
 5. Please ensure you've completed all of the following.
 
-- [ ] I have read the [Contributing Guidelines](https://github.com/getferdi/ferdi/blob/develop/CONTRIBUTING.md) for this project.
-- [ ] I agree to follow the [Code of Conduct](https://github.com/getferdi/ferdi/blob/develop/CODE_OF_CONDUCT.md) that this project adheres to.
-- [ ] I have searched the [issue tracker](https://github.com/getferdi/ferdi/issues) for a feature request that matches the one I want to file, without success.
+- [ ] I have read the [Contributing Guidelines](https://github.com/ferdium/ferdium-app/blob/develop/CONTRIBUTING.md) for this project.
+- [ ] I agree to follow the [Code of Conduct](https://github.com/ferdium/ferdium-app/blob/develop/CODE_OF_CONDUCT.md) that this project adheres to.
+- [ ] I have searched the [issue tracker](https://github.com/ferdium/ferdium-app/issues) for a feature request that matches the one I want to file, without success.
 
 #### Description of Change
 <!-- Describe your changes in detail. -->
@@ -34,4 +34,4 @@
 - [ ] I tested/previewed my changes locally
 
 #### Release Notes
-<!-- Please add a one-line description for users of Ferdi to read in the release notes, or 'none' if no notes relevant to such users. Examples and help on special cases: https://github.com/electron/clerk/blob/master/README.md#examples -->
+<!-- Please add a one-line description for users of Ferdium to read in the release notes, or 'none' if no notes relevant to such users. Examples and help on special cases: https://github.com/electron/clerk/blob/master/README.md#examples -->
diff --git a/.github/release.yml b/.github/release.yml
index 6d8b15d02..6b8ac58bd 100644
--- a/.github/release.yml
+++ b/.github/release.yml
@@ -3,7 +3,7 @@ changelog:
     labels:
       - ignore-for-release
     authors:
-      - FerdiBot
+      - FerdiumBot
       - allcontributors
   categories:
     - title: Breaking Changes 🛠
diff --git a/.github/workflows/builds.yml b/.github/workflows/builds.yml
index cfb03bce0..fa078924d 100644
--- a/.github/workflows/builds.yml
+++ b/.github/workflows/builds.yml
@@ -2,7 +2,7 @@
 # For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
 
 # Note: This workflow requires some secrets setup, and set on this repo with the names:
-# 'FERDI_PUBLISH_TOKEN' (A GitHub Personal Access Token with appropriate permissions - for publishing the built artifacts)
+# 'FERDIUM_PUBLISH_TOKEN' (A GitHub Personal Access Token with appropriate permissions - for publishing the built artifacts)
 # 'APPLEID' (The username of your Apple developer account - for notarizing the mac artifacts)
 # 'APPLEID_PASSWORD' (An app-specific password - for notarizing the mac artifacts)
 # 'CSC_LINK' (The HTTPS link or local path to certificate - for code signing of mac artifacts)
@@ -46,7 +46,7 @@ jobs:
           ref: nightly
           submodules: recursive
           fetch-depth: 0 # Note: Needed to be able to pull the 'develop' branch as well for merging
-          # ssh-key: ${{ secrets.FERDI_PUBLISH_TOKEN }}
+          # ssh-key: ${{ secrets.FERDIUM_PUBLISH_TOKEN }}
       - name: Use Node.js specified in the '.nvmrc' file
         uses: actions/setup-node@v2
         if: ${{ github.event_name == 'schedule' || (github.event_name == 'workflow_dispatch' && contains(github.event.inputs.message, '[nightly branch]')) }}
@@ -105,7 +105,7 @@ jobs:
           echo "ELECTRON_CACHE=$HOME/.cache/electron" >> $GITHUB_ENV
           echo "ELECTRON_BUILDER_CACHE=$HOME/.cache/electron-builder" >> $GITHUB_ENV
           echo "MANUAL_REBUILD_ON_NIGHTLY=${{ github.event_name == 'workflow_dispatch' && contains(github.event.inputs.message, '[nightly branch]') }}" >> $GITHUB_ENV
-          echo "SKIP_NOTARIZATION=${{ !contains(github.repository_owner, 'getferdi') }}" >> $GITHUB_ENV
+          echo "SKIP_NOTARIZATION=${{ !contains(github.repository_owner, 'ferdium') }}" >> $GITHUB_ENV
       - name: Checkout code along with submodules for the 'nightly' branch if the trigger event is 'scheduled' or this is a forced rebuild on the nightly branch
         uses: actions/checkout@v2
         if: ${{ github.event_name == 'schedule' || env.MANUAL_REBUILD_ON_NIGHTLY == 'true' }}
@@ -149,26 +149,26 @@ jobs:
         working-directory: ./recipes
       - name: Run linter and tests
         run: npm run lint && npm run test
-      - name: Build Ferdi without publish for any branch not 'nightly' and not 'release'
+      - name: Build Ferdium without publish for any branch not 'nightly' and not 'release'
         if: ${{ env.GIT_BRANCH_NAME != 'nightly' && env.GIT_BRANCH_NAME != 'release' }}
         run: npm run build -- --publish never
         shell: bash
-      - name: Build Ferdi with publish for 'nightly' branch
+      - name: Build Ferdium with publish for 'nightly' branch
         if: ${{ env.GIT_BRANCH_NAME == 'nightly' }}
         run: npm run build -- --publish always -c.publish.provider=github -c.publish.owner=${{ github.repository_owner }}
         shell: bash
         env:
-          GH_TOKEN: ${{ secrets.FERDI_PUBLISH_TOKEN }}
+          GH_TOKEN: ${{ secrets.FERDIUM_PUBLISH_TOKEN }}
           APPLEID: ${{ secrets.APPLEID }}
           APPLEID_PASSWORD: ${{ secrets.APPLEID_PASSWORD }}
           CSC_LINK: ${{ secrets.CSC_LINK }}
           CSC_KEY_PASSWORD: ${{ secrets.CSC_KEY_PASSWORD }}
-      - name: Build Ferdi with publish for 'release' branch
+      - name: Build Ferdium with publish for 'release' branch
         if: ${{ env.GIT_BRANCH_NAME == 'release' }}
-        run: npm run build -- --publish always -c.publish.provider=github -c.publish.owner=${{ github.repository_owner }} -c.publish.repo=ferdi
+        run: npm run build -- --publish always -c.publish.provider=github -c.publish.owner=${{ github.repository_owner }} -c.publish.repo=ferdium
         shell: bash
         env:
-          GH_TOKEN: ${{ secrets.FERDI_PUBLISH_TOKEN }}
+          GH_TOKEN: ${{ secrets.FERDIUM_PUBLISH_TOKEN }}
           APPLEID: ${{ secrets.APPLEID }}
           APPLEID_PASSWORD: ${{ secrets.APPLEID_PASSWORD }}
           CSC_LINK: ${{ secrets.CSC_LINK }}
@@ -187,7 +187,7 @@ jobs:
           echo "ELECTRON_CACHE=$HOME/.cache/electron" >> $GITHUB_ENV
           echo "ELECTRON_BUILDER_CACHE=$HOME/.cache/electron-builder" >> $GITHUB_ENV
           echo "MANUAL_REBUILD_ON_NIGHTLY=${{ github.event_name == 'workflow_dispatch' && contains(github.event.inputs.message, '[nightly branch]') }}" >> $GITHUB_ENV
-          echo "SKIP_NOTARIZATION=${{ !contains(github.repository_owner, 'getferdi') }}" >> $GITHUB_ENV
+          echo "SKIP_NOTARIZATION=${{ !contains(github.repository_owner, 'ferdium') }}" >> $GITHUB_ENV
       - name: Checkout code along with submodules for the 'nightly' branch if the trigger event is 'scheduled' or this is a forced rebuild on the nightly branch
         uses: actions/checkout@v2
         if: ${{ github.event_name == 'schedule' || env.MANUAL_REBUILD_ON_NIGHTLY == 'true' }}
@@ -234,14 +234,14 @@ jobs:
         working-directory: ./recipes
       - name: Run linter and tests
         run: npm run lint && npm run test
-      - name: Build Ferdi without publish for any branch not 'nightly' and not 'release'
+      - name: Build Ferdium without publish for any branch not 'nightly' and not 'release'
         if: ${{ env.GIT_BRANCH_NAME != 'nightly' && env.GIT_BRANCH_NAME != 'release' }}
         run: npm run build -- --publish never
         shell: bash
-      - name: Build Ferdi with publish for 'nightly' branch
+      - name: Build Ferdium with publish for 'nightly' branch
         if: ${{ env.GIT_BRANCH_NAME == 'nightly' }}
         env:
-          GH_TOKEN: ${{ secrets.FERDI_PUBLISH_TOKEN }}
+          GH_TOKEN: ${{ secrets.FERDIUM_PUBLISH_TOKEN }}
           CSC_IDENTITY_AUTO_DISCOVERY: false
           SNAPCRAFT_LOGIN: ${{ secrets.SNAPCRAFT_LOGIN }}
         run: |
@@ -250,28 +250,28 @@ jobs:
           npm run build -- --publish always -c.publish.provider=github -c.publish.owner=${{ github.repository_owner }} -c.snap.publish.provider=snapStore -c.snap.publish.repo=nightlies -c.snap.publish.channels=edge
           snapcraft logout
         shell: bash
-      - name: Build Ferdi with publish for 'release' beta branch
+      - name: Build Ferdium with publish for 'release' beta branch
         if: ${{ env.GIT_BRANCH_NAME == 'release' && contains(env.PACKAGE_VERSION, 'beta') }}
         env:
-          GH_TOKEN: ${{ secrets.FERDI_PUBLISH_TOKEN }}
+          GH_TOKEN: ${{ secrets.FERDIUM_PUBLISH_TOKEN }}
           CSC_IDENTITY_AUTO_DISCOVERY: false
           SNAPCRAFT_LOGIN: ${{ secrets.SNAPCRAFT_LOGIN }}
         run: |
           sudo snap install snapcraft --classic
           echo "$SNAPCRAFT_LOGIN" | snapcraft login --with -
-          npm run build -- --publish always -c.publish.provider=github -c.publish.owner=${{ github.repository_owner }} -c.publish.repo=ferdi -c.snap.publish.provider=snapStore -c.snap.publish.repo=ferdi -c.snap.publish.channels=beta
+          npm run build -- --publish always -c.publish.provider=github -c.publish.owner=${{ github.repository_owner }} -c.publish.repo=ferdium -c.snap.publish.provider=snapStore -c.snap.publish.repo=ferdium -c.snap.publish.channels=beta
           snapcraft logout
         shell: bash
-      - name: Build Ferdi with publish for 'release' stable branch
+      - name: Build Ferdium with publish for 'release' stable branch
         if: ${{ env.GIT_BRANCH_NAME == 'release' && !contains(env.PACKAGE_VERSION, 'beta') }}
         env:
-          GH_TOKEN: ${{ secrets.FERDI_PUBLISH_TOKEN }}
+          GH_TOKEN: ${{ secrets.FERDIUM_PUBLISH_TOKEN }}
           CSC_IDENTITY_AUTO_DISCOVERY: false
           SNAPCRAFT_LOGIN: ${{ secrets.SNAPCRAFT_LOGIN }}
         run: |
           sudo snap install snapcraft --classic
           echo "$SNAPCRAFT_LOGIN" | snapcraft login --with -
-          npm run build -- --publish always -c.publish.provider=github -c.publish.owner=${{ github.repository_owner }} -c.publish.repo=ferdi -c.snap.publish.provider=snapStore -c.snap.publish.repo=ferdi -c.snap.publish.channels=stable
+          npm run build -- --publish always -c.publish.provider=github -c.publish.owner=${{ github.repository_owner }} -c.publish.repo=ferdium -c.snap.publish.provider=snapStore -c.snap.publish.repo=ferdium -c.snap.publish.channels=stable
           snapcraft logout
         shell: bash
 
@@ -285,7 +285,7 @@ jobs:
         run: |
           echo "HOME=$USERPROFILE" >> $GITHUB_ENV
           echo "MANUAL_REBUILD_ON_NIGHTLY=${{ github.event_name == 'workflow_dispatch' && contains(github.event.inputs.message, '[nightly branch]') }}" >> $GITHUB_ENV
-          echo "SKIP_NOTARIZATION=${{ !contains(github.repository_owner, 'getferdi') }}" >> $GITHUB_ENV
+          echo "SKIP_NOTARIZATION=${{ !contains(github.repository_owner, 'ferdium') }}" >> $GITHUB_ENV
         shell: bash
       - name: Checkout code along with submodules for the 'nightly' branch if the trigger event is 'scheduled' or this is a forced rebuild on the nightly branch
         uses: actions/checkout@v2
@@ -325,23 +325,23 @@ jobs:
       - name: Run linter and tests
         run: npm run lint && npm run test
         shell: bash
-      - name: Build Ferdi without publish for any branch not 'nightly' and not 'release'
+      - name: Build Ferdium without publish for any branch not 'nightly' and not 'release'
         if: ${{ env.GIT_BRANCH_NAME != 'nightly' && env.GIT_BRANCH_NAME != 'release' }}
         run: npm run build -- --publish never
         shell: bash
-      - name: Build Ferdi with publish for 'nightly' branch
+      - name: Build Ferdium with publish for 'nightly' branch
         if: ${{ env.GIT_BRANCH_NAME == 'nightly' }}
         run: npm run build -- --publish always -c.publish.provider=github -c.publish.owner=${{ github.repository_owner }}
         shell: bash
         env:
-          GH_TOKEN: ${{ secrets.FERDI_PUBLISH_TOKEN }}
+          GH_TOKEN: ${{ secrets.FERDIUM_PUBLISH_TOKEN }}
           WIN_CSC_LINK: ${{ secrets.WIN_CSC_LINK }}
           WIN_CSC_KEY_PASSWORD: ${{ secrets.WIN_CSC_KEY_PASSWORD }}
-      - name: Build Ferdi with publish for 'release' branch
+      - name: Build Ferdium with publish for 'release' branch
         if: ${{ env.GIT_BRANCH_NAME == 'release' }}
-        run: npm run build -- --publish always -c.publish.provider=github -c.publish.owner=${{ github.repository_owner }} -c.publish.repo=ferdi
+        run: npm run build -- --publish always -c.publish.provider=github -c.publish.owner=${{ github.repository_owner }} -c.publish.repo=ferdium
         shell: bash
         env:
-          GH_TOKEN: ${{ secrets.FERDI_PUBLISH_TOKEN }}
+          GH_TOKEN: ${{ secrets.FERDIUM_PUBLISH_TOKEN }}
           WIN_CSC_LINK: ${{ secrets.WIN_CSC_LINK }}
           WIN_CSC_KEY_PASSWORD: ${{ secrets.WIN_CSC_KEY_PASSWORD }}
diff --git a/.github/workflows/dependency-updates.yml b/.github/workflows/dependency-updates.yml
index eb69b049b..0f6befb55 100644
--- a/.github/workflows/dependency-updates.yml
+++ b/.github/workflows/dependency-updates.yml
@@ -1,4 +1,4 @@
-# This workflow will do a clean install of ferdi dev-dependencies, update the dependencies, build the source code and run tests. It will only run on scheduled trigger.
+# This workflow will do a clean install of ferdium dev-dependencies, update the dependencies, build the source code and run tests. It will only run on scheduled trigger.
 
 name: Dependency updates