Reset README back to HEAD

This is for tom's runners, whilst they're having network issues

.forgejo/workflows/build-alpine.yml

@@ -1,49 +0,0 @@
-on: 
-  - workflow-dispatch
-  - push
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    container:
-      image: alpine:edge
-
-    steps:
-      - name: set up dependencies
-        run: |
-          apk update 
-          apk upgrade 
-          apk add nodejs git alpine-sdk
-      - uses: actions/checkout@v4
-        name: checkout the alpine dir  
-        with: 
-          sparse-checkout: "alpine/"
-
-      # - uses: actions/checkout@v4
-      #   name: checkout the rest in the alpine dir
-      #   with:
-      #     path: 'alpine/continuwuity'
-      - name: set up user 
-        run: adduser -DG abuild ci 
-
-      - name: set up keys
-        run: |
-          pwd
-          mkdir ~/.abuild 
-          echo "${{ secrets.abuild_privkey }}" > ~/.abuild/ci@continuwuity.rsa
-          echo "${{ secrets.abuild_pubkey }}" > ~/.abuild/ci@continuwuity.rsa.pub 
-          echo $HOME
-          echo 'PACKAGER_PRIVKEY="/root/.abuild/ci@continuwuity.rsa"' > ~/.abuild/abuild.conf 
-          ls ~/.abuild
-
-      - name: go go gadget abuild 
-        run: |
-          cd alpine 
-          # modify the APKBUILD to use the current branch instead of the release
-          # note that it seems to require the repo to be public (as you'll get 
-          # a 404 even if the token is provided)
-          export ARCHIVE_URL="${{ github.server_url }}/${{ github.repository }}/archive/${{ github.ref_name }}.tar.gz"
-          echo $ARCHIVE_URL
-          sed -i '/^source=/c\source="'"$ARCHIVE_URL" APKBUILD 
-          abuild -F checksum
-          abuild -Fr

.forgejo/workflows/documentation.yml

@@ -16,7 +16,7 @@ concurrency:
 jobs:
   docs:
     name: Build and Deploy Documentation
-    runs-on: ubuntu-latest
+    runs-on: not-nexy
 
     steps:
       - name: Sync repository
@@ -36,14 +36,9 @@ jobs:
       - name: Prepare static files for deployment
         run: |
           mkdir -p ./public/.well-known/matrix
-          mkdir -p ./public/.well-known/continuwuity
-          mkdir -p ./public/schema
           # Copy the Matrix .well-known files
           cp ./docs/static/server ./public/.well-known/matrix/server
           cp ./docs/static/client ./public/.well-known/matrix/client
-          cp ./docs/static/client ./public/.well-known/matrix/support
-          cp ./docs/static/announcements.json ./public/.well-known/continuwuity/announcements
-          cp ./docs/static/announcements.schema.json ./public/schema/announcements.schema.json
           # Copy the custom headers file
           cp ./docs/static/_headers ./public/_headers
           echo "Copied .well-known files and _headers to ./public"
@@ -57,17 +52,17 @@ jobs:
         run: npm install --save-dev wrangler@latest
 
       - name: Deploy to Cloudflare Pages (Production)
-        if: github.ref == 'refs/heads/main' && vars.CLOUDFLARE_PROJECT_NAME != ''
+        if: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }}
         uses: https://github.com/cloudflare/wrangler-action@v3
         with:
           accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
           apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
-          command: pages deploy ./public --branch="main" --commit-dirty=true --project-name="${{ vars.CLOUDFLARE_PROJECT_NAME }}"
+          command: pages deploy ./public --branch=main --commit-dirty=true --project-name=${{ vars.CLOUDFLARE_PROJECT_NAME }}"
 
       - name: Deploy to Cloudflare Pages (Preview)
-        if: github.ref != 'refs/heads/main' && vars.CLOUDFLARE_PROJECT_NAME != ''
+        if: ${{ github.event_name != 'push' || github.ref != 'refs/heads/main' }}
         uses: https://github.com/cloudflare/wrangler-action@v3
         with:
           accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
           apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
-          command: pages deploy ./public --branch="${{ github.head_ref || github.ref_name }}" --commit-dirty=true --project-name="${{ vars.CLOUDFLARE_PROJECT_NAME }}"
+          command: pages deploy ./public --branch=${{ github.head_ref }} --commit-dirty=true --project-name=${{ vars.CLOUDFLARE_PROJECT_NAME }}"

.forgejo/workflows/element.yml

@@ -1,127 +0,0 @@
-name: Deploy Element Web
-
-on:
-  schedule:
-    - cron: "0 0 * * *"
-  workflow_dispatch:
-
-concurrency:
-  group: "element-${{ github.ref }}"
-  cancel-in-progress: true
-
-jobs:
-  build-and-deploy:
-    name: Build and Deploy Element Web
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Setup Node.js
-        uses: https://code.forgejo.org/actions/setup-node@v4
-        with:
-          node-version: "20"
-
-      - name: Clone, setup, and build Element Web
-        run: |
-          echo "Cloning Element Web..."
-          git clone https://github.com/maunium/element-web
-          cd element-web
-          git checkout develop
-          git pull
-
-          echo "Cloning matrix-js-sdk..."
-          git clone https://github.com/matrix-org/matrix-js-sdk.git
-
-          echo "Installing Yarn..."
-          npm install -g yarn
-
-          echo "Installing dependencies..."
-          yarn install
-
-          echo "Preparing build environment..."
-          mkdir -p .home
-
-          echo "Cleaning up specific node_modules paths..."
-          rm -rf node_modules/@types/eslint-scope/ matrix-*-sdk/node_modules/@types/eslint-scope || echo "Cleanup paths not found, continuing."
-
-          echo "Getting matrix-js-sdk commit hash..."
-          cd matrix-js-sdk
-          jsver=$(git rev-parse HEAD)
-          jsver=${jsver:0:12}
-          cd ..
-          echo "matrix-js-sdk version hash: $jsver"
-
-          echo "Getting element-web commit hash..."
-          ver=$(git rev-parse HEAD)
-          ver=${ver:0:12}
-          echo "element-web version hash: $ver"
-
-          chmod +x ./build-sh
-
-          export VERSION="$ver-js-$jsver"
-          echo "Building Element Web version: $VERSION"
-          ./build-sh
-
-          echo "Checking for build output..."
-          ls -la webapp/
-
-      - name: Create config.json
-        run: |
-          cat <<EOF > ./element-web/webapp/config.json
-          {
-            "default_server_name": "continuwuity.org",
-            "default_server_config": {
-              "m.homeserver": {
-                "base_url": "https://matrix.continuwuity.org"
-              }
-            },
-            "default_country_code": "GB",
-            "default_theme": "dark",
-            "mobile_guide_toast": false,
-            "show_labs_settings": true,
-            "room_directory": [
-              "continuwuity.org",
-              "matrixrooms.info"
-            ],
-            "settings_defaults": {
-              "UIFeature.urlPreviews": true,
-              "UIFeature.feedback": false,
-              "UIFeature.voip": false,
-              "UIFeature.shareQrCode": false,
-              "UIFeature.shareSocial": false,
-              "UIFeature.locationSharing": false,
-              "enableSyntaxHighlightLanguageDetection": true
-            },
-            "features": {
-              "feature_pinning": true,
-              "feature_custom_themes": true
-            }
-          }
-          EOF
-          echo "Created ./element-web/webapp/config.json"
-          cat ./element-web/webapp/config.json
-
-      - name: Upload Artifact
-        uses: https://code.forgejo.org/actions/upload-artifact@v3
-        with:
-          name: element-web
-          path: ./element-web/webapp/
-          retention-days: 14
-
-      - name: Install Wrangler
-        run: npm install --save-dev wrangler@latest
-
-      - name: Deploy to Cloudflare Pages (Production)
-        if: github.ref == 'refs/heads/main' && vars.CLOUDFLARE_PROJECT_NAME != ''
-        uses: https://github.com/cloudflare/wrangler-action@v3
-        with:
-          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
-          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
-          command: pages deploy ./element-web/webapp --branch="main" --commit-dirty=true --project-name="${{ vars.CLOUDFLARE_PROJECT_NAME }}-element"
-
-      - name: Deploy to Cloudflare Pages (Preview)
-        if: github.ref != 'refs/heads/main' && vars.CLOUDFLARE_PROJECT_NAME != ''
-        uses: https://github.com/cloudflare/wrangler-action@v3
-        with:
-          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
-          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
-          command: pages deploy ./element-web/webapp --branch="${{ github.head_ref || github.ref_name }}" --commit-dirty=true --project-name="${{ vars.CLOUDFLARE_PROJECT_NAME }}-element"

.forgejo/workflows/release-image.yml

@@ -1,25 +1,23 @@
 name: Release Docker Image
-concurrency:
+concurrency: 
   group: "release-image-${{ github.ref }}"
 
 on:
   pull_request:
   push:
     paths-ignore:
-      - "*.md"
+      - '.gitlab-ci.yml'
-      - "**/*.md"
+      - '.gitignore'
-      - ".gitlab-ci.yml"
+      - 'renovate.json'
-      - ".gitignore"
+      - 'debian/**'
-      - "renovate.json"
+      - 'docker/**'
-      - "debian/**"
-      - "docker/**"
-      - "docs/**"
   # Allows you to run this workflow manually from the Actions tab
   workflow_dispatch:
 
 env:
-  BUILTIN_REGISTRY: forgejo.ellis.link
+    BUILTIN_REGISTRY: forgejo.ellis.link
-  BUILTIN_REGISTRY_ENABLED: "${{ ((vars.BUILTIN_REGISTRY_USER && secrets.BUILTIN_REGISTRY_PASSWORD) || (github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork == false)) && 'true' || 'false' }}"
+    BUILTIN_REGISTRY_ENABLED: "${{ ((vars.BUILTIN_REGISTRY_USER && secrets.BUILTIN_REGISTRY_PASSWORD) || (github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork == false)) && 'true' || 'false' }}"
+
 
 jobs:
   define-variables:
@@ -38,7 +36,7 @@ jobs:
           script: |
             const githubRepo = '${{ github.repository }}'.toLowerCase()
             const repoId = githubRepo.split('/')[1]
-
+            
             core.setOutput('github_repository', githubRepo)
             const builtinImage = '${{ env.BUILTIN_REGISTRY }}/' + githubRepo
             let images = []
@@ -49,7 +47,7 @@ jobs:
             core.setOutput('images_list', images.join(","))
             const platforms = ['linux/amd64', 'linux/arm64']
             core.setOutput('build_matrix', JSON.stringify({
-              platform: platforms,
+              platform: platforms, 
               include: platforms.map(platform => { return {
                 platform,
                 slug: platform.replace('/', '-')
@@ -66,15 +64,22 @@ jobs:
       attestations: write
       id-token: write
     strategy:
-      matrix:
+      matrix: {
-        {
+        "include": [
-          "include":
+          {
-            [
+            "platform": "linux/amd64",
-              { "platform": "linux/amd64", "slug": "linux-amd64" },
+            "slug": "linux-amd64"
-              { "platform": "linux/arm64", "slug": "linux-arm64" },
+          },
-            ],
+          {
-          "platform": ["linux/amd64", "linux/arm64"],
+            "platform": "linux/arm64",
-        }
+            "slug": "linux-arm64"
+          }
+        ],
+        "platform": [
+          "linux/amd64",
+          "linux/arm64"
+        ]
+      }
     steps:
       - name: Echo strategy
         run: echo '${{ toJSON(fromJSON(needs.define-variables.outputs.build_matrix)) }}'
@@ -84,13 +89,7 @@ jobs:
         uses: actions/checkout@v4
         with:
           persist-credentials: false
-      - run: |
+      
-          if ! command -v rustup &> /dev/null ; then
-            curl --proto '=https' --tlsv1.2 --retry 10 --retry-connrefused -fsSL "https://sh.rustup.rs" | sh -s -- --default-toolchain none -y
-            echo "${CARGO_HOME:-$HOME/.cargo}/bin" >> $GITHUB_PATH
-          fi
-      - uses: https://github.com/cargo-bins/cargo-binstall@main
-      - run: cargo binstall timelord-cli@3.0.1
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v3
       - name: Set up QEMU
@@ -99,9 +98,9 @@ jobs:
       - name: Login to builtin registry
         uses: docker/login-action@v3
         with:
-          registry: ${{ env.BUILTIN_REGISTRY }}
+            registry: ${{ env.BUILTIN_REGISTRY }}
-          username: ${{ vars.BUILTIN_REGISTRY_USER || github.actor }}
+            username: ${{ vars.BUILTIN_REGISTRY_USER || github.actor }}
-          password: ${{ secrets.BUILTIN_REGISTRY_PASSWORD || secrets.GITHUB_TOKEN }}
+            password: ${{ secrets.BUILTIN_REGISTRY_PASSWORD || secrets.GITHUB_TOKEN }}
 
       # This step uses [docker/metadata-action](https://github.com/docker/metadata-action#about) to extract tags and labels that will be applied to the specified image. The `id` "meta" allows the output of this step to be referenced in a subsequent step. The `images` value provides the base name for the tags and labels.
       - name: Extract metadata (labels, annotations) for Docker
@@ -124,18 +123,6 @@ jobs:
           echo "COMMIT_SHORT_SHA=$calculatedSha" >> $GITHUB_ENV
       - name: Get Git commit timestamps
         run: echo "TIMESTAMP=$(git log -1 --pretty=%ct)" >> $GITHUB_ENV
-      - name: Set up timelord
-        uses: actions/cache/restore@v3
-        with:
-          path: /timelord/
-          key: timelord-v0 # Cache is already split per runner
-      - name: Run timelord to set timestamps
-        run: timelord sync --source-dir . --cache-dir /timelord/
-      - name: Save timelord
-        uses: actions/cache/save@v3
-        with:
-          path: /timelord/
-          key: timelord-v0
       - name: Build and push Docker image by digest
         id: build
         uses: docker/build-push-action@v6
@@ -159,7 +146,7 @@ jobs:
         run: |
           mkdir -p /tmp/digests
           digest="${{ steps.build.outputs.digest }}"
-          touch "/tmp/digests/${digest#sha256:}"
+          touch "/tmp/digests/${digest#sha256:}"          
 
       - name: Upload digest
         uses: forgejo/upload-artifact@v4
@@ -168,7 +155,7 @@ jobs:
           path: /tmp/digests/*
           if-no-files-found: error
           retention-days: 1
-
+  
   merge:
     runs-on: dind
     container: ghcr.io/catthehacker/ubuntu:act-latest
@@ -184,9 +171,9 @@ jobs:
       - name: Login to builtin registry
         uses: docker/login-action@v3
         with:
-          registry: ${{ env.BUILTIN_REGISTRY }}
+            registry: ${{ env.BUILTIN_REGISTRY }}
-          username: ${{ vars.BUILTIN_REGISTRY_USER || github.actor }}
+            username: ${{ vars.BUILTIN_REGISTRY_USER || github.actor }}
-          password: ${{ secrets.BUILTIN_REGISTRY_PASSWORD || secrets.GITHUB_TOKEN }}
+            password: ${{ secrets.BUILTIN_REGISTRY_PASSWORD || secrets.GITHUB_TOKEN }}
 
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v3
@@ -205,7 +192,7 @@ jobs:
           images: ${{needs.define-variables.outputs.images}}
           # default labels & annotations: https://github.com/docker/metadata-action/blob/master/src/meta.ts#L509
         env:
-          DOCKER_METADATA_ANNOTATIONS_LEVELS: index
+          DOCKER_METADATA_ANNOTATIONS_LEVELS: index         
 
       - name: Create manifest list and push
         working-directory: /tmp/digests

CODE_OF_CONDUCT.md

@@ -1,3 +1,4 @@
+
 # Contributor Covenant Code of Conduct
 
 ## Our Pledge
@@ -59,7 +60,8 @@ representative at an online or offline event.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement over Matrix at [#continuwuity:continuwuity.org](https://matrix.to/#/#continuwuity:continuwuity.org) or email at <tom@tcpip.uk>, <jade@continuwuity.org> and <nex@continuwuity.org> respectively.
+reported to the community leaders responsible for enforcement over email at
+<strawberry@puppygock.gay> or over Matrix at @strawberry:puppygock.gay.
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the

CONTRIBUTING.md

@@ -4,7 +4,7 @@ This page is for about contributing to conduwuit. The
 [development](./development.md) page may be of interest for you as well.
 
 If you would like to work on an [issue][issues] that is not assigned, preferably
-ask in the Matrix room first at [#continuwuity:continuwuity.org][continuwuity-matrix],
+ask in the Matrix room first at [#conduwuit:puppygock.gay][conduwuit-matrix],
 and comment on it.
 
 ### Linting and Formatting
@@ -23,9 +23,9 @@ suggestion, allow the lint and mention that in a comment.
 
 ### Running CI tests locally
 
-continuwuity's CI for tests, linting, formatting, audit, etc use
+conduwuit's CI for tests, linting, formatting, audit, etc use
 [`engage`][engage]. engage can be installed from nixpkgs or `cargo install
-engage`. continuwuity's Nix flake devshell has the nixpkgs engage with `direnv`.
+engage`. conduwuit's Nix flake devshell has the nixpkgs engage with `direnv`.
 Use `engage --help` for more usage details.
 
 To test, format, lint, etc that CI would do, install engage, allow the `.envrc`
@@ -111,28 +111,33 @@ applies here.
 
 ### Creating pull requests
 
-Please try to keep contributions to the Forgejo Instance. While the mirrors of continuwuity
+Please try to keep contributions to the GitHub. While the mirrors of conduwuit
-allow for pull/merge requests, there is no guarantee the maintainers will see them in a timely
+allow for pull/merge requests, there is no guarantee I will see them in a timely
 manner. Additionally, please mark WIP or unfinished or incomplete PRs as drafts.
-This prevents us from having to ping once in a while to double check the status
+This prevents me from having to ping once in a while to double check the status
 of it, especially when the CI completed successfully and everything so it
 *looks* done.
 
+If you open a pull request on one of the mirrors, it is your responsibility to
+inform me about its existence. In the future I may try to solve this with more
+repo bots in the conduwuit Matrix room. There is no mailing list or email-patch
+support on the sr.ht mirror, but if you'd like to email me a git patch you can
+do so at `strawberry@puppygock.gay`.
 
 Direct all PRs/MRs to the `main` branch.
 
 By sending a pull request or patch, you are agreeing that your changes are
 allowed to be licenced under the Apache-2.0 licence and all of your conduct is
-in line with the Contributor's Covenant, and continuwuity's Code of Conduct.
+in line with the Contributor's Covenant, and conduwuit's Code of Conduct.
 
 Contribution by users who violate either of these code of conducts will not have
 their contributions accepted. This includes users who have been banned from
-continuwuityMatrix rooms for Code of Conduct violations.
+conduwuit Matrix rooms for Code of Conduct violations.
 
-[issues]: https://forgejo.ellis.link/continuwuation/continuwuity/issues
+[issues]: https://github.com/girlbossceo/conduwuit/issues
-[continuwuity-matrix]: https://matrix.to/#/#continuwuity:continuwuity.org
+[conduwuit-matrix]: https://matrix.to/#/#conduwuit:puppygock.gay
 [complement]: https://github.com/matrix-org/complement/
-[engage.toml]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/engage.toml
+[engage.toml]: https://github.com/girlbossceo/conduwuit/blob/main/engage.toml
 [engage]: https://charles.page.computer.surgery/engage/
 [sytest]: https://github.com/matrix-org/sytest/
 [cargo-deb]: https://github.com/kornelski/cargo-deb
@@ -141,4 +146,4 @@ continuwuityMatrix rooms for Code of Conduct violations.
 [cargo-audit]: https://github.com/RustSec/rustsec/tree/main/cargo-audit
 [direnv]: https://direnv.net/
 [mdbook]: https://rust-lang.github.io/mdBook/
-[documentation.yml]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/.forgejo/workflows/documentation.yml
+[documentation.yml]: https://github.com/girlbossceo/conduwuit/blob/main/.github/workflows/documentation.yml

Cargo.lock

@@ -725,7 +725,7 @@ dependencies = [
 
 [[package]]
 name = "conduwuit"
-version = "0.5.0-rc.5"
+version = "0.5.0"
 dependencies = [
  "clap",
  "conduwuit_admin",
@@ -754,7 +754,7 @@ dependencies = [
 
 [[package]]
 name = "conduwuit_admin"
-version = "0.5.0-rc.5"
+version = "0.5.0"
 dependencies = [
  "clap",
  "conduwuit_api",
@@ -775,7 +775,7 @@ dependencies = [
 
 [[package]]
 name = "conduwuit_api"
-version = "0.5.0-rc.5"
+version = "0.5.0"
 dependencies = [
  "async-trait",
  "axum",
@@ -807,7 +807,7 @@ dependencies = [
 
 [[package]]
 name = "conduwuit_core"
-version = "0.5.0-rc.5"
+version = "0.5.0"
 dependencies = [
  "argon2",
  "arrayvec",
@@ -865,7 +865,7 @@ dependencies = [
 
 [[package]]
 name = "conduwuit_database"
-version = "0.5.0-rc.5"
+version = "0.5.0"
 dependencies = [
  "async-channel",
  "conduwuit_core",
@@ -883,7 +883,7 @@ dependencies = [
 
 [[package]]
 name = "conduwuit_macros"
-version = "0.5.0-rc.5"
+version = "0.5.0"
 dependencies = [
  "itertools 0.14.0",
  "proc-macro2",
@@ -893,7 +893,7 @@ dependencies = [
 
 [[package]]
 name = "conduwuit_router"
-version = "0.5.0-rc.5"
+version = "0.5.0"
 dependencies = [
  "axum",
  "axum-client-ip",
@@ -926,7 +926,7 @@ dependencies = [
 
 [[package]]
 name = "conduwuit_service"
-version = "0.5.0-rc.5"
+version = "0.5.0"
 dependencies = [
  "async-trait",
  "base64 0.22.1",
@@ -3652,7 +3652,7 @@ dependencies = [
 [[package]]
 name = "ruma"
 version = "0.10.1"
-source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=d6870a7fb7f6cccff63f7fd0ff6c581bad80e983#d6870a7fb7f6cccff63f7fd0ff6c581bad80e983"
+source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=920148dca1076454ca0ca5d43b5ce1aa708381d4#920148dca1076454ca0ca5d43b5ce1aa708381d4"
 dependencies = [
  "assign",
  "js_int",
@@ -3672,7 +3672,7 @@ dependencies = [
 [[package]]
 name = "ruma-appservice-api"
 version = "0.10.0"
-source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=d6870a7fb7f6cccff63f7fd0ff6c581bad80e983#d6870a7fb7f6cccff63f7fd0ff6c581bad80e983"
+source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=920148dca1076454ca0ca5d43b5ce1aa708381d4#920148dca1076454ca0ca5d43b5ce1aa708381d4"
 dependencies = [
  "js_int",
  "ruma-common",
@@ -3684,7 +3684,7 @@ dependencies = [
 [[package]]
 name = "ruma-client-api"
 version = "0.18.0"
-source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=d6870a7fb7f6cccff63f7fd0ff6c581bad80e983#d6870a7fb7f6cccff63f7fd0ff6c581bad80e983"
+source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=920148dca1076454ca0ca5d43b5ce1aa708381d4#920148dca1076454ca0ca5d43b5ce1aa708381d4"
 dependencies = [
  "as_variant",
  "assign",
@@ -3707,7 +3707,7 @@ dependencies = [
 [[package]]
 name = "ruma-common"
 version = "0.13.0"
-source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=d6870a7fb7f6cccff63f7fd0ff6c581bad80e983#d6870a7fb7f6cccff63f7fd0ff6c581bad80e983"
+source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=920148dca1076454ca0ca5d43b5ce1aa708381d4#920148dca1076454ca0ca5d43b5ce1aa708381d4"
 dependencies = [
  "as_variant",
  "base64 0.22.1",
@@ -3739,7 +3739,7 @@ dependencies = [
 [[package]]
 name = "ruma-events"
 version = "0.28.1"
-source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=d6870a7fb7f6cccff63f7fd0ff6c581bad80e983#d6870a7fb7f6cccff63f7fd0ff6c581bad80e983"
+source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=920148dca1076454ca0ca5d43b5ce1aa708381d4#920148dca1076454ca0ca5d43b5ce1aa708381d4"
 dependencies = [
  "as_variant",
  "indexmap 2.8.0",
@@ -3764,7 +3764,7 @@ dependencies = [
 [[package]]
 name = "ruma-federation-api"
 version = "0.9.0"
-source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=d6870a7fb7f6cccff63f7fd0ff6c581bad80e983#d6870a7fb7f6cccff63f7fd0ff6c581bad80e983"
+source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=920148dca1076454ca0ca5d43b5ce1aa708381d4#920148dca1076454ca0ca5d43b5ce1aa708381d4"
 dependencies = [
  "bytes",
  "headers",
@@ -3786,7 +3786,7 @@ dependencies = [
 [[package]]
 name = "ruma-identifiers-validation"
 version = "0.9.5"
-source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=d6870a7fb7f6cccff63f7fd0ff6c581bad80e983#d6870a7fb7f6cccff63f7fd0ff6c581bad80e983"
+source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=920148dca1076454ca0ca5d43b5ce1aa708381d4#920148dca1076454ca0ca5d43b5ce1aa708381d4"
 dependencies = [
  "js_int",
  "thiserror 2.0.12",
@@ -3795,7 +3795,7 @@ dependencies = [
 [[package]]
 name = "ruma-identity-service-api"
 version = "0.9.0"
-source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=d6870a7fb7f6cccff63f7fd0ff6c581bad80e983#d6870a7fb7f6cccff63f7fd0ff6c581bad80e983"
+source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=920148dca1076454ca0ca5d43b5ce1aa708381d4#920148dca1076454ca0ca5d43b5ce1aa708381d4"
 dependencies = [
  "js_int",
  "ruma-common",
@@ -3805,7 +3805,7 @@ dependencies = [
 [[package]]
 name = "ruma-macros"
 version = "0.13.0"
-source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=d6870a7fb7f6cccff63f7fd0ff6c581bad80e983#d6870a7fb7f6cccff63f7fd0ff6c581bad80e983"
+source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=920148dca1076454ca0ca5d43b5ce1aa708381d4#920148dca1076454ca0ca5d43b5ce1aa708381d4"
 dependencies = [
  "cfg-if",
  "proc-macro-crate",
@@ -3820,7 +3820,7 @@ dependencies = [
 [[package]]
 name = "ruma-push-gateway-api"
 version = "0.9.0"
-source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=d6870a7fb7f6cccff63f7fd0ff6c581bad80e983#d6870a7fb7f6cccff63f7fd0ff6c581bad80e983"
+source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=920148dca1076454ca0ca5d43b5ce1aa708381d4#920148dca1076454ca0ca5d43b5ce1aa708381d4"
 dependencies = [
  "js_int",
  "ruma-common",
@@ -3832,7 +3832,7 @@ dependencies = [
 [[package]]
 name = "ruma-signatures"
 version = "0.15.0"
-source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=d6870a7fb7f6cccff63f7fd0ff6c581bad80e983#d6870a7fb7f6cccff63f7fd0ff6c581bad80e983"
+source = "git+https://forgejo.ellis.link/continuwuation/ruwuma?rev=920148dca1076454ca0ca5d43b5ce1aa708381d4#920148dca1076454ca0ca5d43b5ce1aa708381d4"
 dependencies = [
  "base64 0.22.1",
  "ed25519-dalek",

Cargo.toml

@@ -21,7 +21,7 @@ license = "Apache-2.0"
 readme = "README.md"
 repository = "https://forgejo.ellis.link/continuwuation/continuwuity"
 rust-version = "1.86.0"
-version = "0.5.0-rc.5"
+version = "0.5.0"
 
 [workspace.metadata.crane]
 name = "conduwuit"
@@ -350,7 +350,7 @@ version = "0.1.2"
 [workspace.dependencies.ruma]
 git = "https://forgejo.ellis.link/continuwuation/ruwuma"
 #branch = "conduwuit-changes"
-rev = "d6870a7fb7f6cccff63f7fd0ff6c581bad80e983"
+rev = "920148dca1076454ca0ca5d43b5ce1aa708381d4"
 features = [
     "compat",
     "rand",

README.md

@@ -46,9 +46,8 @@ Continuwuity aims to:
 
 ### Can I try it out?
 
-Check out the [documentation](introduction) for installation instructions.
+Not right now. We've still got work to do!
 
-There are currently no open registration Continuwuity instances available.
 
 ### What are we working on?
 
@@ -106,7 +105,7 @@ When incorporating code from other forks:
 
 #### Contact
 
-Join our [Matrix room](https://matrix.to/#/#continuwuity:continuwuity.org) and [space](https://matrix.to/#/#space:continuwuity.org) to chat with us about the project!
+<!-- TODO: contact details -->
 
 <!-- ANCHOR_END: footer -->
 

alpine/APKBUILD

@@ -1,63 +0,0 @@
-# Contributor: magmaus3 <maia@magmaus3.eu.org>
-# Maintainer: magmaus3 <maia@magmaus3.eu.org>
-pkgname=continuwuity
-
-# abuild doesn't like the format of v0.5.0-rc.5, so i had to change it 
-# see https://wiki.alpinelinux.org/wiki/Package_policies
-pkgver=0.5.0_rc5
-pkgrel=0
-pkgdesc="a continuwuation of a very cool, featureful fork of conduit"
-url="https://continuwuity.org/"
-arch="all"
-license="Apache-2.0"
-depends="liburing"
-
-# cargo version on alpine v3.21 is too old to use the 2024 edition
-# i recommend either building everything on edge, or adding
-# the edge repo as a tag
-makedepends="cargo liburing-dev clang-dev linux-headers"
-checkdepends=""
-install="$pkgname.pre-install"
-subpackages="$pkgname-openrc"
-source="https://forgejo.ellis.link/continuwuation/continuwuity/archive/v0.5.0-rc.5.tar.gz
-continuwuity.initd
-continuwuity.confd
-"
-builddir="$srcdir/continuwuity"
-options="net !check"
-
-prepare() {
-	default_prepare
-	cd $srcdir/continuwuity
-
-    # add the default database path to the config (commented out)
-    cat conduwuit-example.toml \
-        | sed '/#database_path/ s:$: "/var/lib/continuwuity":' \
-        > "$srcdir"/continuwuity.toml
-
-	cargo fetch --target="$CTARGET" --locked
-}
-
-build() {
-	cargo build --frozen --release --all-features
-}
-
-check() {
-	# TODO: make sure the tests work
-	#cargo test --frozen
-    return
-}
-
-package() {
-	cd $srcdir	
-	install -Dm755 continuwuity/target/release/conduwuit "$pkgdir"/usr/bin/continuwuity
-	install -Dm644 "$srcdir"/continuwuity.toml -t "$pkgdir"/etc/continuwuity
-	install -Dm755 "$srcdir"/continuwuity.initd "$pkgdir"/etc/init.d/continuwuity
-	install -Dm644 "$srcdir"/continuwuity.confd "$pkgdir"/etc/conf.d/continuwuity
-}
-
-sha512sums="
-66f6da5e98b6f7bb8c1082500101d5c87b1b79955c139b44c6ef5123919fb05feb0dffc669a3af1bc8d571ddb9f3576660f08dc10a6b19eab6db9e391175436a  v0.5.0-rc.5.tar.gz
-0482674be24740496d70da256d4121c5a5e3b749f2445d2bbe0e8991f1449de052724f8427da21a6f55574bc53eac9ca1e47e5012b4c13049b2b39044734d80d  continuwuity.initd
-38e2576278b450d16ba804dd8f4a128f18cd793e6c3ce55aedee1e186905755b31ee23baaa6586b1ab0e25a1f29bf1ea86bfaae4185b0cb1a29203726a199426  continuwuity.confd
-"

alpine/README.md

@@ -1,7 +0,0 @@
-# building
-
-1. [set up your build
-   environment](https://wiki.alpinelinux.org/wiki/Include:Setup_your_system_and_account_for_building_packages)
-   
-2. run `abuild` (or `abuild -K` if you want to keep the source directory to make
-   rebuilding faster)

alpine/continuwuity.confd

@@ -1,3 +0,0 @@
-supervisor=supervise-daemon
-export CONTINUWUITY_CONFIG=/etc/continuwuity/continuwuity.toml
-

alpine/continuwuity.initd

@@ -1,19 +0,0 @@
-#!/sbin/openrc-run
-
-command="/usr/bin/continuwuity"
-command_user="continuwuity:continuwuity"
-command_args="--config ${CONTINUWUITY_CONFIG=/etc/continuwuity/continuwuity.toml}"
-command_background=true
-pidfile="/run/$RC_SVCNAME.pid"
-
-output_log="/var/log/continuwuity.log"
-error_log="/var/log/continuwuity.log"
-
-depend() {
-	need net
-}
-
-start_pre() {
-	checkpath -d -m 0755 -o "$command_user" /var/lib/continuwuity
-	checkpath -f -m 0644 -o "$command_user" "$output_log"
-}

alpine/continuwuity.pre-install

@@ -1,4 +0,0 @@
-#!/bin/sh
-addgroup -S continuwuity 2>/dev/null
-adduser -S -D -H -h /var/lib/continuwuity -s /sbin/nologin -G continuwuity -g continuwuity continuwuity 2>/dev/null
-exit 0

conduwuit-example.toml

@@ -112,12 +112,6 @@
 #
 #new_user_displayname_suffix = "🏳️‍⚧️"
 
-# If enabled, conduwuit will send a simple GET request periodically to
-# `https://continuwuity.org/.well-known/continuwuity/announcements` for any new
-# announcements or major updates. This is not an update check endpoint.
-#
-#allow_announcements_check = true
-
 # Set this to any float value to multiply conduwuit's in-memory LRU caches
 # with such as "auth_chain_cache_capacity".
 #
@@ -966,10 +960,10 @@
 #
 #rocksdb_compaction_ioprio_idle = true
 
-# Enables RocksDB compaction. You should never ever have to set this
+# Disables RocksDB compaction. You should never ever have to set this
-# option to false. If you for some reason find yourself needing to use
+# option to true. If you for some reason find yourself needing to use this
-# this option as part of troubleshooting or a bug, please reach out to us
+# option as part of troubleshooting or a bug, please reach out to us in
-# in the conduwuit Matrix room with information and details.
+# the conduwuit Matrix room with information and details.
 #
 # Disabling compaction will lead to a significantly bloated and
 # explosively large database, gradually poor performance, unnecessarily
@@ -1182,34 +1176,6 @@
 #
 #prune_missing_media = false
 
-# List of forbidden server names via regex patterns that we will block
-# incoming AND outgoing federation with, and block client room joins /
-# remote user invites.
-#
-# Note that your messages can still make it to forbidden servers through
-# backfilling. Events we receive from forbidden servers via backfill
-# from servers we *do* federate with will be stored in the database.
-#
-# This check is applied on the room ID, room alias, sender server name,
-# sender user's server name, inbound federation X-Matrix origin, and
-# outbound federation handler.
-#
-# You can set this to ["*"] to block all servers by default, and then
-# use `allowed_remote_server_names` to allow only specific servers.
-#
-# example: ["badserver\\.tld$", "badphrase", "19dollarfortnitecards"]
-#
-#forbidden_remote_server_names = []
-
-# List of allowed server names via regex patterns that we will allow,
-# regardless of if they match `forbidden_remote_server_names`.
-#
-# This option has no effect if `forbidden_remote_server_names` is empty.
-#
-# example: ["goodserver\\.tld$", "goodphrase"]
-#
-#allowed_remote_server_names = []
-
 # Vector list of regex patterns of server names that conduwuit will refuse
 # to download remote media from.
 #
@@ -1217,6 +1183,20 @@
 #
 #prevent_media_downloads_from = []
 
+# List of forbidden server names via regex patterns that we will block
+# incoming AND outgoing federation with, and block client room joins /
+# remote user invites.
+#
+# This check is applied on the room ID, room alias, sender server name,
+# sender user's server name, inbound federation X-Matrix origin, and
+# outbound federation handler.
+#
+# Basically "global" ACLs.
+#
+# example: ["badserver\.tld$", "badphrase", "19dollarfortnitecards"]
+#
+#forbidden_remote_server_names = []
+
 # List of forbidden server names via regex patterns that we will block all
 # outgoing federated room directory requests for. Useful for preventing
 # our users from wandering into bad servers or spaces.
@@ -1225,29 +1205,6 @@
 #
 #forbidden_remote_room_directory_server_names = []
 
-# Vector list of regex patterns of server names that conduwuit will not
-# send messages to the client from.
-#
-# Note that there is no way for clients to receive messages once a server
-# has become unignored without doing a full sync. This is a protocol
-# limitation with the current sync protocols. This means this is somewhat
-# of a nuclear option.
-#
-# example: ["reallybadserver\.tld$", "reallybadphrase",
-# "69dollarfortnitecards"]
-#
-#ignore_messages_from_server_names = []
-
-# Send messages from users that the user has ignored to the client.
-#
-# There is no way for clients to receive messages sent while a user was
-# ignored without doing a full sync. This is a protocol limitation with
-# the current sync protocols. Disabling this option will move
-# responsibility of ignoring messages to the client, which can avoid this
-# limitation.
-#
-#send_messages_from_ignored_users_to_client = false
-
 # Vector list of IPv4 and IPv6 CIDR ranges / subnets *in quotes* that you
 # do not want conduwuit to send outbound requests to. Defaults to
 # RFC1918, unroutable, loopback, multicast, and testnet addresses for

debian/conduwuit.service

@@ -3,7 +3,7 @@ Description=conduwuit Matrix homeserver
 Wants=network-online.target
 After=network-online.target
 Alias=matrix-conduwuit.service
-Documentation=https://continuwuity.org/
+Documentation=https://conduwuit.puppyirl.gay/
 
 [Service]
 DynamicUser=yes

docker/Dockerfile

@@ -44,11 +44,15 @@ ENV CARGO_SBOM_VERSION=0.9.1
 # renovate: datasource=crate depName=lddtree
 ENV LDDTREE_VERSION=0.3.7
 
+# renovate: datasource=crate depName=timelord-cli
+ENV TIMELORD_VERSION=3.0.1
+
 # Install unpackaged tools
 RUN <<EOF
     curl --retry 5 -L --proto '=https' --tlsv1.2 -sSf https://raw.githubusercontent.com/cargo-bins/cargo-binstall/main/install-from-binstall-release.sh | bash
     cargo binstall --no-confirm cargo-sbom --version $CARGO_SBOM_VERSION
     cargo binstall --no-confirm lddtree --version $LDDTREE_VERSION
+    cargo binstall --no-confirm timelord-cli --version $TIMELORD_VERSION
 EOF
 
 # Set up xx (cross-compilation scripts)
@@ -130,6 +134,10 @@ RUN xx-cargo --print-target-triple
 # Get source
 COPY . .
 
+# Timelord sync
+RUN --mount=type=cache,target=/timelord/ \
+    timelord sync --source-dir . --cache-dir /timelord/
+
 # Build the binary
 RUN --mount=type=cache,target=/usr/local/cargo/registry \
     --mount=type=cache,target=/usr/local/cargo/git/db \

docs/SUMMARY.md

@@ -19,4 +19,4 @@
   - [Contributing](contributing.md)
   - [Testing](development/testing.md)
   - [Hot Reloading ("Live" Development)](development/hot_reload.md)
-- [Community (and Guidelines)](community.md)
+- [conduwuit Community Code of Conduct](conduwuit_coc.md)

docs/appservices.md

@@ -3,8 +3,8 @@
 ## Getting help
 
 If you run into any problems while setting up an Appservice: ask us in
-[#continuwuity:continuwuity.org](https://matrix.to/#/#continuwuity:continuwuity.org) or
+[#conduwuit:puppygock.gay](https://matrix.to/#/#conduwuit:puppygock.gay) or
-[open an issue on Forgejo](https://forgejo.ellis.link/continuwuation/continuwuity/issues/new).
+[open an issue on GitHub](https://github.com/girlbossceo/conduwuit/issues/new).
 
 ## Set up the appservice - general instructions
 
@@ -14,7 +14,7 @@ later starting it.
 
 At some point the appservice guide should ask you to add a registration yaml
 file to the homeserver. In Synapse you would do this by adding the path to the
-homeserver.yaml, but in Continuwuity you can do this from within Matrix:
+homeserver.yaml, but in conduwuit you can do this from within Matrix:
 
 First, go into the `#admins` room of your homeserver. The first person that
 registered on the homeserver automatically joins it. Then send a message into
@@ -37,9 +37,9 @@ You can confirm it worked by sending a message like this:
 
 The server bot should answer with `Appservices (1): your-bridge`
 
-Then you are done. Continuwuity will send messages to the appservices and the
+Then you are done. conduwuit will send messages to the appservices and the
 appservice can send requests to the homeserver. You don't need to restart
-Continuwuity, but if it doesn't work, restarting while the appservice is running
+conduwuit, but if it doesn't work, restarting while the appservice is running
 could help.
 
 ## Appservice-specific instructions

docs/community.md

@@ -1,139 +0,0 @@
-# Continuwuity Community Guidelines
-
-Welcome to the Continuwuity commuwunity! We're excited to have you here. Continuwuity is a
-continuation of the conduwuit homeserver, which in turn is a hard-fork of the Conduit homeserver,
-aimed at making Matrix more accessible and inclusive for everyone.
-
-This space is dedicated to fostering a positive, supportive, and welcoming environment for everyone.
-These guidelines apply to all Continuwuity spaces, including our Matrix rooms and any other
-community channels that reference them. We've written these guidelines to help us all create an
-environment where everyone feels safe and respected.
-
-For code and contribution guidelines, please refer to the
-[Contributor's Covenant](https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CODE_OF_CONDUCT.md).
-Below are additional guidelines specific to the Continuwuity community.
-
-## Our Values and Expected Behaviors
-
-We strive to create a community based on mutual respect, collaboration, and inclusivity. We expect
-all members to:
-
-1. **Be Respectful and Inclusive**: Treat everyone with respect. We're committed to a community
-   where everyone feels safe, regardless of background, identity, or experience. Discrimination,
-   harassment, or hate speech won't be tolerated. Remember that each person experiences the world
-   differently; share your own perspective and be open to learning about others'.
-
-2. **Be Positive and Constructive**: Engage in discussions constructively and support each other.
-   If you feel angry or frustrated, take a break before participating. Approach disagreements with
-   the goal of understanding, not winning. Focus on the issue, not the person.
-
-3. **Communicate Clearly and Kindly**: Our community includes neurodivergent individuals and those
-   who may not appreciate sarcasm or subtlety. Communicate clearly and kindly. Avoid ambiguity and
-   ensure your messages can be easily understood by all. Avoid placing the burden of education on
-   marginalized groups; please make an effort to look into your questions before asking others for
-   detailed explanations.
-
-4. **Be Open to Improving Inclusivity**: Actively participate in making our community more inclusive.
-   Report behaviour that contradicts these guidelines (see Reporting and Enforcement below) and be
-   open to constructive feedback aimed at improving our community. Understand that discussing
-   negative experiences can be emotionally taxing; focus on the message, not the tone.
-
-5. **Commit to Our Values**: Building an inclusive community requires ongoing effort from everyone.
-   Recognise that addressing bias and discrimination is a continuous process that needs commitment
-   and action from all members.
-
-## Unacceptable Behaviors
-
-To ensure everyone feels safe and welcome, the following behaviors are considered unacceptable
-within the Continuwuity community:
-
-* **Harassment and Discrimination**: Avoid offensive comments related to background, family status,
-  gender, gender identity or expression, marital status, sex, sexual orientation, native language,
-  age, ability, race and/or ethnicity, caste, national origin, socioeconomic status, religion,
-  geographic location, or any other dimension of diversity. Don't deliberately misgender someone or
-  question the legitimacy of their gender identity.
-
-* **Violence and Threats**: Do not engage in any form of violence or threats, including inciting
-  violence towards anyone or encouraging self-harm. Posting or threatening to post someone else's
-  personally identifying information ("doxxing") is also forbidden.
-
-* **Personal Attacks**: Disagreements happen, but they should never turn into personal attacks.
-  Don't insult, demean, or belittle others.
-
-* **Unwelcome Attention or Contact**: Avoid unwelcome sexual attention, inappropriate physical
-  contact (or simulation thereof), sexualized comments, jokes, or imagery.
-
-* **Disruption**: Do not engage in sustained disruption of discussions, events, or other
-  community activities.
-
-* **Bad Faith Actions**: Do not intentionally make false reports or otherwise abuse the reporting
-  process.
-
-This is not an exhaustive list. Any behaviour that makes others feel unsafe or unwelcome may be
-subject to enforcement action.
-
-## Matrix Community
-
-These Community Guidelines apply to the entire
-[Continuwuity Matrix Space](https://matrix.to/#/#space:continuwuity.org) and its rooms, including:
-
-### [#continuwuity:continuwuity.org](https://matrix.to/#/#continuwuity:continuwuity.org)
-
-This room is for support and discussions about Continuwuity. Ask questions, share insights, and help
-each other out while adhering to these guidelines.
-
-We ask that this room remain focused on the Continuwuity software specifically: the team are
-typically happy to engage in conversations about related subjects in the off-topic room.
-
-### [#offtopic:continuwuity.org](https://matrix.to/#/#offtopic:continuwuity.org)
-
-For off-topic community conversations about any subject. While this room allows for a wide range of
-topics, the same guidelines apply. Please keep discussions respectful and inclusive, and avoid
-divisive or stressful subjects like specific country/world politics unless handled with exceptional
-care and respect for diverse viewpoints.
-
-General topics, such as world events, are welcome as long as they follow the guidelines. If a member
-of the team asks for the conversation to end, please respect their decision.
-
-### [#dev:continuwuity.org](https://matrix.to/#/#dev:continuwuity.org)
-
-This room is dedicated to discussing active development of Continuwuity, including ongoing issues or
-code development. Collaboration here must follow these guidelines, and please consider raising
-[an issue](https://forgejo.ellis.link/continuwuation/continuwuity/issues) on the repository to help
-track progress.
-
-## Reporting and Enforcement
-
-We take these Community Guidelines seriously to protect our community members. If you witness or
-experience unacceptable behaviour, or have any other concerns, please report it.
-
-**How to Report:**
-
-* **Alert Moderators in the Room:** If you feel comfortable doing so, you can address the issue
-  publicly in the relevant room by mentioning the moderation bot, `@rock:continuwuity.org`, which
-  will immediately alert all available moderators.
-* **Direct Message:** If you're not comfortable raising the issue publicly, please send a direct
-  message (DM) to one of the room moderators.
-
-Reports will be handled with discretion. We will investigate promptly and thoroughly.
-
-**Enforcement Actions:**
-
-Anyone asked to stop unacceptable behaviour is expected to comply immediately. Failure to do so, or
-engaging in prohibited behaviour, may result in enforcement action. Moderators may take actions they
-deem appropriate, including but not limited to:
-
-1. **Warning**: A direct message or public warning identifying the violation and requesting
-   corrective action.
-2. **Temporary Mute**: Temporary restriction from participating in discussions for a specified
-   period.
-3. **Kick or Ban**: Removal from a room (kick) or the entire community space (ban). Egregious or
-   repeated violations may result in an immediate ban. Bans are typically permanent and reviewed
-   only in exceptional circumstances.
-
-Retaliation against those who report concerns in good faith will not be tolerated and will be
-subject to the same enforcement actions.
-
-Together, let's build and maintain a community where everyone feels valued, safe, and respected.
-
-— The Continuwuity Moderation Team

docs/conduwuit_coc.md

@@ -0,0 +1,93 @@
+# conduwuit Community Code of Conduct
+
+Welcome to the conduwuit community! We’re excited to have you here. conduwuit is
+a hard-fork of the Conduit homeserver, aimed at making Matrix more accessible
+and inclusive for everyone.
+
+This space is dedicated to fostering a positive, supportive, and inclusive
+environment for everyone. This Code of Conduct applies to all conduwuit spaces,
+including any further community rooms that reference this CoC. Here are our
+guidelines to help maintain the welcoming atmosphere that sets conduwuit apart.
+
+For the general foundational rules, please refer to the [Contributor's
+Covenant](https://github.com/girlbossceo/conduwuit/blob/main/CODE_OF_CONDUCT.md).
+Below are additional guidelines specific to the conduwuit community.
+
+## Our Values and Guidelines
+
+1. **Respect and Inclusivity**: We are committed to maintaining a community
+   where everyone feels safe and respected. Discrimination, harassment, or hate
+speech of any kind will not be tolerated. Recognise that each community member
+experiences the world differently based on their past experiences, background,
+and identity. Share your own experiences and be open to learning about others'
+diverse perspectives.
+
+2. **Positivity and Constructiveness**: Engage in constructive discussions and
+   support each other. If you feel angry, negative, or aggressive, take a break
+until you can participate in a positive and constructive manner. Process intense
+feelings with a friend or in a private setting before engaging in community
+conversations to help maintain a supportive and focused environment.
+
+3. **Clarity and Understanding**: Our community includes neurodivergent
+   individuals and those who may not appreciate sarcasm or subtlety. Communicate
+clearly and kindly, avoiding sarcasm and ensuring your messages are easily
+understood by all. Additionally, avoid putting the burden of education on
+marginalized groups by doing your own research before asking for explanations.
+
+4. **Be Open to Inclusivity**: Actively engage in conversations about making our
+   community more inclusive. Report discriminatory behavior to the moderators
+and be open to constructive feedback that aims to improve our community.
+Understand that discussing discrimination and negative experiences can be
+emotionally taxing, so focus on the message rather than critiquing the tone
+used.
+
+5. **Commit to Inclusivity**: Building an inclusive community requires time,
+   energy, and resources. Recognise that addressing discrimination and bias is
+an ongoing process that necessitates commitment and action from all community
+members.
+
+## Matrix Community
+
+This Code of Conduct applies to the entire [conduwuit Matrix
+Space](https://matrix.to/#/#conduwuit-space:puppygock.gay) and its rooms,
+including:
+
+### [#conduwuit:puppygock.gay](https://matrix.to/#/#conduwuit:puppygock.gay)
+
+This room is for support and discussions about conduwuit. Ask questions, share
+insights, and help each other out.
+
+### [#conduwuit-offtopic:girlboss.ceo](https://matrix.to/#/#conduwuit-offtopic:girlboss.ceo)
+
+For off-topic community conversations about any subject. While this room allows
+for a wide range of topics, the same CoC applies. Keep discussions respectful
+and inclusive, and avoid divisive subjects like country/world politics. General
+topics, such as world events, are welcome as long as they follow the CoC.
+
+### [#conduwuit-dev:puppygock.gay](https://matrix.to/#/#conduwuit-dev:puppygock.gay)
+
+This room is dedicated to discussing active development of conduwuit. Posting
+requires an elevated power level, which can be requested in one of the other
+rooms. Use this space to collaborate and innovate.
+
+## Enforcement
+
+We have a zero-tolerance policy for violations of this Code of Conduct. If
+someone’s behavior makes you uncomfortable, please report it to the moderators.
+Actions we may take include:
+
+1. **Warning**: A warning given directly in the room or via a private message
+   from the moderators, identifying the violation and requesting corrective
+action.
+2. **Temporary Mute**: Temporary restriction from participating in discussions
+   for a specified period to allow for reflection and cooling off.
+3. **Kick or Ban**: Egregious behavior may result in an immediate kick or ban to
+   protect other community members. Bans are considered permanent and will only
+be reversed in exceptional circumstances after proven good behavior.
+
+Please highlight issues directly in rooms when possible, but if you don't feel
+comfortable doing that, then please send a DM to one of the moderators directly.
+
+Together, let’s build a community where everyone feels valued and respected.
+
+— The conduwuit Moderation Team

docs/configuration.md

@@ -1,10 +1,10 @@
 # Configuration
 
-This chapter describes various ways to configure Continuwuity.
+This chapter describes various ways to configure conduwuit.
 
 ## Basics
 
-Continuwuity uses a config file for the majority of the settings, but also supports
+conduwuit uses a config file for the majority of the settings, but also supports
 setting individual config options via commandline.
 
 Please refer to the [example config
@@ -12,13 +12,13 @@ file](./configuration/examples.md#example-configuration) for all of those
 settings.
 
 The config file to use can be specified on the commandline when running
-Continuwuity by specifying the `-c`, `--config` flag. Alternatively, you can use
+conduwuit by specifying the `-c`, `--config` flag. Alternatively, you can use
 the environment variable `CONDUWUIT_CONFIG` to specify the config file to used.
 Conduit's environment variables are supported for backwards compatibility.
 
 ## Option commandline flag
 
-Continuwuity supports setting individual config options in TOML format from the
+conduwuit supports setting individual config options in TOML format from the
 `-O` / `--option` flag. For example, you can set your server name via `-O
 server_name=\"example.com\"`.
 
@@ -33,7 +33,7 @@ string. This does not apply to options that take booleans or numbers:
 
 ## Execute commandline flag
 
-Continuwuity supports running admin commands on startup using the commandline
+conduwuit supports running admin commands on startup using the commandline
 argument `--execute`. The most notable use for this is to create an admin user
 on first startup.
 

docs/deploying.md

@@ -1,3 +1,3 @@
 # Deploying
 
-This chapter describes various ways to deploy Continuwuity.
+This chapter describes various ways to deploy conduwuit.

docs/deploying/arch-linux.md

@@ -1,3 +1,15 @@
-# Continuwuity for Arch Linux
+# conduwuit for Arch Linux
 
-Continuwuity does not have any Arch Linux packages at this time.
+Currently conduwuit is only on the Arch User Repository (AUR).
+
+The conduwuit AUR packages are community maintained and are not maintained by
+conduwuit development team, but the AUR package maintainers are in the Matrix
+room. Please attempt to verify your AUR package's PKGBUILD file looks fine
+before asking for support.
+
+- [conduwuit](https://aur.archlinux.org/packages/conduwuit) - latest tagged
+conduwuit
+- [conduwuit-git](https://aur.archlinux.org/packages/conduwuit-git) - latest git
+conduwuit from `main` branch
+- [conduwuit-bin](https://aur.archlinux.org/packages/conduwuit-bin) - latest
+tagged conduwuit static binary

docs/deploying/docker-compose.for-traefik.yml

@@ -1,14 +1,13 @@
-# Continuwuity - Behind Traefik Reverse Proxy
+# conduwuit - Behind Traefik Reverse Proxy
 
 services:
   homeserver:
     ### If you already built the conduduwit image with 'docker build' or want to use the Docker Hub image,
     ### then you are ready to go.
-    image: forgejo.ellis.link/continuwuation/continuwuity:latest
+    image: girlbossceo/conduwuit:latest
     restart: unless-stopped
     volumes:
       - db:/var/lib/conduwuit
-      - /etc/resolv.conf:/etc/resolv.conf:ro # Use the host's DNS resolver rather than Docker's. 
       #- ./conduwuit.toml:/etc/conduwuit.toml
     networks:
       - proxy
@@ -36,14 +35,14 @@ services:
         server=your.server.name.example:443
         }
     #cpuset: "0-4" # Uncomment to limit to specific CPU cores
-    ulimits: # Continuwuity uses quite a few file descriptors, and on some systems it defaults to 1024, so you can tell docker to increase it
+    ulimits: # conduwuit uses quite a few file descriptors, and on some systems it defaults to 1024, so you can tell docker to increase it
       nofile:
         soft: 1048567
         hard: 1048567
 
     ### Uncomment if you want to use your own Element-Web App.
     ### Note: You need to provide a config.json for Element and you also need a second
-    ###       Domain or Subdomain for the communication between Element and Continuwuity
+    ###       Domain or Subdomain for the communication between Element and conduwuit
     ### Config-Docs: https://github.com/vector-im/element-web/blob/develop/docs/config.md
     # element-web:
     #     image: vectorim/element-web:latest

docs/deploying/docker-compose.override.yml

@@ -1,4 +1,4 @@
-# Continuwuity - Traefik Reverse Proxy Labels
+# conduwuit - Traefik Reverse Proxy Labels
 
 services:
   homeserver:
@@ -6,7 +6,7 @@ services:
       - "traefik.enable=true"
       - "traefik.docker.network=proxy"  # Change this to the name of your Traefik docker proxy network
 
-      - "traefik.http.routers.to-conduwuit.rule=Host(`<SUBDOMAIN>.<DOMAIN>`)"  # Change to the address on which Continuwuity is hosted
+      - "traefik.http.routers.to-conduwuit.rule=Host(`<SUBDOMAIN>.<DOMAIN>`)"  # Change to the address on which conduwuit is hosted
       - "traefik.http.routers.to-conduwuit.tls=true"
       - "traefik.http.routers.to-conduwuit.tls.certresolver=letsencrypt"
       - "traefik.http.routers.to-conduwuit.middlewares=cors-headers@docker"
@@ -16,7 +16,7 @@ services:
       - "traefik.http.middlewares.cors-headers.headers.accessControlAllowHeaders=Origin, X-Requested-With, Content-Type, Accept, Authorization"
       - "traefik.http.middlewares.cors-headers.headers.accessControlAllowMethods=GET, POST, PUT, DELETE, OPTIONS"
 
-      # If you want to have your account on <DOMAIN>, but host Continuwuity on a subdomain,
+      # If you want to have your account on <DOMAIN>, but host conduwuit on a subdomain,
       # you can let it only handle the well known file on that domain instead
       #- "traefik.http.routers.to-matrix-wellknown.rule=Host(`<DOMAIN>`) && PathPrefix(`/.well-known/matrix`)"
       #- "traefik.http.routers.to-matrix-wellknown.tls=true"

docs/deploying/docker-compose.with-caddy.yml

@@ -1,6 +1,6 @@
 services:
     caddy:
-    # This compose file uses caddy-docker-proxy as the reverse proxy for Continuwuity!
+    # This compose file uses caddy-docker-proxy as the reverse proxy for conduwuit!
     # For more info, visit https://github.com/lucaslorentz/caddy-docker-proxy
         image: lucaslorentz/caddy-docker-proxy:ci-alpine
         ports:
@@ -20,13 +20,12 @@ services:
             caddy.1_respond: /.well-known/matrix/client {"m.server":{"base_url":"https://matrix.example.com"},"m.homeserver":{"base_url":"https://matrix.example.com"},"org.matrix.msc3575.proxy":{"url":"https://matrix.example.com"}}
 
     homeserver:
-        ### If you already built the Continuwuity image with 'docker build' or want to use a registry image,
+        ### If you already built the conduwuit image with 'docker build' or want to use a registry image,
         ### then you are ready to go.
-        image: forgejo.ellis.link/continuwuation/continuwuity:latest
+        image: girlbossceo/conduwuit:latest
         restart: unless-stopped
         volumes:
             - db:/var/lib/conduwuit
-            - /etc/resolv.conf:/etc/resolv.conf:ro # Use the host's DNS resolver rather than Docker's. 
             #- ./conduwuit.toml:/etc/conduwuit.toml
         environment:
             CONDUWUIT_SERVER_NAME: example.com # EDIT THIS

docs/deploying/docker-compose.with-traefik.yml

@@ -1,14 +1,13 @@
-# Continuwuity - Behind Traefik Reverse Proxy
+# conduwuit - Behind Traefik Reverse Proxy
 
 services:
   homeserver:
-    ### If you already built the Continuwuity image with 'docker build' or want to use the Docker Hub image,
+    ### If you already built the conduwuit image with 'docker build' or want to use the Docker Hub image,
     ### then you are ready to go.
-    image: forgejo.ellis.link/continuwuation/continuwuity:latest
+    image: girlbossceo/conduwuit:latest
     restart: unless-stopped
     volumes:
       - db:/var/lib/conduwuit
-      - /etc/resolv.conf:/etc/resolv.conf:ro # Use the host's DNS resolver rather than Docker's. 
       #- ./conduwuit.toml:/etc/conduwuit.toml
     networks:
       - proxy
@@ -22,7 +21,7 @@ services:
       CONDUWUIT_PORT: 6167 # you need to match this with the traefik load balancer label if you're want to change it
       CONDUWUIT_DATABASE_PATH: /var/lib/conduwuit
       #CONDUWUIT_CONFIG: '/etc/conduit.toml' # Uncomment if you mapped config toml above
-      ### Uncomment and change values as desired, note that Continuwuity has plenty of config options, so you should check out the example example config too
+      ### Uncomment and change values as desired, note that conduwuit has plenty of config options, so you should check out the example example config too
       # Available levels are: error, warn, info, debug, trace - more info at: https://docs.rs/env_logger/*/env_logger/#enabling-logging
       # CONDUWUIT_LOG: info  # default is: "warn,state_res=warn"
       # CONDUWUIT_ALLOW_ENCRYPTION: 'true'
@@ -44,14 +43,14 @@ services:
           server=your.server.name.example:443
         }
     #cpuset: "0-4" # Uncomment to limit to specific CPU cores
-    ulimits: # Continuwuity uses quite a few file descriptors, and on some systems it defaults to 1024, so you can tell docker to increase it
+    ulimits: # conduwuit uses quite a few file descriptors, and on some systems it defaults to 1024, so you can tell docker to increase it
       nofile:
         soft: 1048567
         hard: 1048567
 
     ### Uncomment if you want to use your own Element-Web App.
     ### Note: You need to provide a config.json for Element and you also need a second
-    ###       Domain or Subdomain for the communication between Element and Continuwuity
+    ###       Domain or Subdomain for the communication between Element and conduwuit
     ### Config-Docs: https://github.com/vector-im/element-web/blob/develop/docs/config.md
     # element-web:
     #     image: vectorim/element-web:latest

docs/deploying/docker-compose.yml

@@ -1,10 +1,10 @@
-# Continuwuity
+# conduwuit
 
 services:
     homeserver:
-        ### If you already built the Continuwuity image with 'docker build' or want to use a registry image,
+        ### If you already built the conduwuit image with 'docker build' or want to use a registry image,
         ### then you are ready to go.
-        image: forgejo.ellis.link/continuwuation/continuwuity:latest
+        image: girlbossceo/conduwuit:latest
         restart: unless-stopped
         ports:
             - 8448:6167
@@ -28,7 +28,7 @@ services:
     #
     ### Uncomment if you want to use your own Element-Web App.
     ### Note: You need to provide a config.json for Element and you also need a second
-    ###       Domain or Subdomain for the communication between Element and Continuwuity
+    ###       Domain or Subdomain for the communication between Element and conduwuit
     ### Config-Docs: https://github.com/vector-im/element-web/blob/develop/docs/config.md
     # element-web:
     #     image: vectorim/element-web:latest

docs/deploying/docker.md

@@ -1,20 +1,31 @@
-# Continuwuity for Docker
+# conduwuit for Docker
 
 ## Docker
 
-To run Continuwuity with Docker you can either build the image yourself or pull it
+To run conduwuit with Docker you can either build the image yourself or pull it
 from a registry.
 
 ### Use a registry
 
-OCI images for Continuwuity are available in the registries listed below.
+OCI images for conduwuit are available in the registries listed below.
 
-| Registry        | Image                                                           | Notes                  |
+| Registry        | Image                                                           | Size                          | Notes                  |
-| --------------- | --------------------------------------------------------------- | -----------------------|
+| --------------- | --------------------------------------------------------------- | ----------------------------- | ---------------------- |
-| Forgejo Registry| [forgejo.ellis.link/continuwuation/continuwuity:latest][fj]     | Latest tagged image.   |
+| GitHub Registry | [ghcr.io/girlbossceo/conduwuit:latest][gh] | ![Image Size][shield-latest]  | Stable latest tagged image.          |
-| Forgejo Registry| [forgejo.ellis.link/continuwuation/continuwuity:main][fj]       | Main branch image.     |
+| GitLab Registry | [registry.gitlab.com/conduwuit/conduwuit:latest][gl] | ![Image Size][shield-latest]  | Stable latest tagged image.          |
+| Docker Hub      | [docker.io/girlbossceo/conduwuit:latest][dh]             | ![Image Size][shield-latest]  | Stable latest tagged image.          |
+| GitHub Registry | [ghcr.io/girlbossceo/conduwuit:main][gh]   | ![Image Size][shield-main]    | Stable main branch.   |
+| GitLab Registry | [registry.gitlab.com/conduwuit/conduwuit:main][gl]   | ![Image Size][shield-main]    | Stable main branch.   |
+| Docker Hub      | [docker.io/girlbossceo/conduwuit:main][dh]               | ![Image Size][shield-main]    | Stable main branch.   |
 
-[fj]: https://forgejo.ellis.link/continuwuation/-/packages/container/continuwuity
+[dh]: https://hub.docker.com/r/girlbossceo/conduwuit
+[gh]: https://github.com/girlbossceo/conduwuit/pkgs/container/conduwuit
+[gl]: https://gitlab.com/conduwuit/conduwuit/container_registry/6369729
+[shield-latest]: https://img.shields.io/docker/image-size/girlbossceo/conduwuit/latest
+[shield-main]: https://img.shields.io/docker/image-size/girlbossceo/conduwuit/main
+
+OCI image `.tar.gz` files are also hosted directly at when uploaded by CI with a
+commit hash/revision or a tagged release: <https://pup.systems/~strawberry/conduwuit/>
 
 Use
 
@@ -41,11 +52,11 @@ or you can use [docker compose](#docker-compose).
 The `-d` flag lets the container run in detached mode. You may supply an
 optional `conduwuit.toml` config file, the example config can be found
 [here](../configuration/examples.md). You can pass in different env vars to
-change config values on the fly. You can even configure Continuwuity completely by
+change config values on the fly. You can even configure conduwuit completely by
 using env vars. For an overview of possible values, please take a look at the
 [`docker-compose.yml`](docker-compose.yml) file.
 
-If you just want to test Continuwuity for a short time, you can use the `--rm`
+If you just want to test conduwuit for a short time, you can use the `--rm`
 flag, which will clean up everything related to your container after you stop
 it.
 
@@ -80,32 +91,32 @@ docker network create caddy
 After that, you can rename it so it matches `docker-compose.yml` and spin up the
 containers!
 
-Additional info about deploying Continuwuity can be found [here](generic.md).
+Additional info about deploying conduwuit can be found [here](generic.md).
 
 ### Build
 
-Official Continuwuity images are built using **Docker Buildx** and the Dockerfile found at [`docker/Dockerfile`][dockerfile-path]. This approach uses common Docker tooling and enables multi-platform builds efficiently.
+Official conduwuit images are built using Nix's
+[`buildLayeredImage`][nix-buildlayeredimage]. This ensures all OCI images are
+repeatable and reproducible by anyone, keeps the images lightweight, and can be
+built offline.
 
-The resulting images are broadly compatible with Docker and other container runtimes like Podman or containerd.
+This also ensures portability of our images because `buildLayeredImage` builds
+OCI images, not Docker images, and works with other container software.
 
-The images *do not contain a shell*. They contain only the Continuwuity binary, required libraries, TLS certificates and metadata. Please refer to the [`docker/Dockerfile`][dockerfile-path] for the specific details of the image composition.
+The OCI images are OS-less with only a very minimal environment of the `tini`
+init system, CA certificates, and the conduwuit binary. This does mean there is
+not a shell, but in theory you can get a shell by adding the necessary layers
+to the layered image. However it's very unlikely you will need a shell for any
+real troubleshooting.
 
-To build an image locally using Docker Buildx, you can typically run a command like:
+The flake file for the OCI image definition is at [`nix/pkgs/oci-image/default.nix`][oci-image-def].
 
-```bash
+To build an OCI image using Nix, the following outputs can be built:
-# Build for the current platform and load into the local Docker daemon
+- `nix build -L .#oci-image` (default features, x86_64 glibc)
-docker buildx build --load --tag continuwuity:latest -f docker/Dockerfile .
+- `nix build -L .#oci-image-x86_64-linux-musl` (default features, x86_64 musl)
-
+- `nix build -L .#oci-image-aarch64-linux-musl` (default features, aarch64 musl)
-# Example: Build for specific platforms and push to a registry.
+- `nix build -L .#oci-image-x86_64-linux-musl-all-features` (all features, x86_64 musl)
-# docker buildx build --platform linux/amd64,linux/arm64 --tag registry.io/org/continuwuity:latest -f docker/Dockerfile . --push
+- `nix build -L .#oci-image-aarch64-linux-musl-all-features` (all features, aarch64 musl)
-
-# Example: Build binary optimized for the current CPU
-# docker buildx build --load --tag continuwuity:latest --build-arg TARGET_CPU=native -f docker/Dockerfile .
-```
-
-Refer to the Docker Buildx documentation for more advanced build options.
-
-[dockerfile-path]: ../../docker/Dockerfile
 
 ### Run
 
@@ -127,10 +138,10 @@ web. With the two provided files,
 [`docker-compose.for-traefik.yml`](docker-compose.for-traefik.yml) (or
 [`docker-compose.with-traefik.yml`](docker-compose.with-traefik.yml)) and
 [`docker-compose.override.yml`](docker-compose.override.yml), it is equally easy
-to deploy and use Continuwuity, with a little caveat. If you already took a look at
+to deploy and use conduwuit, with a little caveat. If you already took a look at
 the files, then you should have seen the `well-known` service, and that is the
 little caveat. Traefik is simply a proxy and loadbalancer and is not able to
-serve any kind of content, but for Continuwuity to federate, we need to either
+serve any kind of content, but for conduwuit to federate, we need to either
 expose ports `443` and `8448` or serve two endpoints `.well-known/matrix/client`
 and `.well-known/matrix/server`.
 
@@ -142,3 +153,4 @@ those two files.
 See the [TURN](../turn.md) page.
 
 [nix-buildlayeredimage]: https://ryantm.github.io/nixpkgs/builders/images/dockertools/#ssec-pkgs-dockerTools-buildLayeredImage
+[oci-image-def]: https://github.com/girlbossceo/conduwuit/blob/main/nix/pkgs/oci-image/default.nix

docs/deploying/freebsd.md

@@ -1,5 +1,5 @@
-# Continuwuity for FreeBSD
+# conduwuit for FreeBSD
 
-Continuwuity at the moment does not provide FreeBSD builds or have FreeBSD packaging, however Continuwuity does build and work on FreeBSD using the system-provided RocksDB.
+conduwuit at the moment does not provide FreeBSD builds or have FreeBSD packaging, however conduwuit does build and work on FreeBSD using the system-provided RocksDB.
 
-Contributions for getting Continuwuity packaged are welcome.
+Contributions for getting conduwuit packaged are welcome.

docs/deploying/generic.md

@@ -2,11 +2,11 @@
 
 > ### Getting help
 >
-> If you run into any problems while setting up Continuwuity, ask us in
+> If you run into any problems while setting up conduwuit, ask us in
-> `#continuwuity:continuwuity.org` or [open an issue on
+> `#conduwuit:puppygock.gay` or [open an issue on
-> Forgejo](https://forgejo.ellis.link/continuwuation/continuwuity/issues/new).
+> GitHub](https://github.com/girlbossceo/conduwuit/issues/new).
 
-## Installing Continuwuity
+## Installing conduwuit
 
 ### Static prebuilt binary
 
@@ -14,10 +14,12 @@ You may simply download the binary that fits your machine architecture (x86_64
 or aarch64). Run `uname -m` to see what you need.
 
 Prebuilt fully static musl binaries can be downloaded from the latest tagged
-release [here](https://forgejo.ellis.link/continuwuation/continuwuity/releases/latest) or
+release [here](https://github.com/girlbossceo/conduwuit/releases/latest) or
 `main` CI branch workflow artifact output. These also include Debian/Ubuntu
 packages.
 
+Binaries are also available on my website directly at: <https://pup.systems/~strawberry/conduwuit/>
+
 These can be curl'd directly from. `ci-bins` are CI workflow binaries by commit
 hash/revision, and `releases` are tagged releases. Sort by descending last
 modified for the latest.
@@ -35,7 +37,7 @@ for performance.
 ### Compiling
 
 Alternatively, you may compile the binary yourself. We recommend using
-Nix (or [Lix](https://lix.systems)) to build Continuwuity as this has the most
+Nix (or [Lix](https://lix.systems)) to build conduwuit as this has the most
 guaranteed reproducibiltiy and easiest to get a build environment and output
 going. This also allows easy cross-compilation.
 
@@ -49,35 +51,35 @@ If wanting to build using standard Rust toolchains, make sure you install:
 - `liburing-dev` on the compiling machine, and `liburing` on the target host
 - LLVM and libclang for RocksDB
 
-You can build Continuwuity using `cargo build --release --all-features`
+You can build conduwuit using `cargo build --release --all-features`
 
-## Adding a Continuwuity user
+## Adding a conduwuit user
 
-While Continuwuity can run as any user it is better to use dedicated users for
+While conduwuit can run as any user it is better to use dedicated users for
 different services. This also allows you to make sure that the file permissions
 are correctly set up.
 
-In Debian, you can use this command to create a Continuwuity user:
+In Debian, you can use this command to create a conduwuit user:
 
 ```bash
-sudo adduser --system continuwuity --group --disabled-login --no-create-home
+sudo adduser --system conduwuit --group --disabled-login --no-create-home
 ```
 
 For distros without `adduser` (or where it's a symlink to `useradd`):
 
 ```bash
-sudo useradd -r --shell /usr/bin/nologin --no-create-home continuwuity
+sudo useradd -r --shell /usr/bin/nologin --no-create-home conduwuit
 ```
 
 ## Forwarding ports in the firewall or the router
 
 Matrix's default federation port is port 8448, and clients must be using port 443.
 If you would like to use only port 443, or a different port, you will need to setup
-delegation. Continuwuity has config options for doing delegation, or you can configure
+delegation. conduwuit has config options for doing delegation, or you can configure
 your reverse proxy to manually serve the necessary JSON files to do delegation
 (see the `[global.well_known]` config section).
 
-If Continuwuity runs behind a router or in a container and has a different public
+If conduwuit runs behind a router or in a container and has a different public
 IP address than the host system these public ports need to be forwarded directly
 or indirectly to the port mentioned in the config.
 
@@ -92,9 +94,9 @@ on the network level, consider something like NextDNS or Pi-Hole.
 
 ## Setting up a systemd service
 
-Two example systemd units for Continuwuity can be found
+Two example systemd units for conduwuit can be found
 [on the configuration page](../configuration/examples.md#debian-systemd-unit-file).
-You may need to change the `ExecStart=` path to where you placed the Continuwuity
+You may need to change the `ExecStart=` path to where you placed the conduwuit
 binary if it is not `/usr/bin/conduwuit`.
 
 On systems where rsyslog is used alongside journald (i.e. Red Hat-based distros
@@ -112,9 +114,9 @@ and entering the following:
 ReadWritePaths=/path/to/custom/database/path
 ```
 
-## Creating the Continuwuity configuration file
+## Creating the conduwuit configuration file
 
-Now we need to create the Continuwuity's config file in
+Now we need to create the conduwuit's config file in
 `/etc/conduwuit/conduwuit.toml`. The example config can be found at
 [conduwuit-example.toml](../configuration/examples.md).
 
@@ -125,7 +127,7 @@ RocksDB is the only supported database backend.
 
 ## Setting the correct file permissions
 
-If you are using a dedicated user for Continuwuity, you will need to allow it to
+If you are using a dedicated user for conduwuit, you will need to allow it to
 read the config. To do that you can run this:
 
 ```bash
@@ -137,7 +139,7 @@ If you use the default database path you also need to run this:
 
 ```bash
 sudo mkdir -p /var/lib/conduwuit/
-sudo chown -R continuwuity:continuwuity /var/lib/conduwuit/
+sudo chown -R conduwuit:conduwuit /var/lib/conduwuit/
 sudo chmod 700 /var/lib/conduwuit/
 ```
 
@@ -172,13 +174,13 @@ As we would prefer our users to use Caddy, we will not provide configuration fil
 
 You will need to reverse proxy everything under following routes:
 - `/_matrix/` - core Matrix C-S and S-S APIs
-- `/_conduwuit/` - ad-hoc Continuwuity routes such as `/local_user_count` and
+- `/_conduwuit/` - ad-hoc conduwuit routes such as `/local_user_count` and
 `/server_version`
 
 You can optionally reverse proxy the following individual routes:
 - `/.well-known/matrix/client` and `/.well-known/matrix/server` if using
-Continuwuity to perform delegation (see the `[global.well_known]` config section)
+conduwuit to perform delegation (see the `[global.well_known]` config section)
-- `/.well-known/matrix/support` if using Continuwuity to send the homeserver admin
+- `/.well-known/matrix/support` if using conduwuit to send the homeserver admin
 contact and support page (formerly known as MSC1929)
 - `/` if you would like to see `hewwo from conduwuit woof!` at the root
 
@@ -198,7 +200,7 @@ header, making federation non-functional. If a workaround is found, feel free to
 
 If using Apache, you need to use `nocanon` in your `ProxyPass` directive to prevent httpd from messing with the `X-Matrix` header (note that Apache isn't very good as a general reverse proxy and we discourage the usage of it if you can).
 
-If using Nginx, you need to give Continuwuity the request URI using `$request_uri`, or like so:
+If using Nginx, you need to give conduwuit the request URI using `$request_uri`, or like so:
 - `proxy_pass http://127.0.0.1:6167$request_uri;`
 - `proxy_pass http://127.0.0.1:6167;`
 
@@ -207,7 +209,7 @@ Nginx users need to increase `client_max_body_size` (default is 1M) to match
 
 ## You're done
 
-Now you can start Continuwuity with:
+Now you can start conduwuit with:
 
 ```bash
 sudo systemctl start conduwuit

docs/deploying/kubernetes.md

@@ -1,9 +1,8 @@
-# Continuwuity for Kubernetes
+# conduwuit for Kubernetes
 
-Continuwuity doesn't support horizontal scalability or distributed loading
+conduwuit doesn't support horizontal scalability or distributed loading
 natively, however a community maintained Helm Chart is available here to run
 conduwuit on Kubernetes: <https://gitlab.cronce.io/charts/conduwuit>
 
-This should be compatible with continuwuity, but you will need to change the image reference.
+Should changes need to be made, please reach out to the maintainer in our
-
+Matrix room as this is not maintained/controlled by the conduwuit maintainers.
-Should changes need to be made, please reach out to the maintainer as this is not maintained/controlled by the Continuwuity maintainers.

docs/deploying/nixos.md

@@ -1,33 +1,66 @@
-# Continuwuity for NixOS
+# conduwuit for NixOS
 
-Continuwuity can be acquired by Nix (or [Lix][lix]) from various places:
+conduwuit can be acquired by Nix (or [Lix][lix]) from various places:
 
 * The `flake.nix` at the root of the repo
 * The `default.nix` at the root of the repo
-* From Continuwuity's binary cache
+* From conduwuit's binary cache
+
+A community maintained NixOS package is available at [`conduwuit`](https://search.nixos.org/packages?channel=unstable&show=conduwuit&from=0&size=50&sort=relevance&type=packages&query=conduwuit)
+
+### Binary cache
+
+A binary cache for conduwuit that the CI/CD publishes to is available at the
+following places (both are the same just different names):
+
+```
+https://attic.kennel.juneis.dog/conduit
+conduit:eEKoUwlQGDdYmAI/Q/0slVlegqh/QmAvQd7HBSm21Wk=
+
+https://attic.kennel.juneis.dog/conduwuit
+conduwuit:BbycGUgTISsltcmH0qNjFR9dbrQNYgdIAcmViSGoVTE=
+```
+
+The binary caches were recreated some months ago due to attic issues. The old public
+keys were:
+
+```
+conduit:Isq8FGyEC6FOXH6nD+BOeAA+bKp6X6UIbupSlGEPuOg=
+conduwuit:lYPVh7o1hLu1idH4Xt2QHaRa49WRGSAqzcfFd94aOTw=
+```
+
+If needed, we have a binary cache on Cachix but it is only limited to 5GB:
+
+```
+https://conduwuit.cachix.org
+conduwuit.cachix.org-1:MFRm6jcnfTf0jSAbmvLfhO3KBMt4px+1xaereWXp8Xg=
+```
+
+If specifying a Git remote URL in your flake, you can use any remotes that
+are specified on the README (the mirrors), such as the GitHub: `github:girlbossceo/conduwuit`
 
 ### NixOS module
 
 The `flake.nix` and `default.nix` do not currently provide a NixOS module (contributions
 welcome!), so [`services.matrix-conduit`][module] from Nixpkgs can be used to configure
-Continuwuity.
+conduwuit.
 
 ### Conduit NixOS Config Module and SQLite
 
 Beware! The [`services.matrix-conduit`][module] module defaults to SQLite as a database backend.
-Continuwuity dropped SQLite support in favor of exclusively supporting the much faster RocksDB.
+Conduwuit dropped SQLite support in favor of exclusively supporting the much faster RocksDB.
 Make sure that you are using the RocksDB backend before migrating!
 
 There is a [tool to  migrate a Conduit SQLite database to
 RocksDB](https://github.com/ShadowJonathan/conduit_toolbox/).
 
-If you want to run the latest code, you should get Continuwuity from the `flake.nix`
+If you want to run the latest code, you should get conduwuit from the `flake.nix`
 or `default.nix` and set [`services.matrix-conduit.package`][package]
-appropriately to use Continuwuity instead of Conduit.
+appropriately to use conduwuit instead of Conduit.
 
 ### UNIX sockets
 
-Due to the lack of a Continuwuity NixOS module, when using the `services.matrix-conduit` module
+Due to the lack of a conduwuit NixOS module, when using the `services.matrix-conduit` module
 a workaround like the one below is necessary to use UNIX sockets. This is because the UNIX
 socket option does not exist in Conduit, and the module forcibly sets the `address` and 
 `port` config options.
@@ -51,13 +84,13 @@ disallows the namespace from accessing or creating UNIX sockets and has to be en
 systemd.services.conduit.serviceConfig.RestrictAddressFamilies = [ "AF_UNIX" ];
 ```
 
-Even though those workarounds are feasible a Continuwuity NixOS configuration module, developed and
+Even though those workarounds are feasible a conduwuit NixOS configuration module, developed and
 published by the community, would be appreciated.
 
 ### jemalloc and hardened profile
 
-Continuwuity uses jemalloc by default. This may interfere with the [`hardened.nix` profile][hardened.nix]
+conduwuit uses jemalloc by default. This may interfere with the [`hardened.nix` profile][hardened.nix]
-due to them using `scudo` by default. You must either disable/hide `scudo` from Continuwuity, or
+due to them using `scudo` by default. You must either disable/hide `scudo` from conduwuit, or
 disable jemalloc like so:
 
 ```nix

docs/development.md

@@ -4,9 +4,9 @@ Information about developing the project. If you are only interested in using
 it, you can safely ignore this page. If you plan on contributing, see the
 [contributor's guide](./contributing.md).
 
-## Continuwuity project layout
+## conduwuit project layout
 
-Continuwuity uses a collection of sub-crates, packages, or workspace members
+conduwuit uses a collection of sub-crates, packages, or workspace members
 that indicate what each general area of code is for. All of the workspace
 members are under `src/`. The workspace definition is at the top level / root
 `Cargo.toml`.
@@ -14,11 +14,11 @@ members are under `src/`. The workspace definition is at the top level / root
 The crate names are generally self-explanatory:
 - `admin` is the admin room
 - `api` is the HTTP API, Matrix C-S and S-S endpoints, etc
-- `core` is core Continuwuity functionality like config loading, error definitions,
+- `core` is core conduwuit functionality like config loading, error definitions,
 global utilities, logging infrastructure, etc
 - `database` is RocksDB methods, helpers, RocksDB config, and general database definitions,
 utilities, or functions
-- `macros` are Continuwuity Rust [macros][macros] like general helper macros, logging
+- `macros` are conduwuit Rust [macros][macros] like general helper macros, logging
 and error handling macros, and [syn][syn] and [procedural macros][proc-macro]
 used for admin room commands and others
 - `main` is the "primary" sub-crate. This is where the `main()` function lives,
@@ -35,7 +35,7 @@ if you truly find yourself needing to, we recommend reaching out to us in
 the Matrix room for discussions about it beforehand.
 
 The primary inspiration for this design was apart of hot reloadable development,
-to support "Continuwuity as a library" where specific parts can simply be swapped out.
+to support "conduwuit as a library" where specific parts can simply be swapped out.
 There is evidence Conduit wanted to go this route too as `axum` is technically an
 optional feature in Conduit, and can be compiled without the binary or axum library
 for handling inbound web requests; but it was never completed or worked.
@@ -68,10 +68,10 @@ do this if Rust supported workspace-level features to begin with.
 
 ## List of forked dependencies
 
-During Continuwuity development, we have had to fork
+During conduwuit development, we have had to fork
 some dependencies to support our use-cases in some areas. This ranges from
 things said upstream project won't accept for any reason, faster-paced
-development (unresponsive or slow upstream), Continuwuity-specific usecases, or
+development (unresponsive or slow upstream), conduwuit-specific usecases, or
 lack of time to upstream some things.
 
 - [ruma/ruma][1]: <https://github.com/girlbossceo/ruwuma> - various performance
@@ -84,7 +84,7 @@ builds seem to be broken on upstream, fixes some broken/suspicious code in
 places, additional safety measures, and support redzones for Valgrind
 - [zyansheep/rustyline-async][4]:
 <https://github.com/girlbossceo/rustyline-async> - tab completion callback and
-`CTRL+\` signal quit event for Continuwuity console CLI
+`CTRL+\` signal quit event for conduwuit console CLI
 - [rust-rocksdb/rust-rocksdb][5]:
 <https://github.com/girlbossceo/rust-rocksdb-zaidoon1> - [`@zaidoon1`][8]'s fork
 has quicker updates, more up to date dependencies, etc. Our fork fixes musl build
@@ -97,7 +97,7 @@ alongside other logging/metrics things
 ## Debugging with `tokio-console`
 
 [`tokio-console`][7] can be a useful tool for debugging and profiling. To make a
-`tokio-console`-enabled build of Continuwuity, enable the `tokio_console` feature,
+`tokio-console`-enabled build of conduwuit, enable the `tokio_console` feature,
 disable the default `release_max_log_level` feature, and set the `--cfg
 tokio_unstable` flag to enable experimental tokio APIs. A build might look like
 this:
@@ -109,7 +109,7 @@ RUSTFLAGS="--cfg tokio_unstable" cargo +nightly build \
     --features=systemd,element_hacks,gzip_compression,brotli_compression,zstd_compression,tokio_console
 ```
 
-You will also need to enable the `tokio_console` config option in Continuwuity when
+You will also need to enable the `tokio_console` config option in conduwuit when
 starting it. This was due to tokio-console causing gradual memory leak/usage
 if left enabled.
 

docs/development/hot_reload.md

@@ -5,7 +5,7 @@ guaranteed to work at this time.
 
 ### Summary
 
-When developing in debug-builds with the nightly toolchain, Continuwuity is modular
+When developing in debug-builds with the nightly toolchain, conduwuit is modular
 using dynamic libraries and various parts of the application are hot-reloadable
 while the server is running: http api handlers, admin commands, services,
 database, etc. These are all split up into individual workspace crates as seen
@@ -42,7 +42,7 @@ library, macOS, and likely other host architectures are not supported (if other
 architectures work, feel free to let us know and/or make a PR updating this).
 This should work on GNU ld and lld (rust-lld) and gcc/clang, however if you
 happen to have linker issues it's recommended to try using `mold` or `gold`
-linkers, and please let us know in the [Continuwuity Matrix room][7] the linker
+linkers, and please let us know in the [conduwuit Matrix room][7] the linker
 error and what linker solved this issue so we can figure out a solution. Ideally
 there should be minimal friction to using this, and in the future a build script
 (`build.rs`) may be suitable to making this easier to use if the capabilities
@@ -52,13 +52,13 @@ allow us.
 
 As of 19 May 2024, the instructions for using this are:
 
-0. Have patience. Don't hesitate to join the [Continuwuity Matrix room][7] to
+0. Have patience. Don't hesitate to join the [conduwuit Matrix room][7] to
    receive help using this. As indicated by the various rustflags used and some
 of the interesting issues linked at the bottom, this is definitely not something
 the Rust ecosystem or toolchain is used to doing.
 
 1. Install the nightly toolchain using rustup. You may need to use `rustup
-   override set nightly` in your local Continuwuity directory, or use `cargo
+   override set nightly` in your local conduwuit directory, or use `cargo
 +nightly` for all actions.
 
 2. Uncomment `cargo-features` at the top level / root Cargo.toml
@@ -85,14 +85,14 @@ LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$HOME/.rustup/toolchains/nightly-x86_64-unknown
    Cargo should only rebuild what was changed / what's necessary, so it should
    not be rebuilding all the crates.
 
-9. In your Continuwuity server terminal, hit/send `CTRL+C` signal. This will tell
+9. In your conduwuit server terminal, hit/send `CTRL+C` signal. This will tell
-   Continuwuity to find which libraries need to be reloaded, and reloads them as
+   conduwuit to find which libraries need to be reloaded, and reloads them as
    necessary.
 
 10. If there were no errors, it will tell you it successfully reloaded `#`
    modules, and your changes should now be visible. Repeat 7 - 9 as needed.
 
-To shutdown Continuwuity in this setup, hit/send `CTRL+\`. Normal builds still
+To shutdown conduwuit in this setup, hit/send `CTRL+\`. Normal builds still
 shutdown with `CTRL+C` as usual.
 
 Steps 1 - 5 are the initial first-time steps for using this. To remove the hot
@@ -101,7 +101,7 @@ reload setup, revert/comment all the Cargo.toml changes.
 As mentioned in the requirements section, if you happen to have some linker
 issues, try using the `-fuse-ld=` rustflag and specify mold or gold in all the
 `rustflags` definitions in the top level Cargo.toml, and please let us know in
-the [Continuwuity Matrix room][7] the problem. mold can be installed typically
+the [conduwuit Matrix room][7] the problem. mold can be installed typically
 through your distro, and gold is provided by the binutils package.
 
 It's possible a helper script can be made to do all of this, or most preferably
@@ -136,7 +136,7 @@ acyclic graph. The primary rule is simple and illustrated in the figure below:
 **no crate is allowed to call a function or use a variable from a crate below
 it.**
 
-![Continuwuity's dynamic library setup diagram - created by Jason
+![conduwuit's dynamic library setup diagram - created by Jason
 Volk](assets/libraries.png)
 
 When a symbol is referenced between crates they become bound: **crates cannot be
@@ -147,7 +147,7 @@ by using an `RTLD_LOCAL` binding for just one link between the main executable
 and the first crate, freeing the executable from all modules as no global
 binding ever occurs between them.
 
-![Continuwuity's reload and load order diagram - created by Jason
+![conduwuit's reload and load order diagram - created by Jason
 Volk](assets/reload_order.png)
 
 Proper resource management is essential for reliable reloading to occur. This is
@@ -196,5 +196,5 @@ The initial implementation PR is available [here][1].
 [4]: https://github.com/rust-lang/rust/issues/28794#issuecomment-368693049
 [5]: https://github.com/rust-lang/cargo/issues/12746
 [6]: https://crates.io/crates/hot-lib-reloader/
-[7]: https://matrix.to/#/#continuwuity:continuwuity.org
+[7]: https://matrix.to/#/#conduwuit:puppygock.gay
 [8]: https://crates.io/crates/libloading

docs/introduction.md

@@ -1,4 +1,4 @@
-# Continuwuity
+# conduwuit
 
 {{#include ../README.md:catchphrase}}
 
@@ -8,7 +8,7 @@
 
 - [Deployment options](deploying.md)
 
-If you want to connect an appservice to Continuwuity, take a look at the
+If you want to connect an appservice to conduwuit, take a look at the
 [appservices documentation](appservices.md).
 
 #### How can I contribute?

docs/maintenance.md

@@ -1,14 +1,14 @@
-# Maintaining your Continuwuity setup
+# Maintaining your conduwuit setup
 
 ## Moderation
 
-Continuwuity has moderation through admin room commands. "binary commands" (medium
+conduwuit has moderation through admin room commands. "binary commands" (medium
 priority) and an admin API (low priority) is planned. Some moderation-related
 config options are available in the example config such as "global ACLs" and
 blocking media requests to certain servers. See the example config for the
 moderation config options under the "Moderation / Privacy / Security" section.
 
-Continuwuity has moderation admin commands for:
+conduwuit has moderation admin commands for:
 
 - managing room aliases (`!admin rooms alias`)
 - managing room directory (`!admin rooms directory`)
@@ -36,7 +36,7 @@ each object being newline delimited. An example of doing this is:
 ## Database (RocksDB)
 
 Generally there is very little you need to do. [Compaction][rocksdb-compaction]
-is ran automatically based on various defined thresholds tuned for Continuwuity to
+is ran automatically based on various defined thresholds tuned for conduwuit to
 be high performance with the least I/O amplifcation or overhead. Manually
 running compaction is not recommended, or compaction via a timer, due to
 creating unnecessary I/O amplification. RocksDB is built with io_uring support
@@ -50,7 +50,7 @@ Some RocksDB settings can be adjusted such as the compression method chosen. See
 the RocksDB section in the [example config](configuration/examples.md).
 
 btrfs users have reported that database compression does not need to be disabled
-on Continuwuity as the filesystem already does not attempt to compress. This can be
+on conduwuit as the filesystem already does not attempt to compress. This can be
 validated by using `filefrag -v` on a `.SST` file in your database, and ensure
 the `physical_offset` matches (no filesystem compression). It is very important
 to ensure no additional filesystem compression takes place as this can render
@@ -70,7 +70,7 @@ they're server logs or database logs, however they are critical RocksDB files
 related to WAL tracking.
 
 The only safe files that can be deleted are the `LOG` files (all caps). These
-are the real RocksDB telemetry/log files, however Continuwuity has already
+are the real RocksDB telemetry/log files, however conduwuit has already
 configured to only store up to 3 RocksDB `LOG` files due to generall being
 useless for average users unless troubleshooting something low-level. If you
 would like to store nearly none at all, see the `rocksdb_max_log_files`
@@ -88,7 +88,7 @@ still be joined together.
 
 To restore a backup from an online RocksDB backup:
 
-- shutdown Continuwuity
+- shutdown conduwuit
 - create a new directory for merging together the data
 - in the online backup created, copy all `.sst` files in
 `$DATABASE_BACKUP_PATH/shared_checksum` to your new directory
@@ -99,9 +99,9 @@ To restore a backup from an online RocksDB backup:
 if you have multiple) to your new directory
 - set your `database_path` config option to your new directory, or replace your
 old one with the new one you crafted
-- start up Continuwuity again and it should open as normal
+- start up conduwuit again and it should open as normal
 
-If you'd like to do an offline backup, shutdown Continuwuity and copy your
+If you'd like to do an offline backup, shutdown conduwuit and copy your
 `database_path` directory elsewhere. This can be restored with no modifications
 needed.
 
@@ -110,7 +110,7 @@ directory.
 
 ## Media
 
-Media still needs various work, however Continuwuity implements media deletion via:
+Media still needs various work, however conduwuit implements media deletion via:
 
 - MXC URI or Event ID (unencrypted and attempts to find the MXC URI in the
 event)
@@ -118,17 +118,17 @@ event)
 - Delete remote media in the past `N` seconds/minutes via filesystem metadata on
 the file created time (`btime`) or file modified time (`mtime`)
 
-See the `!admin media` command for further information. All media in Continuwuity
+See the `!admin media` command for further information. All media in conduwuit
 is stored at `$DATABASE_DIR/media`. This will be configurable soon.
 
 If you are finding yourself needing extensive granular control over media, we
 recommend looking into [Matrix Media
-Repo](https://github.com/t2bot/matrix-media-repo). Continuwuity intends to
+Repo](https://github.com/t2bot/matrix-media-repo). conduwuit intends to
 implement various utilities for media, but MMR is dedicated to extensive media
 management.
 
 Built-in S3 support is also planned, but for now using a "S3 filesystem" on
-`media/` works. Continuwuity also sends a `Cache-Control` header of 1 year and
+`media/` works. conduwuit also sends a `Cache-Control` header of 1 year and
 immutable for all media requests (download and thumbnail) to reduce unnecessary
 media requests from browsers, reduce bandwidth usage, and reduce load.
 

docs/static/_headers

@@ -1,6 +1,3 @@
 /.well-known/matrix/*
   Access-Control-Allow-Origin: *
   Content-Type: application/json
-/.well-known/continuwuity/*
-  Access-Control-Allow-Origin: *
-  Content-Type: application/json

docs/static/announcements.json

@@ -1,9 +0,0 @@
-{
-    "$schema": "https://continuwuity.org/schema/announcements.schema.json",
-    "announcements": [
-        {
-            "id": 1,
-            "message": "Welcome to Continuwuity! Important announcements about the project will appear here."
-        }
-    ]
-}

docs/static/announcements.schema.json

@@ -1,31 +0,0 @@
-{
-    "$schema": "http://json-schema.org/draft-04/schema#",
-    "$id": "https://continwuity.org/schema/announcements.schema.json",
-    "type": "object",
-    "properties": {
-      "updates": {
-        "type": "array",
-        "items": {
-          "type": "object",
-          "properties": {
-            "id": {
-              "type": "integer"
-            },
-            "message": {
-              "type": "string"
-            },
-            "date": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "id",
-            "message"
-          ]
-        }
-      }
-    },
-    "required": [
-      "updates"
-    ]
-  }

docs/static/support

@@ -1,24 +0,0 @@
-{
-  "contacts": [
-    {
-      "email_address": "security@continuwuity.org",
-      "role": "m.role.security"
-    },
-    {
-      "matrix_id": "@tom:continuwuity.org",
-      "email_address": "tom@tcpip.uk",
-      "role": "m.role.admin"
-    },
-    {
-      "matrix_id": "@jade:continuwuity.org",
-      "email_address": "jade@continuwuity.org",
-      "role": "m.role.admin"
-    },
-    {
-      "matrix_id": "@nex:continuwuity.org",
-      "email_address": "nex@continuwuity.org",
-      "role": "m.role.admin"
-    }
-  ],
-  "support_page": "https://continuwuity.org/introduction#contact"
-}

docs/troubleshooting.md

@@ -1,48 +1,47 @@
-# Troubleshooting Continuwuity
+# Troubleshooting conduwuit
 
-> **Docker users ⚠️**
+> ## Docker users ⚠️
 >
-> Docker can be difficult to use and debug. It's common for Docker
+> Docker is extremely UX unfriendly. Because of this, a ton of issues or support
-> misconfigurations to cause issues, particularly with networking and permissions.
+> is actually Docker support, not conduwuit support. We also cannot document the
-> Please check that your issues are not due to problems with your Docker setup.
+> ever-growing list of Docker issues here.
+>
+> If you intend on asking for support and you are using Docker, **PLEASE**
+> triple validate your issues are **NOT** because you have a misconfiguration in
+> your Docker setup.
+>
+> If there are things like Compose file issues or Dockerhub image issues, those
+> can still be mentioned as long as they're something we can fix.
 
-## Continuwuity and Matrix issues
+## conduwuit and Matrix issues
 
-### Lost access to admin room
+#### Lost access to admin room
 
 You can reinvite yourself to the admin room through the following methods:
-
+- Use the `--execute "users make_user_admin <username>"` conduwuit binary
-- Use the `--execute "users make_user_admin <username>"` Continuwuity binary
 argument once to invite yourslf to the admin room on startup
-- Use the Continuwuity console/CLI to run the `users make_user_admin` command
+- Use the conduwuit console/CLI to run the `users make_user_admin` command
 - Or specify the `emergency_password` config option to allow you to temporarily
 log into the server account (`@conduit`) from a web client
 
 ## General potential issues
 
-### Potential DNS issues when using Docker
+#### Potential DNS issues when using Docker
 
-Docker's DNS setup for containers in a non-default network intercepts queries to
+Docker has issues with its default DNS setup that may cause DNS to not be
-enable resolving of container hostnames to IP addresses. However, due to
+properly functional when running conduwuit, resulting in federation issues. The
-performance issues with Docker's built-in resolver, this can cause DNS queries
+symptoms of this have shown in excessively long room joins (30+ minutes) from
-to take a long time to resolve, resulting in federation issues.
+very long DNS timeouts, log entries of "mismatching responding nameservers",
-
-This is particularly common with Docker Compose, as custom networks are easily
-created and configured.
-
-Symptoms of this include excessively long room joins (30+ minutes) from very
-long DNS timeouts, log entries of "mismatching responding nameservers",
 and/or partial or non-functional inbound/outbound federation.
 
-This is not a bug in continuwuity. Docker's default DNS resolver is not suitable
+This is **not** a conduwuit issue, and is purely a Docker issue. It is not
-for heavy DNS activity, which is normal for federated protocols like Matrix.
+sustainable for heavy DNS activity which is normal for Matrix federation. The
-
+workarounds for this are:
-Workarounds:
-
 - Use DNS over TCP via the config option `query_over_tcp_only = true`
-- Bypass Docker's default DNS setup and instead allow the container to use and communicate with your host's DNS servers. Typically, this can be done by mounting the host's `/etc/resolv.conf`.
+- Don't use Docker's default DNS setup and instead allow the container to use
+and communicate with your host's DNS servers (host's `/etc/resolv.conf`)
 
-### DNS No connections available error message
+#### DNS No connections available error message
 
 If you receive spurious amounts of error logs saying "DNS No connections
 available", this is due to your DNS server (servers from `/etc/resolv.conf`)
@@ -65,7 +64,7 @@ very computationally expensive, and is extremely susceptible to denial of
 service, especially on Matrix. Many servers also strangely have broken DNSSEC
 setups and will result in non-functional federation.
 
-Continuwuity cannot provide a "works-for-everyone" Unbound DNS setup guide, but
+conduwuit cannot provide a "works-for-everyone" Unbound DNS setup guide, but
 the [official Unbound tuning guide][unbound-tuning] and the [Unbound Arch Linux wiki page][unbound-arch]
 may be of interest. Disabling DNSSEC on Unbound is commenting out trust-anchors
 config options and removing the `validator` module.
@@ -76,9 +75,9 @@ high load, and we have identified its DNS caching to not be very effective.
 dnsmasq can possibly work, but it does **not** support TCP fallback which can be
 problematic when receiving large DNS responses such as from large SRV records.
 If you still want to use dnsmasq, make sure you **disable** `dns_tcp_fallback`
-in Continuwuity config.
+in conduwuit config.
 
-Raising `dns_cache_entries` in Continuwuity config from the default can also assist
+Raising `dns_cache_entries` in conduwuit config from the default can also assist
 in DNS caching, but a full-fledged external caching resolver is better and more
 reliable.
 
@@ -92,13 +91,13 @@ reliability at a slight performance cost due to TCP overhead.
 
 ## RocksDB / database issues
 
-### Database corruption
+#### Database corruption
 
 If your database is corrupted *and* is failing to start (e.g. checksum
 mismatch), it may be recoverable but careful steps must be taken, and there is
 no guarantee it may be recoverable.
 
-The first thing that can be done is launching Continuwuity with the
+The first thing that can be done is launching conduwuit with the
 `rocksdb_repair` config option set to true. This will tell RocksDB to attempt to
 repair itself at launch. If this does not work, disable the option and continue
 reading.
@@ -110,7 +109,7 @@ RocksDB has the following recovery modes:
 - `PointInTime`
 - `SkipAnyCorruptedRecord`
 
-By default, Continuwuity uses `TolerateCorruptedTailRecords` as generally these may
+By default, conduwuit uses `TolerateCorruptedTailRecords` as generally these may
 be due to bad federation and we can re-fetch the correct data over federation.
 The RocksDB default is `PointInTime` which will attempt to restore a "snapshot"
 of the data when it was last known to be good. This data can be either a few
@@ -127,12 +126,12 @@ if `PointInTime` does not work as a last ditch effort.
 
 With this in mind:
 
-- First start Continuwuity with the `PointInTime` recovery method. See the [example
+- First start conduwuit with the `PointInTime` recovery method. See the [example
 config](configuration/examples.md) for how to do this using
 `rocksdb_recovery_mode`
 - If your database successfully opens, clients are recommended to clear their
 client cache to account for the rollback
-- Leave your Continuwuity running in `PointInTime` for at least 30-60 minutes so as
+- Leave your conduwuit running in `PointInTime` for at least 30-60 minutes so as
 much possible corruption is restored
 - If all goes will, you should be able to restore back to using
 `TolerateCorruptedTailRecords` and you have successfully recovered your database
@@ -143,16 +142,16 @@ Note that users should not really be debugging things. If you find yourself
 debugging and find the issue, please let us know and/or how we can fix it.
 Various debug commands can be found in `!admin debug`.
 
-### Debug/Trace log level
+#### Debug/Trace log level
 
-Continuwuity builds without debug or trace log levels at compile time by default
+conduwuit builds without debug or trace log levels at compile time by default
 for substantial performance gains in CPU usage and improved compile times. If
 you need to access debug/trace log levels, you will need to build without the
 `release_max_log_level` feature or use our provided static debug binaries.
 
-### Changing log level dynamically
+#### Changing log level dynamically
 
-Continuwuity supports changing the tracing log environment filter on-the-fly using
+conduwuit supports changing the tracing log environment filter on-the-fly using
 the admin command `!admin debug change-log-level <log env filter>`. This accepts
 a string **without quotes** the same format as the `log` config option.
 
@@ -167,9 +166,9 @@ load, simply pass the `--reset` flag.
 
 `!admin debug change-log-level --reset`
 
-### Pinging servers
+#### Pinging servers
 
-Continuwuity can ping other servers using `!admin debug ping <server>`. This takes
+conduwuit can ping other servers using `!admin debug ping <server>`. This takes
 a server name and goes through the server discovery process and queries
 `/_matrix/federation/v1/version`. Errors are outputted.
 
@@ -178,15 +177,15 @@ server performance on either side as that endpoint is completely unauthenticated
 and simply fetches a string on a static JSON endpoint. It is very low cost both
 bandwidth and computationally.
 
-### Allocator memory stats
+#### Allocator memory stats
 
 When using jemalloc with jemallocator's `stats` feature (`--enable-stats`), you
-can see Continuwuity's high-level allocator stats by using
+can see conduwuit's high-level allocator stats by using
 `!admin server memory-usage` at the bottom.
 
 If you are a developer, you can also view the raw jemalloc statistics with
 `!admin debug memory-stats`. Please note that this output is extremely large
-which may only be visible in the Continuwuity console CLI due to PDU size limits,
+which may only be visible in the conduwuit console CLI due to PDU size limits,
 and is not easy for non-developers to understand.
 
 [unbound-tuning]: https://unbound.docs.nlnetlabs.nl/en/latest/topics/core/performance.html

docs/turn.md

@@ -1,6 +1,6 @@
 # Setting up TURN/STURN
 
-In order to make or receive calls, a TURN server is required. Continuwuity suggests
+In order to make or receive calls, a TURN server is required. conduwuit suggests
 using [Coturn](https://github.com/coturn/coturn) for this purpose, which is also
 available as a Docker image.
 
@@ -17,9 +17,9 @@ realm=<your server domain>
 A common way to generate a suitable alphanumeric secret key is by using `pwgen
 -s 64 1`.
 
-These same values need to be set in Continuwuity. See the [example
+These same values need to be set in conduwuit. See the [example
 config](configuration/examples.md) in the TURN section for configuring these and
-restart Continuwuity after.
+restart conduwuit after.
 
 `turn_secret` or a path to `turn_secret_file` must have a value of your
 coturn `static-auth-secret`, or use `turn_username` and `turn_password`
@@ -34,7 +34,7 @@ If you are using TURN over TLS, you can replace `turn:` with `turns:` in the
 TURN over TLS. This is highly recommended.
 
 If you need unauthenticated access to the TURN URIs, or some clients may be
-having trouble, you can enable `turn_guest_access` in Continuwuity which disables
+having trouble, you can enable `turn_guest_access` in conduwuit which disables
 authentication for the TURN URI endpoint `/_matrix/client/v3/voip/turnServer`
 
 ### Run

src/admin/query/globals.rs

@@ -11,8 +11,6 @@ pub(crate) enum GlobalsCommand {
 
 	CurrentCount,
 
-	LastCheckForAnnouncementsId,
-
 	/// - This returns an empty `Ok(BTreeMap<..>)` when there are no keys found
 	///   for the server.
 	SigningKeysFor {
@@ -39,16 +37,6 @@ pub(super) async fn process(subcommand: GlobalsCommand, context: &Context<'_>) -
 
 			write!(context, "Query completed in {query_time:?}:\n\n```rs\n{results:#?}\n```")
 		},
-		| GlobalsCommand::LastCheckForAnnouncementsId => {
-			let timer = tokio::time::Instant::now();
-			let results = services
-				.announcements
-				.last_check_for_announcements_id()
-				.await;
-			let query_time = timer.elapsed();
-
-			write!(context, "Query completed in {query_time:?}:\n\n```rs\n{results:#?}\n```")
-		},
 		| GlobalsCommand::SigningKeysFor { origin } => {
 			let timer = tokio::time::Instant::now();
 			let results = services.server_keys.verify_keys_for(&origin).await;

src/admin/server/mod.rs

@@ -36,7 +36,7 @@ pub(super) enum ServerCommand {
 	/// - Print database memory usage statistics
 	MemoryUsage,
 
-	/// - Clears all of Continuwuity's caches
+	/// - Clears all of Conduwuit's caches
 	ClearCaches,
 
 	/// - Performs an online backup of the database (only available for RocksDB

src/api/client/directory.rs

@@ -52,8 +52,13 @@ pub(crate) async fn get_public_rooms_filtered_route(
 ) -> Result<get_public_rooms_filtered::v3::Response> {
 	if let Some(server) = &body.server {
 		if services
-			.moderation
+			.config
-			.is_remote_server_room_directory_forbidden(server)
+			.forbidden_remote_room_directory_server_names
+			.is_match(server.host())
+			|| services
+				.config
+				.forbidden_remote_server_names
+				.is_match(server.host())
 		{
 			return Err!(Request(Forbidden("Server is banned on this homeserver.")));
 		}
@@ -87,7 +92,15 @@ pub(crate) async fn get_public_rooms_route(
 	body: Ruma<get_public_rooms::v3::Request>,
 ) -> Result<get_public_rooms::v3::Response> {
 	if let Some(server) = &body.server {
-		if services.moderation.is_remote_server_forbidden(server) {
+		if services
+			.config
+			.forbidden_remote_room_directory_server_names
+			.is_match(server.host())
+			|| services
+				.config
+				.forbidden_remote_server_names
+				.is_match(server.host())
+		{
 			return Err!(Request(Forbidden("Server is banned on this homeserver.")));
 		}
 	}

src/api/client/membership.rs

@@ -83,8 +83,9 @@ async fn banned_room_check(
 	if let Some(room_id) = room_id {
 		if services.rooms.metadata.is_banned(room_id).await
 			|| services
-				.moderation
+				.config
-				.is_remote_server_forbidden(room_id.server_name().expect("legacy room mxid"))
+				.forbidden_remote_server_names
+				.is_match(room_id.server_name().expect("legacy room mxid").host())
 		{
 			warn!(
 				"User {user_id} who is not an admin attempted to send an invite for or \
@@ -1855,10 +1856,7 @@ pub async fn leave_room(
 
 	// Ask a remote server if we don't have this room and are not knocking on it
 	if dont_have_room.and(not_knocked).await {
-		if let Err(e) = remote_leave_room(services, user_id, room_id, reason.clone())
+		if let Err(e) = remote_leave_room(services, user_id, room_id).boxed().await {
-			.boxed()
-			.await
-		{
 			warn!(%user_id, "Failed to leave room {room_id} remotely: {e}");
 			// Don't tell the client about this error
 		}
@@ -1943,7 +1941,6 @@ async fn remote_leave_room(
 	services: &Services,
 	user_id: &UserId,
 	room_id: &RoomId,
-	reason: Option<String>,
 ) -> Result<()> {
 	let mut make_leave_response_and_server =
 		Err!(BadServerResponse("No remote server available to assist in leaving {room_id}."));
@@ -2060,12 +2057,6 @@ async fn remote_leave_room(
 				.expect("Timestamp is valid js_int value"),
 		),
 	);
-	// Inject the reason key into the event content dict if it exists
-	if let Some(reason) = reason {
-		if let Some(CanonicalJsonValue::Object(content)) = leave_event_stub.get_mut("content") {
-			content.insert("reason".to_owned(), CanonicalJsonValue::String(reason));
-		}
-	}
 
 	// room v3 and above removed the "event_id" field from remote PDU format
 	match room_version_id {

src/api/client/message.rs

@@ -1,5 +1,3 @@
-use core::panic;
-
 use axum::extract::State;
 use conduwuit::{
 	Err, Result, at,
@@ -134,6 +132,8 @@ pub(crate) async fn get_message_events_route(
 		.take(limit)
 		.collect()
 		.await;
+	// let appservice_id = body.appservice_info.map(|appservice|
+	// appservice.registration.id);
 
 	let lazy_loading_context = lazy_loading::Context {
 		user_id: sender_user,
@@ -143,7 +143,7 @@ pub(crate) async fn get_message_events_route(
 				if let Some(registration) = body.appservice_info.as_ref() {
 					<&DeviceId>::from(registration.registration.id.as_str())
 				} else {
-					panic!("No device_id provided and no appservice registration found, this should be unreachable");
+					<&DeviceId>::from("")
 				},
 		},
 		room_id,
@@ -274,13 +274,12 @@ pub(crate) async fn is_ignored_pdu(
 	let ignored_type = IGNORED_MESSAGE_TYPES.binary_search(&pdu.kind).is_ok();
 
 	let ignored_server = services
-		.moderation
+		.config
-		.is_remote_server_ignored(pdu.sender().server_name());
+		.forbidden_remote_server_names
+		.is_match(pdu.sender().server_name().host());
 
 	if ignored_type
-		&& (ignored_server
+		&& (ignored_server || services.users.user_is_ignored(&pdu.sender, user_id).await)
-			|| (!services.config.send_messages_from_ignored_users_to_client
-				&& services.users.user_is_ignored(&pdu.sender, user_id).await))
 	{
 		return true;
 	}

src/api/client/room/create.rs

@@ -107,6 +107,7 @@ pub(crate) async fn create_room_route(
 
 		return Err!(Request(Forbidden("Publishing rooms to the room directory is not allowed")));
 	}
+
 	let _short_id = services
 		.rooms
 		.short
@@ -605,42 +606,24 @@ fn custom_room_id_check(services: &Services, custom_room_id: &str) -> Result<Own
 		return Err(Error::BadRequest(ErrorKind::Unknown, "Custom room ID is forbidden."));
 	}
 
-	let server_name = services.globals.server_name();
-	let mut room_id = custom_room_id.to_owned();
 	if custom_room_id.contains(':') {
-		if !custom_room_id.starts_with('!') {
-			return Err(Error::BadRequest(
-				ErrorKind::InvalidParam,
-				"Custom room ID contains an unexpected `:` which is not allowed.",
-			));
-		}
-	} else if custom_room_id.starts_with('!') {
 		return Err(Error::BadRequest(
 			ErrorKind::InvalidParam,
-			"Room ID is prefixed with !, but is not fully qualified. You likely did not want \
+			"Custom room ID contained `:` which is not allowed. Please note that this expects a \
-			 this.",
+			 localpart, not the full room ID.",
+		));
+	} else if custom_room_id.contains(char::is_whitespace) {
+		return Err(Error::BadRequest(
+			ErrorKind::InvalidParam,
+			"Custom room ID contained spaces which is not valid.",
 		));
-	} else {
-		room_id = format!("!{custom_room_id}:{server_name}");
 	}
-	OwnedRoomId::parse(room_id)
+
+	let server_name = services.globals.server_name();
+	let full_room_id = format!("!{custom_room_id}:{server_name}");
+
+	OwnedRoomId::parse(full_room_id)
 		.map_err(Into::into)
-		.and_then(|full_room_id| {
+		.inspect(|full_room_id| debug_info!(?full_room_id, "Full custom room ID"))
-			if full_room_id
-				.server_name()
-				.expect("failed to extract server name from room ID")
-				!= server_name
-			{
-				Err(Error::BadRequest(
-					ErrorKind::InvalidParam,
-					"Custom room ID must be on this server.",
-				))
-			} else {
-				Ok(full_room_id)
-			}
-		})
-		.inspect(|full_room_id| {
-			debug_info!(?full_room_id, "Full custom room ID");
-		})
 		.inspect_err(|e| warn!(?e, ?custom_room_id, "Failed to create room with custom room ID",))
 }

src/api/client/space.rs

@@ -121,7 +121,9 @@ where
 					.map(|(key, val)| (key, val.collect()))
 					.collect();
 
-				if !populate {
+				if populate {
+					rooms.push(summary_to_chunk(summary.clone()));
+				} else {
 					children = children
 						.iter()
 						.rev()
@@ -144,10 +146,8 @@ where
 						.collect();
 				}
 
-				if populate {
+				if queue.is_empty() && children.is_empty() {
-					rooms.push(summary_to_chunk(summary.clone()));
+					break;
-				} else if queue.is_empty() && children.is_empty() {
-					return Err!(Request(InvalidParam("Room IDs in token were not found.")));
 				}
 
 				parents.insert(current_room.clone());

src/api/router/auth.rs

@@ -306,7 +306,7 @@ async fn auth_server(
 }
 
 fn auth_server_checks(services: &Services, x_matrix: &XMatrix) -> Result<()> {
-	if !services.config.allow_federation {
+	if !services.server.config.allow_federation {
 		return Err!(Config("allow_federation", "Federation is disabled."));
 	}
 
@@ -316,7 +316,11 @@ fn auth_server_checks(services: &Services, x_matrix: &XMatrix) -> Result<()> {
 	}
 
 	let origin = &x_matrix.origin;
-	if services.moderation.is_remote_server_forbidden(origin) {
+	if services
+		.config
+		.forbidden_remote_server_names
+		.is_match(origin.host())
+	{
 		return Err!(Request(Forbidden(debug_warn!(
 			"Federation requests from {origin} denied."
 		))));

src/api/server/invite.rs

@@ -37,14 +37,19 @@ pub(crate) async fn create_invite_route(
 	}
 
 	if let Some(server) = body.room_id.server_name() {
-		if services.moderation.is_remote_server_forbidden(server) {
+		if services
+			.config
+			.forbidden_remote_server_names
+			.is_match(server.host())
+		{
 			return Err!(Request(Forbidden("Server is banned on this homeserver.")));
 		}
 	}
 
 	if services
-		.moderation
+		.config
-		.is_remote_server_forbidden(body.origin())
+		.forbidden_remote_server_names
+		.is_match(body.origin().host())
 	{
 		warn!(
 			"Received federated/remote invite from banned server {} for room ID {}. Rejecting.",

src/api/server/make_join.rs

@@ -42,8 +42,9 @@ pub(crate) async fn create_join_event_template_route(
 		.await?;
 
 	if services
-		.moderation
+		.config
-		.is_remote_server_forbidden(body.origin())
+		.forbidden_remote_server_names
+		.is_match(body.origin().host())
 	{
 		warn!(
 			"Server {} for remote user {} tried joining room ID {} which has a server name that \
@@ -56,7 +57,11 @@ pub(crate) async fn create_join_event_template_route(
 	}
 
 	if let Some(server) = body.room_id.server_name() {
-		if services.moderation.is_remote_server_forbidden(server) {
+		if services
+			.config
+			.forbidden_remote_server_names
+			.is_match(server.host())
+		{
 			return Err!(Request(Forbidden(warn!(
 				"Room ID server name {server} is banned on this homeserver."
 			))));

src/api/server/make_knock.rs

@@ -33,8 +33,9 @@ pub(crate) async fn create_knock_event_template_route(
 		.await?;
 
 	if services
-		.moderation
+		.config
-		.is_remote_server_forbidden(body.origin())
+		.forbidden_remote_server_names
+		.is_match(body.origin().host())
 	{
 		warn!(
 			"Server {} for remote user {} tried knocking room ID {} which has a server name \
@@ -47,7 +48,11 @@ pub(crate) async fn create_knock_event_template_route(
 	}
 
 	if let Some(server) = body.room_id.server_name() {
-		if services.moderation.is_remote_server_forbidden(server) {
+		if services
+			.config
+			.forbidden_remote_server_names
+			.is_match(server.host())
+		{
 			return Err!(Request(Forbidden("Server is banned on this homeserver.")));
 		}
 	}

src/api/server/send_join.rs

@@ -268,8 +268,9 @@ pub(crate) async fn create_join_event_v1_route(
 	body: Ruma<create_join_event::v1::Request>,
 ) -> Result<create_join_event::v1::Response> {
 	if services
-		.moderation
+		.config
-		.is_remote_server_forbidden(body.origin())
+		.forbidden_remote_server_names
+		.is_match(body.origin().host())
 	{
 		warn!(
 			"Server {} tried joining room ID {} through us who has a server name that is \
@@ -281,7 +282,11 @@ pub(crate) async fn create_join_event_v1_route(
 	}
 
 	if let Some(server) = body.room_id.server_name() {
-		if services.moderation.is_remote_server_forbidden(server) {
+		if services
+			.config
+			.forbidden_remote_server_names
+			.is_match(server.host())
+		{
 			warn!(
 				"Server {} tried joining room ID {} through us which has a server name that is \
 				 globally forbidden. Rejecting.",
@@ -309,14 +314,19 @@ pub(crate) async fn create_join_event_v2_route(
 	body: Ruma<create_join_event::v2::Request>,
 ) -> Result<create_join_event::v2::Response> {
 	if services
-		.moderation
+		.config
-		.is_remote_server_forbidden(body.origin())
+		.forbidden_remote_server_names
+		.is_match(body.origin().host())
 	{
 		return Err!(Request(Forbidden("Server is banned on this homeserver.")));
 	}
 
 	if let Some(server) = body.room_id.server_name() {
-		if services.moderation.is_remote_server_forbidden(server) {
+		if services
+			.config
+			.forbidden_remote_server_names
+			.is_match(server.host())
+		{
 			warn!(
 				"Server {} tried joining room ID {} through us which has a server name that is \
 				 globally forbidden. Rejecting.",

src/api/server/send_knock.rs

@@ -26,8 +26,9 @@ pub(crate) async fn create_knock_event_v1_route(
 	body: Ruma<send_knock::v1::Request>,
 ) -> Result<send_knock::v1::Response> {
 	if services
-		.moderation
+		.config
-		.is_remote_server_forbidden(body.origin())
+		.forbidden_remote_server_names
+		.is_match(body.origin().host())
 	{
 		warn!(
 			"Server {} tried knocking room ID {} who has a server name that is globally \
@@ -39,7 +40,11 @@ pub(crate) async fn create_knock_event_v1_route(
 	}
 
 	if let Some(server) = body.room_id.server_name() {
-		if services.moderation.is_remote_server_forbidden(server) {
+		if services
+			.config
+			.forbidden_remote_server_names
+			.is_match(server.host())
+		{
 			warn!(
 				"Server {} tried knocking room ID {} which has a server name that is globally \
 				 forbidden. Rejecting.",

src/core/config/mod.rs

@@ -160,14 +160,6 @@ pub struct Config {
 	#[serde(default = "default_new_user_displayname_suffix")]
 	pub new_user_displayname_suffix: String,
 
-	/// If enabled, conduwuit will send a simple GET request periodically to
-	/// `https://continuwuity.org/.well-known/continuwuity/announcements` for any new
-	/// announcements or major updates. This is not an update check endpoint.
-	///
-	/// default: true
-	#[serde(alias = "allow_check_for_updates", default = "true_fn")]
-	pub allow_announcements_check: bool,
-
 	/// Set this to any float value to multiply conduwuit's in-memory LRU caches
 	/// with such as "auth_chain_cache_capacity".
 	///
@@ -1132,9 +1124,9 @@ pub struct Config {
 	pub rocksdb_compaction_ioprio_idle: bool,
 
 	/// Enables RocksDB compaction. You should never ever have to set this
-	/// option to false. If you for some reason find yourself needing to use
+	/// option to false. If you for some reason find yourself needing to use this
-	/// this option as part of troubleshooting or a bug, please reach out to us
+	/// option as part of troubleshooting or a bug, please reach out to us in
-	/// in the conduwuit Matrix room with information and details.
+	/// the conduwuit Matrix room with information and details.
 	///
 	/// Disabling compaction will lead to a significantly bloated and
 	/// explosively large database, gradually poor performance, unnecessarily
@@ -1359,38 +1351,6 @@ pub struct Config {
 	#[serde(default)]
 	pub prune_missing_media: bool,
 
-	/// List of forbidden server names via regex patterns that we will block
-	/// incoming AND outgoing federation with, and block client room joins /
-	/// remote user invites.
-	///
-	/// Note that your messages can still make it to forbidden servers through
-	/// backfilling. Events we receive from forbidden servers via backfill
-	/// from servers we *do* federate with will be stored in the database.
-	///
-	/// This check is applied on the room ID, room alias, sender server name,
-	/// sender user's server name, inbound federation X-Matrix origin, and
-	/// outbound federation handler.
-	///
-	/// You can set this to ["*"] to block all servers by default, and then
-	/// use `allowed_remote_server_names` to allow only specific servers.
-	///
-	/// example: ["badserver\\.tld$", "badphrase", "19dollarfortnitecards"]
-	///
-	/// default: []
-	#[serde(default, with = "serde_regex")]
-	pub forbidden_remote_server_names: RegexSet,
-
-	/// List of allowed server names via regex patterns that we will allow,
-	/// regardless of if they match `forbidden_remote_server_names`.
-	///
-	/// This option has no effect if `forbidden_remote_server_names` is empty.
-	///
-	/// example: ["goodserver\\.tld$", "goodphrase"]
-	///
-	/// default: []
-	#[serde(default, with = "serde_regex")]
-	pub allowed_remote_server_names: RegexSet,
-
 	/// Vector list of regex patterns of server names that conduwuit will refuse
 	/// to download remote media from.
 	///
@@ -1400,6 +1360,22 @@ pub struct Config {
 	#[serde(default, with = "serde_regex")]
 	pub prevent_media_downloads_from: RegexSet,
 
+	/// List of forbidden server names via regex patterns that we will block
+	/// incoming AND outgoing federation with, and block client room joins /
+	/// remote user invites.
+	///
+	/// This check is applied on the room ID, room alias, sender server name,
+	/// sender user's server name, inbound federation X-Matrix origin, and
+	/// outbound federation handler.
+	///
+	/// Basically "global" ACLs.
+	///
+	/// example: ["badserver\.tld$", "badphrase", "19dollarfortnitecards"]
+	///
+	/// default: []
+	#[serde(default, with = "serde_regex")]
+	pub forbidden_remote_server_names: RegexSet,
+
 	/// List of forbidden server names via regex patterns that we will block all
 	/// outgoing federated room directory requests for. Useful for preventing
 	/// our users from wandering into bad servers or spaces.
@@ -1410,31 +1386,6 @@ pub struct Config {
 	#[serde(default, with = "serde_regex")]
 	pub forbidden_remote_room_directory_server_names: RegexSet,
 
-	/// Vector list of regex patterns of server names that conduwuit will not
-	/// send messages to the client from.
-	///
-	/// Note that there is no way for clients to receive messages once a server
-	/// has become unignored without doing a full sync. This is a protocol
-	/// limitation with the current sync protocols. This means this is somewhat
-	/// of a nuclear option.
-	///
-	/// example: ["reallybadserver\.tld$", "reallybadphrase",
-	/// "69dollarfortnitecards"]
-	///
-	/// default: []
-	#[serde(default, with = "serde_regex")]
-	pub ignore_messages_from_server_names: RegexSet,
-
-	/// Send messages from users that the user has ignored to the client.
-	///
-	/// There is no way for clients to receive messages sent while a user was
-	/// ignored without doing a full sync. This is a protocol limitation with
-	/// the current sync protocols. Disabling this option will move
-	/// responsibility of ignoring messages to the client, which can avoid this
-	/// limitation.
-	#[serde(default)]
-	pub send_messages_from_ignored_users_to_client: bool,
-
 	/// Vector list of IPv4 and IPv6 CIDR ranges / subnets *in quotes* that you
 	/// do not want conduwuit to send outbound requests to. Defaults to
 	/// RFC1918, unroutable, loopback, multicast, and testnet addresses for
@@ -1993,7 +1944,7 @@ impl Config {
 		let mut addrs = Vec::with_capacity(
 			self.get_bind_hosts()
 				.len()
-				.saturating_mul(self.get_bind_ports().len()),
+				.saturating_add(self.get_bind_ports().len()),
 		);
 		for host in &self.get_bind_hosts() {
 			for port in &self.get_bind_ports() {

src/core/matrix/state_res/event_auth.rs

@@ -38,7 +38,7 @@ struct GetMembership {
 	membership: MembershipState,
 }
 
-#[derive(Deserialize, Debug)]
+#[derive(Deserialize)]
 struct RoomMemberContentFields {
 	membership: Option<Raw<MembershipState>>,
 	join_authorised_via_users_server: Option<Raw<OwnedUserId>>,
@@ -149,9 +149,9 @@ where
 	Incoming: Event + Send + Sync,
 {
 	debug!(
-		event_id = format!("{}", incoming_event.event_id()),
+		"auth_check beginning for {} ({})",
-		event_type = format!("{}", incoming_event.event_type()),
+		incoming_event.event_id(),
-		"auth_check beginning"
+		incoming_event.event_type()
 	);
 
 	// [synapse] check that all the events are in the same room as `incoming_event`
@@ -383,15 +383,10 @@ where
 
 	let sender_membership_event_content: RoomMemberContentFields =
 		from_json_str(sender_member_event.content().get())?;
-	let Some(membership_state) = sender_membership_event_content.membership else {
+	let membership_state = sender_membership_event_content
-		warn!(
+		.membership
-			sender_membership_event_content = format!("{sender_membership_event_content:?}"),
+		.expect("we should test before that this field exists")
-			event_id = format!("{}", incoming_event.event_id()),
+		.deserialize()?;
-			"Sender membership event content missing membership field"
-		);
-		return Err(Error::InvalidPdu("Missing membership field".to_owned()));
-	};
-	let membership_state = membership_state.deserialize()?;
 
 	if !matches!(membership_state, MembershipState::Join) {
 		warn!("sender's membership is not join");

src/main/Cargo.toml

@@ -36,7 +36,6 @@ assets = [
 
 [features]
 default = [
-    "blurhashing",
 	"brotli_compression",
 	"element_hacks",
 	"gzip_compression",

src/router/Cargo.toml

@@ -114,11 +114,11 @@ ruma.workspace = true
 rustls.workspace = true
 rustls.optional = true
 sentry.optional = true
-sentry.workspace = true
 sentry-tower.optional = true
 sentry-tower.workspace = true
 sentry-tracing.optional = true
 sentry-tracing.workspace = true
+sentry.workspace = true
 serde_json.workspace = true
 tokio.workspace = true
 tower.workspace = true

src/service/admin/grant.rs

@@ -126,7 +126,7 @@ pub async fn make_user_admin(&self, user_id: &UserId) -> Result {
 
 	if self.services.server.config.admin_room_notices {
 		let welcome_message = String::from(
-			"## Thank you for trying out Continuwuity!\n\nContinuwuity is a hard fork of conduwuit, which is also a hard fork of Conduit, currently in Beta. The Beta status initially was inherited from Conduit, however overtime this Beta status is rapidly becoming less and less relevant as our codebase significantly diverges more and more. Continuwuity is quite stable and very usable as a daily driver and for a low-medium sized homeserver. There is still a lot of more work to be done, but it is in a far better place than the project was in early 2024.\n\nHelpful links:\n> Source code: https://forgejo.ellis.link/continuwuation/continuwuity\n> Documentation: https://continuwuity.org/\n> Report issues: https://forgejo.ellis.link/continuwuation/continuwuity/issues\n\nFor a list of available commands, send the following message in this room: `!admin --help`\n\nHere are some rooms you can join (by typing the command into your client) -\n\nContinuwuity space: `/join #space:continuwuity.org`\nContinuwuity main room (Ask questions and get notified on updates): `/join #continuwuity:continuwuity.org`\nContinuwuity offtopic room: `/join #offtopic:continuwuity.org`",
+			"## Thank you for trying out conduwuit!\n\nconduwuit is technically a hard fork of Conduit, which is in Beta. The Beta status initially was inherited from Conduit, however overtime this Beta status is rapidly becoming less and less relevant as our codebase significantly diverges more and more. conduwuit is quite stable and very usable as a daily driver and for a low-medium sized homeserver. There is still a lot of more work to be done, but it is in a far better place than the project was in early 2024.\n\nHelpful links:\n> GitHub Repo: https://github.com/girlbossceo/conduwuit\n> Documentation: https://conduwuit.puppyirl.gay/\n> Report issues: https://github.com/girlbossceo/conduwuit/issues\n\nFor a list of available commands, send the following message in this room: `!admin --help`\n\nHere are some rooms you can join (by typing the command into your client) -\n\nconduwuit space: `/join #conduwuit-space:puppygock.gay`\nconduwuit main room (Ask questions and get notified on updates): `/join #conduwuit:puppygock.gay`\nconduwuit offtopic room: `/join #conduwuit-offtopic:puppygock.gay`",
 		);
 
 		// Send welcome message

src/service/announcements/mod.rs

@@ -1,169 +0,0 @@
-//! # Announcements service
-//!
-//! This service is responsible for checking for announcements and sending them
-//! to the client.
-//!
-//! It is used to send announcements to the admin room and logs.
-//! Annuncements are stored in /docs/static/announcements right now.
-//! The highest seen announcement id is stored in the database. When the
-//! announcement check is run, all announcements with an ID higher than those
-//! seen before are printed to the console and sent to the admin room.
-//!
-//! Old announcements should be deleted to avoid spamming the room on first
-//! install.
-//!
-//! Announcements are displayed as markdown in the admin room, but plain text in
-//! the console.
-
-use std::{sync::Arc, time::Duration};
-
-use async_trait::async_trait;
-use conduwuit::{Result, Server, debug, info, warn};
-use database::{Deserialized, Map};
-use ruma::events::room::message::RoomMessageEventContent;
-use serde::Deserialize;
-use tokio::{
-	sync::Notify,
-	time::{MissedTickBehavior, interval},
-};
-
-use crate::{Dep, admin, client, globals};
-
-pub struct Service {
-	interval: Duration,
-	interrupt: Notify,
-	db: Arc<Map>,
-	services: Services,
-}
-
-struct Services {
-	admin: Dep<admin::Service>,
-	client: Dep<client::Service>,
-	globals: Dep<globals::Service>,
-	server: Arc<Server>,
-}
-
-#[derive(Debug, Deserialize)]
-struct CheckForAnnouncementsResponse {
-	announcements: Vec<CheckForAnnouncementsResponseEntry>,
-}
-
-#[derive(Debug, Deserialize)]
-struct CheckForAnnouncementsResponseEntry {
-	id: u64,
-	date: Option<String>,
-	message: String,
-}
-
-const CHECK_FOR_ANNOUNCEMENTS_URL: &str =
-	"https://continuwuity.org/.well-known/continuwuity/announcements";
-const CHECK_FOR_ANNOUNCEMENTS_INTERVAL: u64 = 7200; // 2 hours
-const LAST_CHECK_FOR_ANNOUNCEMENTS_ID: &[u8; 25] = b"last_seen_announcement_id";
-// In conduwuit, this was under b"a"
-
-#[async_trait]
-impl crate::Service for Service {
-	fn build(args: crate::Args<'_>) -> Result<Arc<Self>> {
-		Ok(Arc::new(Self {
-			interval: Duration::from_secs(CHECK_FOR_ANNOUNCEMENTS_INTERVAL),
-			interrupt: Notify::new(),
-			db: args.db["global"].clone(),
-			services: Services {
-				globals: args.depend::<globals::Service>("globals"),
-				admin: args.depend::<admin::Service>("admin"),
-				client: args.depend::<client::Service>("client"),
-				server: args.server.clone(),
-			},
-		}))
-	}
-
-	#[tracing::instrument(skip_all, name = "announcements", level = "debug")]
-	async fn worker(self: Arc<Self>) -> Result<()> {
-		if !self.services.globals.allow_announcements_check() {
-			debug!("Disabling announcements check");
-			return Ok(());
-		}
-
-		let mut i = interval(self.interval);
-		i.set_missed_tick_behavior(MissedTickBehavior::Delay);
-		i.reset_after(self.interval);
-		loop {
-			tokio::select! {
-				() = self.interrupt.notified() => break,
-				_ = i.tick() => (),
-			}
-
-			if let Err(e) = self.check().await {
-				warn!(%e, "Failed to check for announcements");
-			}
-		}
-
-		Ok(())
-	}
-
-	fn interrupt(&self) { self.interrupt.notify_waiters(); }
-
-	fn name(&self) -> &str { crate::service::make_name(std::module_path!()) }
-}
-
-impl Service {
-	#[tracing::instrument(skip_all)]
-	async fn check(&self) -> Result<()> {
-		debug_assert!(self.services.server.running(), "server must not be shutting down");
-
-		let response = self
-			.services
-			.client
-			.default
-			.get(CHECK_FOR_ANNOUNCEMENTS_URL)
-			.send()
-			.await?
-			.text()
-			.await?;
-
-		let response = serde_json::from_str::<CheckForAnnouncementsResponse>(&response)?;
-		for announcement in &response.announcements {
-			if announcement.id > self.last_check_for_announcements_id().await {
-				self.handle(announcement).await;
-				self.update_check_for_announcements_id(announcement.id);
-			}
-		}
-
-		Ok(())
-	}
-
-	#[tracing::instrument(skip_all)]
-	async fn handle(&self, announcement: &CheckForAnnouncementsResponseEntry) {
-		if let Some(date) = &announcement.date {
-			info!("[announcements] {date} {:#}", announcement.message);
-		} else {
-			info!("[announcements] {:#}", announcement.message);
-		}
-
-		self.services
-			.admin
-			.send_message(RoomMessageEventContent::text_markdown(format!(
-				"### New announcement{}\n\n{}",
-				announcement
-					.date
-					.as_ref()
-					.map_or_else(String::new, |date| format!(" - `{date}`")),
-				announcement.message
-			)))
-			.await
-			.ok();
-	}
-
-	#[inline]
-	pub fn update_check_for_announcements_id(&self, id: u64) {
-		self.db.raw_put(LAST_CHECK_FOR_ANNOUNCEMENTS_ID, id);
-	}
-
-	pub async fn last_check_for_announcements_id(&self) -> u64 {
-		self.db
-			.get(LAST_CHECK_FOR_ANNOUNCEMENTS_ID)
-			.await
-			.deserialized()
-			.unwrap_or(0_u64)
-	}
-}

src/service/federation/execute.rs

@@ -64,7 +64,13 @@ where
 		return Err!(Config("allow_federation", "Federation is disabled."));
 	}
 
-	if self.services.moderation.is_remote_server_forbidden(dest) {
+	if self
+		.services
+		.server
+		.config
+		.forbidden_remote_server_names
+		.is_match(dest.host())
+	{
 		return Err!(Request(Forbidden(debug_warn!("Federation with {dest} is not allowed."))));
 	}
 

src/service/federation/mod.rs

@@ -4,7 +4,7 @@ use std::sync::Arc;
 
 use conduwuit::{Result, Server};
 
-use crate::{Dep, client, moderation, resolver, server_keys};
+use crate::{Dep, client, resolver, server_keys};
 
 pub struct Service {
 	services: Services,
@@ -15,7 +15,6 @@ struct Services {
 	client: Dep<client::Service>,
 	resolver: Dep<resolver::Service>,
 	server_keys: Dep<server_keys::Service>,
-	moderation: Dep<moderation::Service>,
 }
 
 impl crate::Service for Service {
@@ -26,7 +25,6 @@ impl crate::Service for Service {
 				client: args.depend::<client::Service>("client"),
 				resolver: args.depend::<resolver::Service>("resolver"),
 				server_keys: args.depend::<server_keys::Service>("server_keys"),
-				moderation: args.depend::<moderation::Service>("moderation"),
 			},
 		}))
 	}

src/service/globals/mod.rs

@@ -127,10 +127,6 @@ impl Service {
 		&self.server.config.new_user_displayname_suffix
 	}
 
-	pub fn allow_announcements_check(&self) -> bool {
-		self.server.config.allow_announcements_check
-	}
-
 	pub fn trusted_servers(&self) -> &[OwnedServerName] { &self.server.config.trusted_servers }
 
 	pub fn turn_password(&self) -> &String { &self.server.config.turn_password }

src/service/media/mod.rs

@@ -22,7 +22,7 @@ use tokio::{
 
 use self::data::{Data, Metadata};
 pub use self::thumbnail::Dim;
-use crate::{Dep, client, globals, moderation, sending};
+use crate::{Dep, client, globals, sending};
 
 #[derive(Debug)]
 pub struct FileMeta {
@@ -42,7 +42,6 @@ struct Services {
 	client: Dep<client::Service>,
 	globals: Dep<globals::Service>,
 	sending: Dep<sending::Service>,
-	moderation: Dep<moderation::Service>,
 }
 
 /// generated MXC ID (`media-id`) length
@@ -65,7 +64,6 @@ impl crate::Service for Service {
 				client: args.depend::<client::Service>("client"),
 				globals: args.depend::<globals::Service>("globals"),
 				sending: args.depend::<sending::Service>("sending"),
-				moderation: args.depend::<moderation::Service>("moderation"),
 			},
 		}))
 	}

src/service/media/remote.rs

@@ -423,8 +423,16 @@ pub async fn fetch_remote_content_legacy(
 fn check_fetch_authorized(&self, mxc: &Mxc<'_>) -> Result<()> {
 	if self
 		.services
-		.moderation
+		.server
-		.is_remote_server_media_downloads_forbidden(mxc.server_name)
+		.config
+		.prevent_media_downloads_from
+		.is_match(mxc.server_name.host())
+		|| self
+			.services
+			.server
+			.config
+			.forbidden_remote_server_names
+			.is_match(mxc.server_name.host())
 	{
 		// we'll lie to the client and say the blocked server's media was not found and
 		// log. the client has no way of telling anyways so this is a security bonus.

src/service/mod.rs

@@ -8,7 +8,6 @@ pub mod services;
 
 pub mod account_data;
 pub mod admin;
-pub mod announcements;
 pub mod appservice;
 pub mod client;
 pub mod config;
@@ -17,7 +16,6 @@ pub mod federation;
 pub mod globals;
 pub mod key_backups;
 pub mod media;
-pub mod moderation;
 pub mod presence;
 pub mod pusher;
 pub mod resolver;

src/service/moderation.rs

@@ -1,93 +0,0 @@
-use std::sync::Arc;
-
-use conduwuit::{Result, implement};
-use ruma::ServerName;
-
-use crate::{Dep, config};
-
-pub struct Service {
-	services: Services,
-}
-
-struct Services {
-	// pub server: Arc<Server>,
-	pub config: Dep<config::Service>,
-}
-
-impl crate::Service for Service {
-	fn build(args: crate::Args<'_>) -> Result<Arc<Self>> {
-		Ok(Arc::new(Self {
-			services: Services {
-				// server: args.server.clone(),
-				config: args.depend::<config::Service>("config"),
-			},
-		}))
-	}
-
-	fn name(&self) -> &str { crate::service::make_name(std::module_path!()) }
-}
-
-#[implement(Service)]
-#[must_use]
-pub fn is_remote_server_ignored(&self, server_name: &ServerName) -> bool {
-	// We must never block federating with ourselves
-	if server_name == self.services.config.server_name {
-		return false;
-	}
-
-	self.services
-		.config
-		.ignore_messages_from_server_names
-		.is_match(server_name.host())
-}
-
-#[implement(Service)]
-#[must_use]
-pub fn is_remote_server_forbidden(&self, server_name: &ServerName) -> bool {
-	// We must never block federating with ourselves
-	if server_name == self.services.config.server_name {
-		return false;
-	}
-
-	// Check if server is explicitly allowed
-	if self
-		.services
-		.config
-		.allowed_remote_server_names
-		.is_match(server_name.host())
-	{
-		return false;
-	}
-
-	// Check if server is explicitly forbidden
-	self.services
-		.config
-		.forbidden_remote_server_names
-		.is_match(server_name.host())
-}
-
-#[implement(Service)]
-#[must_use]
-pub fn is_remote_server_room_directory_forbidden(&self, server_name: &ServerName) -> bool {
-	// Forbidden if NOT (allowed is empty OR allowed contains server OR is self)
-	// OR forbidden contains server
-	self.is_remote_server_forbidden(server_name)
-		|| self
-			.services
-			.config
-			.forbidden_remote_room_directory_server_names
-			.is_match(server_name.host())
-}
-
-#[implement(Service)]
-#[must_use]
-pub fn is_remote_server_media_downloads_forbidden(&self, server_name: &ServerName) -> bool {
-	// Forbidden if NOT (allowed is empty OR allowed contains server OR is self)
-	// OR forbidden contains server
-	self.is_remote_server_forbidden(server_name)
-		|| self
-			.services
-			.config
-			.prevent_media_downloads_from
-			.is_match(server_name.host())
-}

src/service/services.rs

@@ -10,10 +10,9 @@ use futures::{Stream, StreamExt, TryStreamExt};
 use tokio::sync::Mutex;
 
 use crate::{
-	account_data, admin, announcements, appservice, client, config, emergency, federation,
+	account_data, admin, appservice, client, config, emergency, federation, globals, key_backups,
-	globals, key_backups,
 	manager::Manager,
-	media, moderation, presence, pusher, resolver, rooms, sending, server_keys, service,
+	media, presence, pusher, resolver, rooms, sending, server_keys, service,
 	service::{Args, Map, Service},
 	sync, transaction_ids, uiaa, users,
 };
@@ -39,8 +38,6 @@ pub struct Services {
 	pub transaction_ids: Arc<transaction_ids::Service>,
 	pub uiaa: Arc<uiaa::Service>,
 	pub users: Arc<users::Service>,
-	pub moderation: Arc<moderation::Service>,
-	pub announcements: Arc<announcements::Service>,
 
 	manager: Mutex<Option<Arc<Manager>>>,
 	pub(crate) service: Arc<Map>,
@@ -107,8 +104,6 @@ impl Services {
 			transaction_ids: build!(transaction_ids::Service),
 			uiaa: build!(uiaa::Service),
 			users: build!(users::Service),
-			moderation: build!(moderation::Service),
-			announcements: build!(announcements::Service),
 
 			manager: Mutex::new(None),
 			service,

src/service/users/mod.rs

@@ -577,7 +577,7 @@ impl Service {
 
 			self.db
 				.userid_usersigningkeyid
-				.raw_put(user_id, user_signing_key_key);
+				.put(user_id, user_signing_key_key);
 		}
 
 		if notify {