851 changed files with 26339 additions and 175399 deletions
--- a/.buildpacks
+++ b/.buildpacks
@ -0,0 +1 @@
+https://github.com/hashnuke/heroku-buildpack-elixir  
--- a/.formatter.exs
+++ b/.formatter.exs
@ -1,14 +1,3 @@
 [
-  import_deps: [:ecto, :ecto_sql, :phoenix],
-  subdirectories: ["priv/*/migrations"],
-  plugins: [Phoenix.LiveView.HTMLFormatter],
-  inputs: [
-    "mix.exs",
-    "*.{heex,ex,exs}",
-    "{config,lib,test}/**/*.{heex,ex,exs}",
-    "priv/*/seeds.exs",
-    "priv/repo/migrations/*.exs",
-    "priv/repo/optional_migrations/**/*.exs",
-    "priv/scrubbers/*.ex"
-  ]
+  inputs: ["mix.exs", "{config,lib,test}/**/*.{ex,exs}", "priv/repo/migrations/*.exs", "priv/repo/optional_migrations/**/*.exs", "priv/scrubbers/*.ex"]
 ]
--- a/.gitattributes
+++ b/.gitattributes
@ -1,4 +1,10 @@
 *.ex diff=elixir
 *.exs diff=elixir

-*.css diff=css
+priv/static/instance/static.css diff=css
+
+# Most of js/css files included in the repo are minified bundles,
+#   and we don't want to search/diff those as text files.
+*.js binary
+*.js.map binary
+*.css binary
--- a/.gitea/issue_template/bug.yml
+++ b/.gitea/issue_template/bug.yml
@ -1,87 +0,0 @@
-name: "Bug report"
-about: "Something isn't working as expected"
-title: "[bug] "
-labels:
- bug
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to file this bug report! Please try to be as specific and detailed as you can, so we can track down the issue and fix it as soon as possible.
-
-        # General information
-  - type: dropdown
-    id: installation
-    attributes:
-      label: "Your setup"
-      description: "What sort of installation are you using?"
-      options:
-        - "OTP"
-        - "From source"
-        - "Docker"
-      validations:
-        required: true
-  - type: input
-    id: setup-details
-    attributes:
-      label: "Extra details"
-      description: "If installing from source or docker, please specify your distro or docker setup."
-      placeholder: "e.g. Alpine Linux edge"
-  - type: input
-    id: version
-    attributes:
-      label: "Version"
-      description: "Which version of Akkoma are you running? If running develop, specify the commit hash."
-      placeholder: "e.g. 2022.11, 4e4bd248"
-  - type: input
-    id: postgres
-    attributes:
-      label: "PostgreSQL version"
-      placeholder: "14"
-      validations:
-        required: true
-  - type: markdown
-    attributes:
-      value: "# The issue"
-  - type: textarea
-    id: attempt
-    attributes:
-      label: "What were you trying to do?"
-      validations:
-        required: true
-  - type: textarea
-    id: expectation
-    attributes:
-      label: "What did you expect to happen?"
-      validations:
-        required: true
-  - type: textarea
-    id: reality
-    attributes:
-      label: "What actually happened?"
-      validations:
-        required: true
-  - type: textarea
-    id: logs
-    attributes:
-      label: "Logs"
-      description: "Please copy and paste any relevant log output, if applicable."
-      render: shell
-  - type: dropdown
-    id: severity
-    attributes:
-      label: "Severity"
-      description: "Does this issue prevent you from using the software as normal?"
-      options:
-        - "I cannot use the software"
-        - "I cannot use it as easily as I'd like"
-        - "I can manage"
-      validations:
-        required: true
-  - type: checkboxes
-    id: searched
-    attributes:
-      label: "Have you searched for this issue?"
-      description: "Please double-check that your issue is not already being tracked on [the forums](https://meta.akkoma.dev) or [the issue tracker](https://akkoma.dev/AkkomaGang/akkoma/issues)."
-      options:
-        - label: "I have double-checked and have not found this issue mentioned anywhere."
--- a/.gitea/issue_template/feat.yml
+++ b/.gitea/issue_template/feat.yml
@ -1,32 +0,0 @@
-name: "Feature request"
-about: "I'd like something to be added to Akkoma"
-title: "[feat] "
-labels:
- "feature request"
-
-body:
-  - type: markdown
-    attributes:
-      value: "Thanks for taking the time to request a new feature! Please be as concise and clear as you can in your proposal, so we could understand what you're going for."
-  - type: textarea
-    id: idea
-    attributes:
-      label: "The idea"
-      description: "What do you think you should be able to do in Akkoma?"
-      validations:
-        required: true
-  - type: textarea
-    id: reason
-    attributes:
-      label: "The reasoning"
-      description: "Why would this be a worthwhile feature? Does it solve any problems? Have people talked about wanting it?"
-      validations:
-        required: true
-  - type: checkboxes
-    id: searched
-    attributes:
-      label: "Have you searched for this feature request?"
-      description: "Please double-check that your issue is not already being tracked on [the forums](https://meta.akkoma.dev), [the issue tracker](https://akkoma.dev/AkkomaGang/akkoma/issues), or the one for [pleroma-fe](https://akkoma.dev/AkkomaGang/pleroma-fe/issues)."
-      options:
-        - label: "I have double-checked and have not found this feature request mentioned anywhere."
-        - label: "This feature is related to the Akkoma backend specifically, and not pleroma-fe."
--- a/.gitignore
+++ b/.gitignore
@ -73,9 +73,6 @@ pleroma.iml

 # Generated documentation
 docs/site
-docs/venv

 # docker stuff
 docker-db
-*.iml
-docker-compose.override.yml
--- a/.woodpecker/build-amd64.yml
+++ b/.woodpecker/build-amd64.yml
@ -1,9 +1,3 @@
-labels:
-  platform: linux/amd64
-
-depends_on:
-  - test
-
 variables:
  - &scw-secrets
    - SCW_ACCESS_KEY
@ -18,6 +12,8 @@ variables:
      branch:
        - develop
        - stable
+        - refs/tags/v*
+        - refs/tags/stable-*
  - &on-stable
    when:
      event:
@ -25,6 +21,14 @@ variables:
        - tag
      branch:
        - stable
+        - refs/tags/stable-*
+  - &on-point-release
+    when:
+      event:
+        - push
+      branch:
+        - develop
+        - stable
  - &on-pr-open
    when:
      event:
@ -35,10 +39,63 @@ variables:
  - &clean "(rm -rf release || true) && (rm -rf _build || true) && (rm -rf /root/.mix)"
  - &mix-clean "mix deps.clean --all && mix clean"

-steps:
+services:
+  postgres:
+    image: postgres:13
+    when:
+      event:
+        - pull_request
+    environment:
+      POSTGRES_DB: pleroma_test
+      POSTGRES_USER: postgres
+      POSTGRES_PASSWORD: postgres
+
+pipeline:
+  lint:
+    <<: *on-pr-open
+    image: akkoma/ci-base:latest
+    commands:
+    - mix local.hex --force
+    - mix local.rebar --force
+    - mix format --check-formatted
+
+  build:
+    image: akkoma/ci-base:latest
+    <<: *on-pr-open
+    environment:
+      MIX_ENV: test
+      POSTGRES_DB: pleroma_test
+      POSTGRES_USER: postgres
+      POSTGRES_PASSWORD: postgres
+      DB_HOST: postgres
+    commands:
+      - mix local.hex --force
+      - mix local.rebar --force
+      - mix deps.get
+      - mix compile
+
+  test:
+    image: akkoma/ci-base:latest
+    <<: *on-pr-open
+    environment:
+      MIX_ENV: test
+      POSTGRES_DB: pleroma_test
+      POSTGRES_USER: postgres
+      POSTGRES_PASSWORD: postgres
+      DB_HOST: postgres
+    commands:
+    - mix local.hex --force
+    - mix local.rebar --force
+    - mix deps.get
+    - mix compile
+    - mix ecto.drop -f -q
+    - mix ecto.create
+    - mix ecto.migrate
+    - mix test --preload-modules --exclude erratic --exclude federated --max-cases 4
+
  # Canonical amd64
-  debian-bookworm:
-    image: hexpm/elixir:1.15.4-erlang-26.0.2-debian-bookworm-20230612
+  ubuntu22:
+    image: hexpm/elixir:1.13.4-erlang-24.3.4.5-ubuntu-jammy-20220428
    <<: *on-release
    environment:
      MIX_ENV: prod
@ -51,50 +108,50 @@ steps:
      - *tag-build
      - mix deps.get --only prod
      - mix release --path release
+      - zip akkoma-ubuntu-jammy.zip -r release
+
+  release-ubuntu22:
+    image: akkoma/releaser
+    <<: *on-release
+    secrets: *scw-secrets
+    commands:
+      - export SOURCE=akkoma-ubuntu-jammy.zip
+      - export DEST=scaleway:akkoma-updates/$${CI_COMMIT_TAG:-"$CI_COMMIT_BRANCH"}/akkoma-ubuntu-jammy.zip
+      - /bin/sh /entrypoint.sh
+      - export DEST=scaleway:akkoma-updates/$${CI_COMMIT_TAG:-"$CI_COMMIT_BRANCH"}/akkoma-amd64-ubuntu-jammy.zip
+      - /bin/sh /entrypoint.sh
+
+  debian-bullseye:
+    image: hexpm/elixir:1.13.4-erlang-24.3.4.5-debian-bullseye-20220801
+    <<: *on-release
+    environment:
+      MIX_ENV: prod
+      DEBIAN_FRONTEND: noninteractive
+    commands:
+      - apt-get update && apt-get install -y cmake libmagic-dev rclone zip imagemagick libmagic-dev git build-essential gcc make g++ wget
+      - *clean
+      - echo "import Config" > config/prod.secret.exs
+      - *setup-hex
+      - *tag-build
+      - *mix-clean
+      - mix deps.get --only prod
+      - mix release --path release
      - zip akkoma-amd64.zip -r release

-  release-debian-bookworm:
+  release-debian:
    image: akkoma/releaser
    <<: *on-release
    secrets: *scw-secrets
    commands:
      - export SOURCE=akkoma-amd64.zip
-      # AMD64
      - export DEST=scaleway:akkoma-updates/$${CI_COMMIT_TAG:-"$CI_COMMIT_BRANCH"}/akkoma-amd64.zip
      - /bin/sh /entrypoint.sh
-      # Ubuntu jammy (currently compatible)
-      - export DEST=scaleway:akkoma-updates/$${CI_COMMIT_TAG:-"$CI_COMMIT_BRANCH"}/akkoma-amd64-ubuntu-jammy.zip
-      - /bin/sh /entrypoint.sh
-
-  debian-bullseye:
-    image: hexpm/elixir:1.15.4-erlang-26.0.2-debian-bullseye-20230612
-    <<: *on-release
-    environment:
-      MIX_ENV: prod
-      DEBIAN_FRONTEND: noninteractive
-    commands:
-      - apt-get update && apt-get install -y cmake libmagic-dev rclone zip imagemagick libmagic-dev git build-essential g++ wget
-      - *clean
-      - echo "import Config" > config/prod.secret.exs
-      - *setup-hex
-      - *tag-build
-      - mix deps.get --only prod
-      - mix release --path release
-      - zip akkoma-amd64-debian-bullseye.zip -r release
-
-  release-debian-bullseye:
-    image: akkoma/releaser
-    <<: *on-release
-    secrets: *scw-secrets
-    commands:
-      - export SOURCE=akkoma-amd64-debian-bullseye.zip
-      # AMD64
-      - export DEST=scaleway:akkoma-updates/$${CI_COMMIT_TAG:-"$CI_COMMIT_BRANCH"}/akkoma-amd64-debian-bullseye.zip
+      - export DEST=scaleway:akkoma-updates/$${CI_COMMIT_TAG:-"$CI_COMMIT_BRANCH"}/akkoma-debian-stable.zip
      - /bin/sh /entrypoint.sh

  # Canonical amd64-musl
  musl:
-    image: hexpm/elixir:1.15.4-erlang-26.0.2-alpine-3.18.2
+    image: hexpm/elixir:1.13.4-erlang-24.3.4.5-alpine-3.15.6
    <<: *on-stable
    environment:
      MIX_ENV: prod
@ -116,3 +173,25 @@ steps:
      - export SOURCE=akkoma-amd64-musl.zip
      - export DEST=scaleway:akkoma-updates/$${CI_COMMIT_TAG:-"$CI_COMMIT_BRANCH"}/akkoma-amd64-musl.zip
      - /bin/sh /entrypoint.sh
+
+  docs:
+    <<: *on-point-release
+    secrets:
+    - SCW_ACCESS_KEY
+    - SCW_SECRET_KEY
+    - SCW_DEFAULT_ORGANIZATION_ID
+    environment:
+      CI: "true"
+    image: python:3.10-slim
+    commands:
+      - apt-get update && apt-get install -y rclone wget git zip
+      - wget https://github.com/scaleway/scaleway-cli/releases/download/v2.5.1/scaleway-cli_2.5.1_linux_amd64
+      - mv scaleway-cli_2.5.1_linux_amd64 scaleway-cli
+      - chmod +x scaleway-cli
+      - ./scaleway-cli object config install type=rclone
+      - cd docs
+      - pip install -r requirements.txt
+      - mkdocs build
+      - zip -r docs.zip site/*
+      - cd site
+      - rclone copy . scaleway:akkoma-docs/$CI_COMMIT_BRANCH/
--- a/.woodpecker/build-arm64.yml
+++ b/.woodpecker/build-arm64.yml
@ -1,90 +0,0 @@
-labels:
-  platform: linux/aarch64
-
-depends_on:
-  - test
-
-variables:
-  - &scw-secrets
-    - SCW_ACCESS_KEY
-    - SCW_SECRET_KEY
-    - SCW_DEFAULT_ORGANIZATION_ID
-  - &setup-hex "mix local.hex --force && mix local.rebar --force"
-  - &on-release
-    when:
-      event:
-        - push
-        - tag
-      branch:
-        - stable
-        - develop
-  - &on-stable
-    when:
-      event:
-        - push
-        - tag
-      branch:
-        - stable
-  - &on-pr-open
-    when:
-      event:
-        - pull_request
-
-  - &tag-build "export BUILD_TAG=$${CI_COMMIT_TAG:-\"$CI_COMMIT_BRANCH\"} && export PLEROMA_BUILD_BRANCH=$BUILD_TAG"
-
-  - &clean "(rm -rf release || true) && (rm -rf _build || true) && (rm -rf /root/.mix)"
-  - &mix-clean "mix deps.clean --all && mix clean"
-
-steps:
-  # Canonical arm64
-  debian-bookworm:
-    image: hexpm/elixir:1.15.4-erlang-26.0.2-debian-bookworm-20230612
-    <<: *on-release
-    environment:
-      MIX_ENV: prod
-      DEBIAN_FRONTEND: noninteractive
-    commands:
-      - apt-get update && apt-get install -y cmake libmagic-dev rclone zip imagemagick libmagic-dev git build-essential g++ wget
-      - *clean
-      - echo "import Config" > config/prod.secret.exs
-      - *setup-hex
-      - *tag-build
-      - mix deps.get --only prod
-      - mix release --path release
-      - zip akkoma-arm64.zip -r release
-
-  release-debian-bookworm:
-    image: akkoma/releaser:arm64
-    <<: *on-release
-    secrets: *scw-secrets
-    commands:
-      - export SOURCE=akkoma-arm64.zip
-      - export DEST=scaleway:akkoma-updates/$${CI_COMMIT_TAG:-"$CI_COMMIT_BRANCH"}/akkoma-arm64-ubuntu-jammy.zip
-      - /bin/sh /entrypoint.sh
-      - export DEST=scaleway:akkoma-updates/$${CI_COMMIT_TAG:-"$CI_COMMIT_BRANCH"}/akkoma-arm64.zip
-      - /bin/sh /entrypoint.sh
-
-  # Canonical arm64-musl
-  musl:
-    image: hexpm/elixir:1.15.4-erlang-26.0.2-alpine-3.18.2
-    <<: *on-stable
-    environment:
-      MIX_ENV: prod
-    commands:
-      - apk add git gcc g++ musl-dev make cmake file-dev rclone wget zip imagemagick
-      - *clean
-      - *setup-hex
-      - *mix-clean
-      - *tag-build
-      - mix deps.get --only prod
-      - mix release --path release
-      - zip akkoma-arm64-musl.zip -r release
-
-  release-musl:
-    image: akkoma/releaser:arm64
-    <<: *on-stable
-    secrets: *scw-secrets
-    commands:
-      - export SOURCE=akkoma-arm64-musl.zip
-      - export DEST=scaleway:akkoma-updates/$${CI_COMMIT_TAG:-"$CI_COMMIT_BRANCH"}/akkoma-arm64-musl.zip
-      - /bin/sh /entrypoint.sh
--- a/.woodpecker/docs.yml
+++ b/.woodpecker/docs.yml
@ -1,70 +0,0 @@
-labels:
-  platform: linux/amd64
-
-depends_on:
-  - test
-  - build-amd64
-
-variables:
-  - &scw-secrets
-    - SCW_ACCESS_KEY
-    - SCW_SECRET_KEY
-    - SCW_DEFAULT_ORGANIZATION_ID
-  - &setup-hex "mix local.hex --force && mix local.rebar --force"
-  - &on-release
-    when:
-      event:
-        - push
-        - tag
-      branch:
-        - develop
-        - stable
-        - refs/tags/v*
-        - refs/tags/stable-*
-  - &on-stable
-    when:
-      event:
-        - push
-        - tag
-      branch:
-        - stable
-        - refs/tags/stable-*
-  - &on-point-release
-    when:
-      event:
-        - push
-      branch:
-        - develop
-        - stable
-  - &on-pr-open
-    when:
-      event:
-        - pull_request
-
-  - &tag-build "export BUILD_TAG=$${CI_COMMIT_TAG:-\"$CI_COMMIT_BRANCH\"} && export PLEROMA_BUILD_BRANCH=$BUILD_TAG"
-
-  - &clean "(rm -rf release || true) && (rm -rf _build || true) && (rm -rf /root/.mix)"
-  - &mix-clean "mix deps.clean --all && mix clean"
-
-steps:
-  docs:
-    <<: *on-point-release
-    secrets:
-    - SCW_ACCESS_KEY
-    - SCW_SECRET_KEY
-    - SCW_DEFAULT_ORGANIZATION_ID
-    environment:
-      CI: "true"
-    image: python:3.10-slim
-    commands:
-      - apt-get update && apt-get install -y rclone wget git zip
-      - wget https://github.com/scaleway/scaleway-cli/releases/download/v2.5.1/scaleway-cli_2.5.1_linux_amd64
-      - mv scaleway-cli_2.5.1_linux_amd64 scaleway-cli
-      - chmod +x scaleway-cli
-      - ./scaleway-cli object config install type=rclone
-      - cd docs
-      - pip install -r requirements.txt
-      - mkdocs build
-      - zip -r docs.zip site/*
-      - cd site
-      - rclone copy . scaleway:akkoma-docs/$CI_COMMIT_BRANCH/
--- a/.woodpecker/lint.yml
+++ b/.woodpecker/lint.yml
@ -1,56 +0,0 @@
-labels:
-  platform: linux/amd64
-
-variables:
-  - &scw-secrets
-    - SCW_ACCESS_KEY
-    - SCW_SECRET_KEY
-    - SCW_DEFAULT_ORGANIZATION_ID
-  - &setup-hex "mix local.hex --force && mix local.rebar --force"
-  - &on-release
-    when:
-      event:
-        - push
-        - tag
-      branch:
-        - develop
-        - stable
-        - refs/tags/v*
-        - refs/tags/stable-*
-  - &on-stable
-    when:
-      event:
-        - push
-        - tag
-      branch:
-        - stable
-        - refs/tags/stable-*
-  - &on-point-release
-    when:
-      event:
-        - push
-      branch:
-        - develop
-        - stable
-  - &on-pr-open
-    when:
-      event:
-        - pull_request
-
-  - &tag-build "export BUILD_TAG=$${CI_COMMIT_TAG:-\"$CI_COMMIT_BRANCH\"} && export PLEROMA_BUILD_BRANCH=$BUILD_TAG"
-
-  - &clean "(rm -rf release || true) && (rm -rf _build || true) && (rm -rf /root/.mix)"
-  - &mix-clean "mix deps.clean --all && mix clean"
-
-steps:
-  lint:
-    image: akkoma/ci-base:1.16-otp26
-    <<: *on-pr-open
-    environment:
-      MIX_ENV: test
-    commands:
-      - mix local.hex --force
-      - mix local.rebar --force
-      - mix deps.get
-      - mix compile
-      - mix format --check-formatted
--- a/.woodpecker/test.yml
+++ b/.woodpecker/test.yml
@ -1,91 +0,0 @@
-labels:
-  platform: linux/amd64
-
-depends_on:
-  - lint
-
-matrix:
-  ELIXIR_VERSION:
-    - 1.14
-    - 1.15
-    - 1.16
-  OTP_VERSION:
-    - 25
-    - 26
-  include:
-    - ELIXIR_VERSION: 1.16
-      OTP_VERSION: 26
-
-variables:
-  - &scw-secrets
-    - SCW_ACCESS_KEY
-    - SCW_SECRET_KEY
-    - SCW_DEFAULT_ORGANIZATION_ID
-  - &setup-hex "mix local.hex --force && mix local.rebar --force"
-  - &on-release
-    when:
-      event:
-        - push
-        - tag
-      branch:
-        - develop
-        - stable
-        - refs/tags/v*
-        - refs/tags/stable-*
-  - &on-stable
-    when:
-      event:
-        - push
-        - tag
-      branch:
-        - stable
-        - refs/tags/stable-*
-  - &on-point-release
-    when:
-      event:
-        - push
-      branch:
-        - develop
-        - stable
-  - &on-pr-open
-    when:
-      event:
-        - pull_request
-
-  - &tag-build "export BUILD_TAG=$${CI_COMMIT_TAG:-\"$CI_COMMIT_BRANCH\"} && export PLEROMA_BUILD_BRANCH=$BUILD_TAG"
-
-  - &clean "(rm -rf release || true) && (rm -rf _build || true) && (rm -rf /root/.mix)"
-  - &mix-clean "mix deps.clean --all && mix clean"
-
-services:
-  postgres:
-    image: postgres:15
-    when:
-      event:
-        - pull_request
-    environment:
-      POSTGRES_DB: pleroma_test_${ELIXIR_VERSION}_${OTP_VERSION}
-      POSTGRES_USER: postgres
-      POSTGRES_PASSWORD: postgres
-
-steps:
-  test:
-    image: akkoma/ci-base:${ELIXIR_VERSION}-otp${OTP_VERSION}
-    <<: *on-pr-open
-    environment:
-      MIX_ENV: test
-      POSTGRES_DB: pleroma_test_${ELIXIR_VERSION}_${OTP_VERSION}
-      POSTGRES_USER: postgres
-      POSTGRES_PASSWORD: postgres
-      DB_HOST: postgres
-    commands:
-      - mix local.hex --force
-      - mix local.rebar --force
-      - mix deps.get
-      - mix compile
-      - mix ecto.drop -f -q
-      - mix ecto.create
-      - mix ecto.migrate
-      - mkdir -p test/tmp
-      - mix test --preload-modules --exclude erratic --exclude federated --exclude mocked || mix test --failed
-      - mix test --preload-modules --only mocked || mix test --failed
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@ -4,297 +4,13 @@ All notable changes to this project will be documented in this file.

 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).

-## UNRELEASED
-
-## BREAKING
- Minimum PostgreSQL version is raised to 12
- Swagger UI moved from `/akkoma/swaggerui/` to `/pleroma/swaggerui/`
-
-## Added
- Implement [FEP-67ff](https://codeberg.org/fediverse/fep/src/branch/main/fep/67ff/fep-67ff.md) (federation documentation)
- Meilisearch: it is now possible to use separate keys for search and admin actions
- New standalone `prune_orphaned_activities` mix task with configurable batch limit
- The `prune_objects` mix task now accepts a `--limit` parameter for initial object pruning
-
-## Fixed
- Meilisearch: order of results returned from our REST API now actually matches how Meilisearch ranks results
- Emoji are now federated as anonymous objects, fixing issues with
-  some strict servers e.g. rejecting e.g. remote emoji reactions
- AP objects with additional JSON-LD profiles beyond ActivityStreams can now be fetched
- Single-selection polls no longer expose the voter_count; MastoAPI demands it be null
-  and this confused some clients leading to vote distributions >100%
-
-## Changed
- Refactored Rich Media to cache the content in the database. Fetching operations that could block status rendering have been eliminated.
-
-## 2024.04.1 (Security)
-
-## Fixed
- Issue allowing non-owners to use media objects in posts
- Issue allowing use of non-media objects as attachments and crashing timeline rendering
- Issue allowing webfinger spoofing in certain situations
-
-## 2024.04
-
-## Added
- Support for [FEP-fffd](https://codeberg.org/fediverse/fep/src/branch/main/fep/fffd/fep-fffd.md) (proxy objects)
- Verified support for elixir 1.16
- Uploadfilter `Pleroma.Upload.Filter.Exiftool.ReadDescription` returns description values to the FE so they can pre fill the image description field
-  NOTE: this filter MUST be placed before `Exiftool.StripMetadata` to work
-
-## Changed
- Inbound pipeline error handing was modified somewhat, which should lead to less incomprehensible log spam. Hopefully.
- Uploadfilter `Pleroma.Upload.Filter.Exiftool` was replaced by `Pleroma.Upload.Filter.Exiftool.StripMetadata`;
-  the latter strips all non-essential metadata by default but can be configured.
-  To regain the old behaviour of only stripping GPS data set `purge: ["gps:all"]`.
- Uploadfilter `Pleroma.Upload.Filter.Exiftool` has been renamed to `Pleroma.Upload.Filter.Exiftool.StripMetadata`
- MRF.InlineQuotePolicy now prefers to insert display URLs instead of ActivityPub IDs
- Old accounts are no longer listed in WebFinger as aliases; this was breaking spec
-
-## Fixed
- Issue preventing fetching anything from IPv6-only instances
- Issue allowing post content to leak via opengraph tags despite :estrict\_unauthenticated being set
- Move activities no longer operate on stale user data
- Missing definitions in our JSON-LD context
- Issue mangling newlines in code blocks for RSS/Atom feeds
- static\_fe squeezing non-square avatars and emoji
- Issue leading to properly JSON-LD compacted emoji reactions being rejected
- We now use a standard-compliant Accept header when fetching ActivityPub objects
- /api/pleroma/notification\_settings was rejecting body parameters;
-  this also broke changing this setting via akkoma-fe
- Issue leading to Mastodon bot accounts being rejected
- Scope misdetection of remote posts resulting from not recognising
-  JSON-LD-compacted forms of public scope; affected e.g. federation with bovine
- Ratelimits encountered when fetching objects are now respected; 429 responses will cause a backoff when we get one.
-
-## Removed
- ActivityPub Client-To-Server write API endpoints have been disabled;
-  read endpoints are planned to be removed next release unless a clear need is demonstrated
-
-## 2024.03
-
-## Added
- CLI tasks best-effort checking for past abuse of the recent spoofing exploit
- new `:mrf_steal_emoji, :download_unknown_size` option; defaults to `false`
-
-## Changed
- `Pleroma.Upload, :base_url` now MUST be configured explicitly if used;
-  use of the same domain as the instance is **strongly** discouraged
- `:media_proxy, :base_url` now MUST be configured explicitly if used;
-  use of the same domain as the instance is **strongly** discouraged
- StealEmoji:
-  - now uses the pack.json format;
-    existing users must migrate with an out-of-band script (check release notes)
-  - only steals shortcodes recognised as valid
-  - URLs of stolen emoji is no longer predictable
- The `Dedupe` upload filter is now always active;
-  `AnonymizeFilenames` is again opt-in
- received AP data is sanity checked before we attempt to parse it as a user
- Uploads, emoji and media proxy now restrict Content-Type headers to a safe subset
- Akkoma will no longer fetch and parse objects hosted on the same domain
-
-## Fixed
- Critical security issue allowing Akkoma to be used as a vector for
-  (depending on configuration) impersonation of other users or creation
-  of bogus users and posts on the upload domain
- Critical security issue letting Akkoma fall for the above impersonation
-  payloads due to lack of strict id checking
- Critical security issue allowing domains redirect to to pose as the initial domain
-  (e.g. with media proxy's fallback redirects)
- refetched objects can no longer attribute themselves to third-party actors
-  (this had no externally visible effect since actor info is read from the Create activity)
- our litepub JSON-LD schema is now served with the correct content type
- remote APNG attachments are now recognised as images
-
-## Upgrade Notes
-
- As mentioned in "Changed", `Pleroma.Upload, :base_url` **MUST** be configured. Uploads will fail without it.
-  - Akkoma will refuse to start if this is not set.
- Same with media proxy.
-
-## 2024.02
-
-## Added
- Full compatibility with Erlang OTP26
- handling of GET /api/v1/preferences
- Akkoma API is now documented
- ability to auto-approve follow requests from users you are already following
- The SimplePolicy MRF can now strip user backgrounds from selected remote hosts
-
-## Changed
- OTP builds are now built on erlang OTP26
- The base Phoenix framework is now updated to 1.7
- An `outbox` field has been added to actor profiles to comply with AP spec
- User profile backgrounds do now federate with other Akkoma instances and Sharkey
-
-## Fixed
- Documentation issue in which a non-existing nginx file was referenced
- Issue where a bad inbox URL could break federation
- Issue where hashtag rel values would be scrubbed
- Issue where short domains listed in `transparency_obfuscate_domains` were not actually obfuscated
-
-## 2023.08
-
-## Added
-
- Added a new configuration option to the MediaProxy feature that allows the blocking of specific domains from using the media proxy or being explicitly allowed by the Content-Security-Policy.
-  - Please make sure instances you wanted to block media from are not in the MediaProxy `whitelist`, and instead use `blocklist`.
- `OnlyMedia` Upload Filter to simplify restricting uploads to audio, image, and video types
- ARM64 OTP builds
-  - Ubuntu22 builds are available for develop and stable
-  - other distributions are stable only
- Support for Elixir 1.15
-  - 1.14 is still supported
-  - OTP26 is currently "unsupported". It will probably work, but due to the way
-    it handles map ordering, the test suite will not pass for it as yet.
-
-## Changed
-
- Alpine OTP builds are now from alpine 3.18, which is OpenSSLv3 compatible.
-  If you use alpine OTP builds you will have to update your local system.
- Debian OTP builds are now from a base of bookworm, which is OpenSSLv3 compatible.
-  If you use debian OTP builds you will have to update your local system to
-  bookworm (currently: stable).
- Ubuntu and debian builds are compatible again! (for now...)
- Blocks/Mutes now return from max ID to min ID, in line with mastodon.
- The AnonymizeFilename filter is now enabled by default.
-
-## Fixed
-
- Deactivated users can no longer show up in the emoji reaction list
- Embedded posts can no longer bypass `:restrict\_unauthenticated`
- GET/HEAD requests will now work when requesting AWS-based instances.
-
-## Security
-
- Add `no_new_privs` hardening to OpenRC and systemd service files
- XML parsers cannot load any entities (thanks @Mae@is.badat.dev!)
- Reduced permissions of config files and directories, distros requiring greater permissions like group-read need to pre-create the directories
-
-## Removed
-
- Builds for debian oldstable (bullseye)
-  - If you are on oldstable you should NOT attempt to update OTP builds without
-    first updating your machine.
-
-## 2023.05
-
-## Added
- Custom options for users to accept/reject private messages
-  - options: everybody, nobody, people\_i\_follow
- MRF to reject notes from accounts newer than a given age
-  - this will have the side-effect of rejecting legitimate messages if your
-    post gets boosted outside of your local bubble and people your instance
-    does not know about reply to it.
-
-## Fixed
- Support for `streams` public key URIs
- Bookmarks are cleaned up on DB prune now
-
-## Security
- Fixed mediaproxy being a bit of a silly billy
-
-## 2023.04
-
-## Added
- Nodeinfo keys for unauthenticated timeline visibility
- Option to disable federated timeline
- Option to make the bubble timeline publicly accessible
- Ability to swap between installed standard frontends
-  - *mastodon frontends are still not counted as standard frontends due to the complexity in serving them correctly*. 
-
-### Upgrade Notes
- Elixir 1.14 is now required. If your distribution does not package this, you can
-  use [asdf](https://asdf-vm.com/). At time of writing, elixir 1.14.3 / erlang 25.3
-  is confirmed to work.
-
-## 2023.03
-
-## Fixed
- Allowed contentMap to be updated on edit
- Filter creation now accepts expires\_at
-
-### Changed
- Restoring the database from a dump now goes much faster without need for work-arounds
- Misskey reaction matching uses `content` parameter now
-
-### Added
- Extend the mix task `prune_objects` with option `--prune-orphaned-activities` to also prune orphaned activities, allowing to reclaim even more database space
-
-### Removed
- Possibility of using the `style` parameter on `span` elements. This will break certain MFM parameters.
- Option for "default" image description.
-
-## 2023.02
-
-### Added
- Prometheus metrics exporting from `/api/v1/akkoma/metrics`
- Ability to alter http pool size
- Translation of statuses via ArgosTranslate
- Argon2 password hashing
- Ability to "verify" links in profile fields via rel=me
- Mix tasks to dump/load config to/from json for bulk editing
- Followed hashtag list at /api/v1/followed\_tags, API parity with mastodon
- Ability to set posting language in the post form, API parity with mastodon
- Ability to match domains in MRF by a trailing wildcard
-  - Currently supported formats:
-    - `example.com` (implicitly matches `*.example.com`)
-    - `*.example.com`
-    - `example.*` (implicitly matches `*.example.*`)
-
-### Removed
- Non-finch HTTP adapters
- Legacy redirect from /api/pleroma/admin to /api/v1/pleroma/admin
- Legacy redirects from /api/pleroma to /api/v1/pleroma
- :crypt dependency
-
-### Changed
- Return HTTP error 413 when uploading an avatar or banner that's above the configured upload limit instead of a 500.
- Non-admin users now cannot register `admin` scope tokens (not security-critical, they didn't work before, but you _could_ create them)
-  - Admin scopes will be dropped on create
- Rich media will now backoff for 20 minutes after a failure
- Quote posts are now considered as part of the same thread as the post they are quoting
- Extend the mix task `prune_objects` with options to keep more relevant posts
- Simplified HTTP signature processing
- Rich media will now hard-exit after 5 seconds, to prevent timeline hangs
- HTTP Content Security Policy is now far more strict to prevent any potential XSS/CSS leakages
- Follow requests are now paginated, matches mastodon API spec, so use the Link header to paginate.
-
-### Fixed 
- /api/v1/accounts/lookup will now respect restrict\_unauthenticated
- Unknown atoms in the config DB will no longer crash akkoma on boot
-
-### Upgrade notes
- Ensure `config :tesla, :adapter` is either unset, or set to `{Tesla.Adapter.Finch, name: MyFinch}` in your .exs config
- Pleroma-FE will need to be updated to handle the new /api/v1/pleroma endpoints for  custom emoji
-
-## 2022.12
+## Unreleased

 ## Added
 - Config: HTTP timeout options, :pool\_timeout and :receive\_timeout
- Added statistic gathering about instances which do/don't have signed fetches when they request from us
- Ability to set a default post expiry time, after which the post will be deleted. If used in concert with ActivityExpiration MRF, the expiry which comes _sooner_ will be applied.
- Regular task to prune local transient activities
- Task to manually run the transient prune job (pleroma.database prune\_task)
- Ability to follow hashtags
- Option to extend `reject` in MRF-Simple to apply to entire threads, where the originating instance is rejected
- Extra information to failed HTTP requests

 ## Changed
 - MastoAPI: Accept BooleanLike input on `/api/v1/accounts/:id/follow` (fixes follows with mastodon.py)
- Relays from akkoma are now off by default
- NormalizeMarkup MRF is now on by default
- Follow/Block/Mute imports now spin off into *n* tasks to avoid the oban timeout
- Transient activities recieved from remote servers are no longer persisted in the database
- Overhauled static-fe view for logged-out users
- Blocked instances will now not be sent _any_ requests, even fetch ones that would get rejected by MRF anyhow
-
-## Removed
- FollowBotPolicy
- Passing of undo/block into MRF
-
-## Upgrade Notes
- If you have an old instance, you will probably want to run `mix pleroma.database prune_task` in the foreground to catch it up with the history of your instance.

 ## 2022.11

--- a/3
+++ b/3
@ -1,7 +1,6 @@
-FROM hexpm/elixir:1.15.4-erlang-26.0.2-alpine-3.18.2
+FROM hexpm/elixir:1.13.4-erlang-24.3.4.5-alpine-3.15.6

 ENV MIX_ENV=prod
-ENV ERL_EPMD_ADDRESS=127.0.0.1

 ARG HOME=/opt/akkoma

--- a/FEDERATION.md
+++ b/FEDERATION.md
@ -1,42 +0,0 @@
-# Federation
-
-## Supported federation protocols and standards
-
- [ActivityPub](https://www.w3.org/TR/activitypub/) (Server-to-Server)
- [WebFinger](https://webfinger.net/)
- [Http Signatures](https://datatracker.ietf.org/doc/html/draft-cavage-http-signatures)
- [NodeInfo](https://nodeinfo.diaspora.software/)
-
-## Supported FEPs
-
- [FEP-67ff: FEDERATION](https://codeberg.org/fediverse/fep/src/branch/main/fep/67ff/fep-67ff.md)
- [FEP-f1d5: NodeInfo in Fediverse Software](https://codeberg.org/fediverse/fep/src/branch/main/fep/f1d5/fep-f1d5.md)
- [FEP-fffd: Proxy Objects](https://codeberg.org/fediverse/fep/src/branch/main/fep/fffd/fep-fffd.md)
-
-## ActivityPub
-
-Akkoma mostly follows the server-to-server parts of the ActivityPub standard,
-but implements quirks for Mastodon compatibility as well as Mastodon-specific
-and custom extensions.
-
-See our documentation and Mastodon’s federation information
-linked further below for details on these quirks and extensions.
-
-Akkoma does not perform JSON-LD processing.
-
-### Required extensions
-
-#### HTTP Signatures
-All AP S2S POST requests to Akkoma instances MUST be signed.
-Depending on instance configuration the same may be true for GET requests.
-
-## Nodeinfo
-
-Akkoma provides many additional entries in its nodeinfo response,
-see the documentation linked below for details.
-
-## Additional documentation
-
- [Akkoma’s ActivityPub extensions](https://docs.akkoma.dev/develop/development/ap_extensions/)
- [Akkoma’s nodeinfo extensions](https://docs.akkoma.dev/develop/development/nodeinfo_extensions/)
- [Mastodon’s federation requirements](https://github.com/mastodon/mastodon/blob/main/FEDERATION.md)
--- a/7
+++ b/7
@ -0,0 +1,7 @@
+all:	install
+	pipenv run mkdocs build
+
+install:
+	pipenv install
+clean:
+	rm -rf docs
--- a/2
+++ b/2
@ -0,0 +1,2 @@
+web: mix phx.server
+release: mix ecto.migrate
--- a/README.md
+++ b/README.md
@ -54,9 +54,6 @@ If your platform is not supported, or you just want to be able to edit the sourc
 ### Docker
 Docker installation is supported via [this setup](https://docs.akkoma.dev/stable/installation/docker_en/)

-### Packages
-Akkoma is packaged for [YunoHost](https://yunohost.org) and can be found and installed from the [YunoHost app catalogue](https://yunohost.org/#/apps).
-
 ### Compilation Troubleshooting
 If you ever encounter compilation issues during the updating of Akkoma, you can try these commands and see if they fix things:

--- a/SECURITY.md
+++ b/SECURITY.md
@ -1,21 +1,16 @@
-# Akkoma backend security handling
+# Pleroma backend security policy
+
+## Supported versions
+
+Currently, Pleroma offers bugfixes and security patches only for the latest minor release.
+
+| Version | Support 
+|---------| --------
+| 2.2     | Bugfixes and security patches

 ## Reporting a vulnerability

-Please send an email (preferably encrypted) or
-a DM via our IRC to one of the following people:
-
-| Forgejo nick | IRC nick      | Email         | GPG                                     |
-| ------------ | ------------- | ------------- | --------------------------------------- |
-| floatinghost | FloatingGhost | *see GPG key* | https://coffee-and-dreams.uk/pubkey.asc |
-
+Please use confidential issues (tick the "This issue is confidential and should only be visible to team members with at least Reporter access." box when submitting) at our [bugtracker](https://git.pleroma.social/pleroma/pleroma/-/issues/new) for reporting vulnerabilities.
 ## Announcements

-New releases and security issues are announced at
-[meta.akkoma.dev](https://meta.akkoma.dev/c/releases) and
-[@akkoma@ihatebeinga.live](https://ihatebeinga.live/akkoma).
-
-Both also offer RSS feeds
-([meta](https://meta.akkoma.dev/c/releases/7.rss),
-[fedi](https://ihatebeinga.live/users/akkoma.rss))
-so you can keep an eye on it without any accounts.
+New releases are announced at [pleroma.social](https://pleroma.social/announcements/). All security releases are tagged with ["Security"](https://pleroma.social/announcements/tags/security/). You can be notified of them by subscribing to an Atom feed at <https://pleroma.social/announcements/tags/security/feed.xml>. 
--- a/config/benchmark.exs
+++ b/config/benchmark.exs
@ -14,7 +14,7 @@
  method: Pleroma.Captcha.Mock

 # Print only warnings and errors during test
-config :logger, level: :warning
+config :logger, level: :warn

 config :pleroma, :auth, oauth_consumer_strategies: []

--- a/config/config.exs
+++ b/config/config.exs
@ -61,11 +61,12 @@
 # Upload configuration
 config :pleroma, Pleroma.Upload,
  uploader: Pleroma.Uploaders.Local,
-  filters: [],
+  filters: [Pleroma.Upload.Filter.Dedupe],
  link_name: false,
+  proxy_remote: false,
  filename_display_max_length: 30,
-  base_url: nil,
-  allowed_mime_types: ["image", "audio", "video"]
+  default_description: nil,
+  base_url: nil

 config :pleroma, Pleroma.Uploaders.Local, uploads: "uploads"

@ -110,6 +111,17 @@
    "xmpp"
  ]

+websocket_config = [
+  path: "/websocket",
+  serializer: [
+    {Phoenix.Socket.V1.JSONSerializer, "~> 1.0.0"},
+    {Phoenix.Socket.V2.JSONSerializer, "~> 2.0.0"}
+  ],
+  timeout: 60_000,
+  transport_log: false,
+  compress: false
+]
+
 # Configures the endpoint
 config :pleroma, Pleroma.Web.Endpoint,
  url: [host: "localhost"],
@ -119,7 +131,10 @@
      {:_,
       [
         {"/api/v1/streaming", Pleroma.Web.MastodonAPI.WebsocketHandler, []},
-         {:_, Plug.Cowboy.Handler, {Pleroma.Web.Endpoint, []}}
+         {"/websocket", Phoenix.Endpoint.CowboyWebSocket,
+          {Phoenix.Transports.WebSocket,
+           {Pleroma.Web.Endpoint, Pleroma.Web.UserSocket, websocket_config}}},
+         {:_, Phoenix.Endpoint.Cowboy2Handler, {Pleroma.Web.Endpoint, []}}
       ]}
    ]
  ],
@ -148,38 +163,19 @@
  format: "$metadata[$level] $message",
  metadata: [:request_id]

-# ———————————————————————————————————————————————————————————————
-#                       W  A  R  N  I  N  G
-# ———————————————————————————————————————————————————————————————
-#
-#  Whenever adding a privileged new custom type for e.g.
-#  ActivityPub objects, ALWAYS map their extension back
-#  to "application/octet-stream".
-#  Else files served by us can automatically end up with
-#  those privileged types causing severe security hazards.
-#  (We need those mappings so Phoenix can assoiate its format
-#   (the "extension") to incoming requests of those MIME types)
-#
-# ———————————————————————————————————————————————————————————————
+config :quack,
+  level: :warn,
+  meta: [:all],
+  webhook_url: "https://hooks.slack.com/services/YOUR-KEY-HERE"
+
 config :mime, :types, %{
  "application/xml" => ["xml"],
  "application/xrd+xml" => ["xrd+xml"],
  "application/jrd+json" => ["jrd+json"],
  "application/activity+json" => ["activity+json"],
-  "application/ld+json" => ["activity+json"],
-  # Can be removed when bumping MIME past 2.0.5
-  # see https://akkoma.dev/AkkomaGang/akkoma/issues/657
-  "image/apng" => ["apng"]
+  "application/ld+json" => ["activity+json"]
 }

-config :mime, :extensions, %{
-  "xrd+xml" => "text/plain",
-  "jrd+json" => "text/plain",
-  "activity+json" => "text/plain"
-}
-
-# ———————————————————————————————————————————————————————————————
-
 config :tesla, :adapter, {Tesla.Adapter.Finch, name: MyFinch}

 # Configures http settings, upstream proxy etc.
@ -188,10 +184,7 @@
  receive_timeout: :timer.seconds(15),
  proxy_url: nil,
  user_agent: :default,
-  pool_size: 10,
-  adapter: [],
-  # see: https://hexdocs.pm/finch/Finch.html#start_link/1
-  pool_max_idle_time: :timer.seconds(30)
+  adapter: []

 config :pleroma, :instance,
  name: "Akkoma",
@ -271,9 +264,7 @@
  profile_directory: true,
  privileged_staff: false,
  local_bubble: [],
-  max_frontend_settings_json_chars: 100_000,
-  export_prometheus_metrics: true,
-  federated_timeline_available: true
+  max_frontend_settings_json_chars: 100_000

 config :pleroma, :welcome,
  direct_message: [
@ -312,6 +303,7 @@
    alwaysShowSubjectInput: true,
    background: "/images/city.jpg",
    collapseMessageWithSubject: false,
+    disableChat: false,
    greentext: false,
    hideFilteredStatuses: false,
    hideMutedPosts: false,
@ -365,7 +357,7 @@

 config :pleroma, :activitypub,
  unfollow_blocked: true,
-  outgoing_blocks: false,
+  outgoing_blocks: true,
  blockers_visible: true,
  follow_handshake_timeout: 500,
  note_replies_output_limit: 5,
@ -399,9 +391,7 @@
  accept: [],
  avatar_removal: [],
  banner_removal: [],
-  background_removal: [],
-  reject_deletes: [],
-  handle_threads: true
+  reject_deletes: []

 config :pleroma, :mrf_keyword,
  reject: [],
@ -428,7 +418,7 @@
  threshold: 604_800,
  actions: [:delist, :strip_followers]

-config :pleroma, :mrf_reject_newly_created_account_notes, age: 86_400
+config :pleroma, :mrf_follow_bot, follower_nickname: nil

 config :pleroma, :rich_media,
  enabled: true,
@ -439,11 +429,7 @@
    Pleroma.Web.RichMedia.Parsers.OEmbed
  ],
  failure_backoff: 60_000,
-  ttl_setters: [
-    Pleroma.Web.RichMedia.Parser.TTL.AwsSignedUrl,
-    Pleroma.Web.RichMedia.Parser.TTL.Opengraph
-  ],
-  max_body: 5_000_000
+  ttl_setters: [Pleroma.Web.RichMedia.Parser.TTL.AwsSignedUrl]

 config :pleroma, :media_proxy,
  enabled: false,
@ -457,8 +443,7 @@
    # Note: max_read_duration defaults to Pleroma.ReverseProxy.max_read_duration_default/1
    max_read_duration: 30_000
  ],
-  whitelist: [],
-  blocklist: []
+  whitelist: []

 config :pleroma, Pleroma.Web.MediaProxy.Invalidation.Http,
  method: :purge,
@ -477,6 +462,10 @@
  image_quality: 85,
  min_content_length: 100 * 1024

+config :pleroma, :shout,
+  enabled: true,
+  limit: 5_000
+
 config :phoenix, :format_encoders, json: Jason, "activity+json": Jason

 config :phoenix, :json_library, Jason
@ -580,10 +569,7 @@
    new_users_digest: 1,
    mute_expire: 5,
    search_indexing: 10,
-    nodeinfo_fetcher: 1,
-    database_prune: 1,
-    rich_media_backfill: 2,
-    rich_media_expiration: 2
+    nodeinfo_fetcher: 1
  ],
  plugins: [
    Oban.Plugins.Pruner,
@ -591,16 +577,14 @@
  ],
  crontab: [
    {"0 0 * * 0", Pleroma.Workers.Cron.DigestEmailsWorker},
-    {"0 0 * * *", Pleroma.Workers.Cron.NewUsersDigestWorker},
-    {"0 3 * * *", Pleroma.Workers.Cron.PruneDatabaseWorker}
+    {"0 0 * * *", Pleroma.Workers.Cron.NewUsersDigestWorker}
  ]

 config :pleroma, :workers,
  retries: [
    federator_incoming: 5,
    federator_outgoing: 5,
-    search_indexing: 2,
-    rich_media_backfill: 3
+    search_indexing: 2
  ],
  timeout: [
    activity_expiration: :timer.seconds(5),
@ -621,9 +605,7 @@
    new_users_digest: :timer.seconds(10),
    mute_expire: :timer.seconds(5),
    search_indexing: :timer.seconds(5),
-    nodeinfo_fetcher: :timer.seconds(10),
-    database_prune: :timer.minutes(10),
-    rich_media_backfill: :timer.seconds(30)
+    nodeinfo_fetcher: :timer.seconds(10)
  ]

 config :pleroma, Pleroma.Formatter,
@ -669,10 +651,6 @@

 config :pleroma, Pleroma.Emails.Mailer, adapter: Swoosh.Adapters.Sendmail, enabled: false

-config :swoosh,
-  api_client: Swoosh.ApiClient.Finch,
-  finch_name: MyFinch
-
 config :pleroma, Pleroma.Emails.UserEmail,
  logo: nil,
  styling: %{
@ -762,9 +740,6 @@
  primary: %{"name" => "pleroma-fe", "ref" => "stable"},
  admin: %{"name" => "admin-fe", "ref" => "stable"},
  mastodon: %{"name" => "mastodon-fe", "ref" => "akkoma"},
-  pickable: [
-    "pleroma-fe/stable"
-  ],
  swagger: %{
    "name" => "swagger-ui",
    "ref" => "stable",
@ -803,6 +778,14 @@
        "https://akkoma-updates.s3-website.fr-par.scw.cloud/frontend/${ref}/admin-fe.zip",
      "ref" => "stable"
    },
+    "soapbox-fe" => %{
+      "name" => "soapbox-fe",
+      "git" => "https://gitlab.com/soapbox-pub/soapbox",
+      "build_url" =>
+        "https://gitlab.com/soapbox-pub/soapbox/-/jobs/artifacts/${ref}/download?job=build-production",
+      "ref" => "v2.0.0",
+      "build_dir" => "static"
+    },
    # For developers - enables a swagger frontend to view the openapi spec
    "swagger-ui" => %{
      "name" => "swagger-ui",
@ -822,17 +805,15 @@
 config :pleroma, configurable_from_database: false

 config :pleroma, Pleroma.Repo,
-  parameters: [
-    gin_fuzzy_search_limit: "500",
-    plan_cache_mode: "force_custom_plan"
-  ]
+  parameters: [gin_fuzzy_search_limit: "500"],
+  prepare: :unnamed

 config :pleroma, :majic_pool, size: 2

 private_instance? = :if_instance_is_private

 config :pleroma, :restrict_unauthenticated,
-  timelines: %{local: private_instance?, federated: private_instance?, bubble: true},
+  timelines: %{local: private_instance?, federated: private_instance?},
  profiles: %{local: private_instance?, remote: private_instance?},
  activities: %{local: private_instance?, remote: private_instance?}

@ -904,11 +885,6 @@
  url: "http://127.0.0.1:5000",
  api_key: nil

-config :pleroma, :argos_translate,
-  command_argos_translate: "argos-translate",
-  command_argospm: "argospm",
-  strip_html: true
-
 # Import environment specific config. This must remain at the bottom
 # of this file so it overrides the configuration defined above.
 import_config "#{Mix.env()}.exs"
--- a/config/custom_emoji.txt
+++ b/config/custom_emoji.txt
@ -1,2 +0,0 @@
-hehe, /emoji/hehe.png, Akkoma
-nothehe, /emoji/nothehe.png, Akkoma
--- a/config/description.exs
+++ b/config/description.exs
@ -100,23 +100,18 @@
        label: "Base URL",
        type: :string,
        description:
-          "Base URL for the uploads. Required if you use a CDN or host attachments under a different domain - it is HIGHLY recommended that you **do not** set this to be the same as the domain akkoma is hosted on.",
+          "Base URL for the uploads. Required if you use a CDN or host attachments under a different domain.",
        suggestions: [
-          "https://media.akkoma.dev/media/"
+          "https://cdn-host.com"
        ]
      },
      %{
-        key: :allowed_mime_types,
-        label: "Allowed MIME types",
-        type: {:list, :string},
-        description:
-          "List of MIME (main) types uploads are allowed to identify themselves with. Other types may still be uploaded, but will identify as a generic binary to clients. WARNING: Loosening this over the defaults can lead to security issues. Removing types is safe, but only add to the list if you are sure you know what you are doing.",
-        suggestions: [
-          "image",
-          "audio",
-          "video",
-          "font"
-        ]
+        key: :proxy_remote,
+        type: :boolean,
+        description: """
+        Proxy requests to the remote uploader.\n
+        Useful if media upload endpoint is not internet accessible.
+        """
      },
      %{
        key: :filename_display_max_length,
@ -214,26 +209,6 @@
      }
    ]
  },
-  %{
-    group: :pleroma,
-    key: Pleroma.Upload.Filter.Exiftool.StripMetadata,
-    type: :group,
-    description: "Strip specified metadata from image uploads",
-    children: [
-      %{
-        key: :purge,
-        description: "Metadata fields or groups to strip",
-        type: {:list, :string},
-        suggestions: ["all", "CommonIFD0"]
-      },
-      %{
-        key: :preserve,
-        description: "Metadata fields or groups to preserve (takes precedence over stripping)",
-        type: {:list, :string},
-        suggestions: ["ColorSpaces", "Orientation"]
-      }
-    ]
-  },
  %{
    group: :pleroma,
    key: Pleroma.Emails.Mailer,
@ -716,8 +691,8 @@
        key: :public,
        type: :boolean,
        description:
-          "Switching this on will allow unauthenticated users access to all public resources on your instance" <>
-            " Switching it off is useful for disabling the Local Timeline and The Whole Known Network. " <>
+          "Makes the client API in authenticated mode-only except for user-profiles." <>
+            " Useful for disabling the Local Timeline and The Whole Known Network. " <>
            " Note: when setting to `false`, please also check `:restrict_unauthenticated` setting."
      },
      %{
@ -748,8 +723,7 @@
          "text/plain",
          "text/html",
          "text/markdown",
-          "text/bbcode",
-          "text/x.misskeymarkdown"
+          "text/bbcode"
        ]
      },
      %{
@ -815,7 +789,7 @@
      %{
        key: :healthcheck,
        type: :boolean,
-        description: "If enabled, system data will be shown on `/api/v1/pleroma/healthcheck`"
+        description: "If enabled, system data will be shown on `/api/pleroma/healthcheck`"
      },
      %{
        key: :remote_post_retention_days,
@ -989,17 +963,6 @@
        type: {:list, :string},
        description:
          "List of instances that make up your local bubble (closely-related instances). Used to populate the 'bubble' timeline (domain only)."
-      },
-      %{
-        key: :export_prometheus_metrics,
-        type: :boolean,
-        description: "Enable prometheus metrics (at /api/v1/akkoma/metrics)"
-      },
-      %{
-        key: :federated_timeline_available,
-        type: :boolean,
-        description:
-          "Let people view the 'firehose' feed of all public statuses from all instances."
      }
    ]
  },
@ -1106,7 +1069,7 @@
        key: :level,
        type: {:dropdown, :atom},
        description: "Log level",
-        suggestions: [:debug, :info, :warning, :error]
+        suggestions: [:debug, :info, :warn, :error]
      },
      %{
        key: :ident,
@ -1139,7 +1102,7 @@
        key: :level,
        type: {:dropdown, :atom},
        description: "Log level",
-        suggestions: [:debug, :info, :warning, :error]
+        suggestions: [:debug, :info, :warn, :error]
      },
      %{
        key: :format,
@ -1154,6 +1117,45 @@
      }
    ]
  },
+  %{
+    group: :quack,
+    type: :group,
+    label: "Quack Logger",
+    description: "Quack-related settings",
+    children: [
+      %{
+        key: :level,
+        type: {:dropdown, :atom},
+        description: "Log level",
+        suggestions: [:debug, :info, :warn, :error]
+      },
+      %{
+        key: :meta,
+        type: {:list, :atom},
+        description: "Configure which metadata you want to report on",
+        suggestions: [
+          :application,
+          :module,
+          :file,
+          :function,
+          :line,
+          :pid,
+          :crash_reason,
+          :initial_call,
+          :registered_name,
+          :all,
+          :none
+        ]
+      },
+      %{
+        key: :webhook_url,
+        label: "Webhook URL",
+        type: :string,
+        description: "Configure the Slack incoming webhook",
+        suggestions: ["https://hooks.slack.com/services/YOUR-KEY-HERE"]
+      }
+    ]
+  },
  %{
    group: :pleroma,
    key: :frontend_configurations,
@ -1292,13 +1294,7 @@
            label: "Post Content Type",
            type: {:dropdown, :atom},
            description: "Default post formatting option",
-            suggestions: [
-              "text/plain",
-              "text/html",
-              "text/markdown",
-              "text/bbcode",
-              "text/x.misskeymarkdown"
-            ]
+            suggestions: ["text/plain", "text/html", "text/markdown", "text/bbcode"]
          },
          %{
            key: :redirectRootNoLogin,
@ -1583,21 +1579,7 @@
      %{
        key: :whitelist,
        type: {:list, :string},
-        description: """
-        List of hosts with scheme to bypass the MediaProxy.\n
-        The media will be fetched by the client, directly from the remote server.\n
-        To allow this, it will Content-Security-Policy exceptions for each instance listed.\n
-        This is to be used for instances you trust and do not want to cache media for.
-        """,
-        suggestions: ["http://example.com"]
-      },
-      %{
-        key: :blocklist,
-        type: {:list, :string},
-        description: """
-        List of hosts with scheme which will not go through the MediaProxy, and will not be explicitly allowed by the Content-Security-Policy.
-        This is to be used for instances where you do not want their media to go through your server or to be accessed by clients.
-        """,
+        description: "List of hosts with scheme to bypass the MediaProxy",
        suggestions: ["http://example.com"]
      }
    ]
@ -1883,7 +1865,7 @@
        key: :log,
        type: {:dropdown, :atom},
        description: "Logs verbose mode",
-        suggestions: [false, :error, :warning, :info, :debug]
+        suggestions: [false, :error, :warn, :info, :debug]
      },
      %{
        key: :queues,
@ -2706,12 +2688,6 @@
          "What user agent to use. Must be a string or an atom `:default`. Default value is `:default`.",
        suggestions: ["Pleroma", :default]
      },
-      %{
-        key: :pool_size,
-        type: :integer,
-        description: "Number of concurrent outbound HTTP requests to allow PER HOST. Default 10.",
-        suggestions: [10]
-      },
      %{
        key: :adapter,
        type: :keyword,
@ -2733,13 +2709,6 @@
            ]
          }
        ]
-      },
-      %{
-        key: :pool_max_idle_time,
-        type: :integer,
-        description:
-          "Number of seconds to retain an HTTP pool; pool will remain if actively in use. Default 30 seconds (in ms).",
-        suggestions: [30_000]
      }
    ]
  },
@ -3029,7 +2998,8 @@
    key: :restrict_unauthenticated,
    label: "Restrict Unauthenticated",
    type: :group,
-    description: "Disallow unauthenticated viewing of timelines, user profiles and statuses.",
+    description:
+      "Disallow viewing timelines, user profiles and statuses for unauthenticated users.",
    children: [
      %{
        key: :timelines,
@ -3039,17 +3009,12 @@
          %{
            key: :local,
            type: :boolean,
-            description: "Disallow viewing the public timeline."
+            description: "Disallow view public timeline."
          },
          %{
            key: :federated,
            type: :boolean,
-            description: "Disallow viewing the whole known network timeline."
-          },
-          %{
-            key: :bubble,
-            type: :boolean,
-            description: "Disallow viewing the bubble timeline."
+            description: "Disallow view federated timeline."
          }
        ]
      },
@ -3061,29 +3026,29 @@
          %{
            key: :local,
            type: :boolean,
-            description: "Disallow viewing local user profiles."
+            description: "Disallow view local user profiles."
          },
          %{
            key: :remote,
            type: :boolean,
-            description: "Disallow viewing remote user profiles."
+            description: "Disallow view remote user profiles."
          }
        ]
      },
      %{
        key: :activities,
        type: :map,
-        description: "Settings for posts.",
+        description: "Settings for statuses.",
        children: [
          %{
            key: :local,
            type: :boolean,
-            description: "Disallow viewing local posts."
+            description: "Disallow view local statuses."
          },
          %{
            key: :remote,
            type: :boolean,
-            description: "Disallow viewing remote posts."
+            description: "Disallow view remote statuses."
          }
        ]
      }
@ -3205,12 +3170,6 @@
        description:
          "A map containing available frontends and parameters for their installation.",
        children: frontend_options
-      },
-      %{
-        key: :pickable,
-        type: {:list, :string},
-        description:
-          "A list containing all frontends users can pick as their preference, format is :name/:ref, e.g pleroma-fe/stable."
      }
    ]
  },
@ -3505,32 +3464,5 @@
        suggestion: [nil]
      }
    ]
-  },
-  %{
-    group: :pleroma,
-    key: :argos_translate,
-    type: :group,
-    description: "ArgosTranslate Settings.",
-    children: [
-      %{
-        key: :command_argos_translate,
-        type: :string,
-        description:
-          "command for `argos-translate`. Can be the command if it's in your PATH, or the full path to the file.",
-        suggestion: ["argos-translate"]
-      },
-      %{
-        key: :command_argospm,
-        type: :string,
-        description:
-          "command for `argospm`. Can be the command if it's in your PATH, or the full path to the file.",
-        suggestion: ["argospm"]
-      },
-      %{
-        key: :strip_html,
-        type: :boolean,
-        description: "Strip html from the post before translating it."
-      }
-    ]
  }
 ]
--- a/config/dokku.exs
+++ b/config/dokku.exs
@ -0,0 +1,25 @@
+import Config
+
+config :pleroma, Pleroma.Web.Endpoint,
+  http: [
+    port: String.to_integer(System.get_env("PORT") || "4000"),
+    protocol_options: [max_request_line_length: 8192, max_header_value_length: 8192]
+  ],
+  protocol: "http",
+  secure_cookie_flag: false,
+  url: [host: System.get_env("APP_HOST"), scheme: "https", port: 443],
+  secret_key_base: "+S+ULgf7+N37c/lc9K66SMphnjQIRGklTu0BRr2vLm2ZzvK0Z6OH/PE77wlUNtvP"
+
+database_url =
+  System.get_env("DATABASE_URL") ||
+    raise """
+    environment variable DATABASE_URL is missing.
+    For example: ecto://USER:PASS@HOST/DATABASE
+    """
+
+config :pleroma, Pleroma.Repo,
+  # ssl: true,
+  url: database_url,
+  pool_size: String.to_integer(System.get_env("POOL_SIZE") || "10")
+
+config :pleroma, :instance, name: "#{System.get_env("APP_NAME")} CI Instance"
--- a/config/test.exs
+++ b/config/test.exs
@ -16,17 +16,15 @@

 # Print only warnings and errors during test
 config :logger, :console,
-  level: :warning,
+  level: :warn,
  format: "\n[$level] $message\n"

 config :pleroma, :auth, oauth_consumer_strategies: []

 config :pleroma, Pleroma.Upload,
-  base_url: "http://localhost:4001/media/",
  filters: [],
-  link_name: false
-
-config :pleroma, :media_proxy, base_url: "http://localhost:4001"
+  link_name: false,
+  default_description: :filename

 config :pleroma, Pleroma.Uploaders.Local, uploads: "test/uploads"

@ -51,8 +49,7 @@
  hostname: System.get_env("DB_HOST") || "localhost",
  pool: Ecto.Adapters.SQL.Sandbox,
  pool_size: 50,
-  queue_target: 5000,
-  log: false
+  queue_target: 5000

 config :pleroma, :dangerzone, override_repo_pool_size: true

@ -64,8 +61,7 @@
 config :pleroma, :rich_media,
  enabled: false,
  ignore_hosts: [],
-  ignore_tld: ["local", "localdomain", "lan"],
-  max_body: 2_000_000
+  ignore_tld: ["local", "localdomain", "lan"]

 config :pleroma, :instance,
  multi_factor_authentication: [
@ -86,7 +82,10 @@
    "BLH1qVhJItRGCfxgTtONfsOKDc9VRAraXw-3NsmjMngWSh7NxOizN6bkuRA7iLTMPS82PjwJAr3UoK9EC1IFrz4",
  private_key: "_-XZ0iebPrRfZ_o0-IatTdszYa8VCH1yLN-JauK7HHA"

-config :pleroma, Oban, testing: :manual
+config :pleroma, Oban,
+  queues: false,
+  crontab: false,
+  plugins: false

 config :pleroma, Pleroma.ScheduledActivity,
  daily_user_limit: 2,
@ -143,8 +142,6 @@
 config :pleroma, :instances_favicons, enabled: false
 config :pleroma, :instances_nodeinfo, enabled: false

-config :pleroma, Pleroma.Web.RichMedia.Backfill, provider: Pleroma.Web.RichMedia.Backfill
-
 if File.exists?("./config/test.secret.exs") do
  import_config "test.secret.exs"
 else
--- a/coveralls.json
+++ b/coveralls.json
@ -0,0 +1,7 @@
+{
+  "skip_files": [
+    "test/support",
+    "lib/mix/tasks/pleroma/benchmark.ex",
+    "lib/credo/check/consistency/file_location.ex"
+  ]
+}
--- a/diagnostic-tools/binary-leak-checker.sh
+++ b/diagnostic-tools/binary-leak-checker.sh
@ -1,10 +0,0 @@
-if [ "$#" -ne 2 ]; then
-	echo "Usage: binary-leak-checker.sh <nodename> <erlang cookie>"
-	exit 1
-fi
-
-echo "The command you want to run is:
-:recon.bin_leak(10)
-"
-
-iex --sname debug --remsh $1 --erl "-setcookie $2" 
--- a/docker-compose.yml
+++ b/docker-compose.yml
@ -4,7 +4,6 @@ services:
  db:
    image: akkoma-db:latest
    build: ./docker-resources/database
-    shm_size: 4gb
    restart: unless-stopped
    user: ${DOCKER_USER}
    environment: {
@ -46,7 +45,7 @@ services:
    volumes:
      - .:/opt/akkoma

-  # Copy this into docker-compose.override.yml and uncomment there if you want to use a reverse proxy
+  # Uncomment the following if you want to use a reverse proxy
  #proxy:
  #  image: caddy:2-alpine
  #  restart: unless-stopped
--- a/docker-entrypoint.sh
+++ b/docker-entrypoint.sh
@ -11,4 +11,4 @@ echo "-- Running migrations..."
 mix ecto.migrate

 echo "-- Starting!"
-elixir --erl "+sbwt none +sbwtdcpu none +sbwtdio none" -S mix phx.server
+mix phx.server
--- a/docker-resources/build.sh
+++ b/docker-resources/build.sh
@ -1,4 +1,4 @@
 #!/bin/sh

-docker compose build --build-arg UID=$(id -u) --build-arg GID=$(id -g) akkoma
-docker compose build --build-arg UID=$(id -u) --build-arg GID=$(id -g) db
+docker-compose build --build-arg UID=$(id -u) --build-arg GID=$(id -g) akkoma
+docker-compose build --build-arg UID=$(id -u) --build-arg GID=$(id -g) db
--- a/docker-resources/env.example
+++ b/docker-resources/env.example
@ -1,5 +1,4 @@
 MIX_ENV=prod
-ERL_EPMD_ADDRESS=127.0.0.1
 DB_NAME=akkoma
 DB_USER=akkoma
 DB_PASS=akkoma
--- a/docker-resources/manage.sh
+++ b/docker-resources/manage.sh
@ -1,3 +1,3 @@
 #!/bin/sh

-docker compose run --rm akkoma $@
+docker-compose run --rm akkoma $@
--- a/docs/Pipfile.lock
+++ b/docs/Pipfile.lock
@ -19,7 +19,7 @@
                "sha256:0d9c601124e5a6ba9712dbc60d9c53c21e34f5f641fe83002317394311bdce14",
                "sha256:90c1a32f1d68f940488354e36370f6cca89f0f106db09518524c88d6ed83f382"
            ],
-            "markers": "python_full_version >= '3.6.0'",
+            "markers": "python_version >= '3.6'",
            "version": "==2022.9.24"
        },
        "charset-normalizer": {
@ -27,7 +27,7 @@
                "sha256:5a3d016c7c547f69d6f81fb0db9449ce888b418b5b9952cc5e6e66843e9dd845",
                "sha256:83e9a75d1911279afd89352c68b45348559d1fc0506b054b346651b5e7fee29f"
            ],
-            "markers": "python_full_version >= '3.6.0'",
+            "markers": "python_version >= '3.6'",
            "version": "==2.1.1"
        },
        "click": {
@ -66,16 +66,15 @@
                "sha256:cbb516f16218e643d8e0a95b309f77eb118cb138d39a4f27851e6a63581db874",
                "sha256:f5da449a6e1c989a4cea2631aa8ee67caa5a2ef855d551c88f9e309f4634c621"
            ],
-            "markers": "python_full_version >= '3.6.0'",
+            "markers": "python_version >= '3.6'",
            "version": "==3.3.7"
        },
        "markdown-include": {
            "hashes": [
-                "sha256:b8f6b6f4e8b506cbe773d7e26c74a97d1354c35f3a3452d3449140a8f578d665",
-                "sha256:d12fb51500c46334a53608635035c78b7d8ad7f772566f70b8a6a9b2ef2ddbf5"
+                "sha256:a06183b7c7225e73112737acdc6fe0ac0686c39457234eeb5ede23881fed001d"
            ],
            "index": "pypi",
-            "version": "==0.8.0"
+            "version": "==0.7.0"
        },
        "markupsafe": {
            "hashes": [
@ -128,7 +127,7 @@
                "sha256:0096d52e9dad9939c3d975a774666af186eda617e6ca84df4c94dec30004f2a8",
                "sha256:70775750742b25c0d8f36c55aed03d24c3384d17c951b3175d898bd778ef0307"
            ],
-            "markers": "python_full_version >= '3.6.0'",
+            "markers": "python_version >= '3.6'",
            "version": "==1.3.4"
        },
        "mkdocs": {
@ -141,26 +140,26 @@
        },
        "mkdocs-material": {
            "hashes": [
-                "sha256:b0ea0513fd8cab323e8a825d6692ea07fa83e917bb5db042e523afecc7064ab7",
-                "sha256:c907b4b052240a5778074a30a78f31a1f8ff82d7012356dc26898b97559f082e"
+                "sha256:143ea55843b3747b640e1110824d91e8a4c670352380e166e64959f9abe98862",
+                "sha256:45eeabb23d2caba8fa3b85c91d9ec8e8b22add716e9bba8faf16d56af8aa5622"
            ],
            "index": "pypi",
-            "version": "==8.5.11"
+            "version": "==8.5.9"
        },
        "mkdocs-material-extensions": {
            "hashes": [
-                "sha256:9c003da71e2cc2493d910237448c672e00cefc800d3d6ae93d2fc69979e3bd93",
-                "sha256:e41d9f38e4798b6617ad98ca8f7f1157b1e4385ac1459ca1e4ea219b556df945"
+                "sha256:96ca979dae66d65c2099eefe189b49d5ac62f76afb59c38e069ffc7cf3c131ec",
+                "sha256:bcc2e5fc70c0ec50e59703ee6e639d87c7e664c0c441c014ea84461a90f1e902"
            ],
            "markers": "python_version >= '3.7'",
-            "version": "==1.1.1"
+            "version": "==1.1"
        },
        "packaging": {
            "hashes": [
                "sha256:dd47c42927d89ab911e606518907cc2d3a1f38bbd026385970643f9c5b8ecfeb",
                "sha256:ef103e05f519cdc783ae24ea4e2e0f508a9c99b2d4969652eed6a2e1ea5bd522"
            ],
-            "markers": "python_full_version >= '3.6.0'",
+            "markers": "python_version >= '3.6'",
            "version": "==21.3"
        },
        "pygments": {
@ -168,16 +167,16 @@
                "sha256:56a8508ae95f98e2b9bdf93a6be5ae3f7d8af858b43e02c5a2ff083726be40c1",
                "sha256:f643f331ab57ba3c9d89212ee4a2dabc6e94f117cf4eefde99a0574720d14c42"
            ],
-            "markers": "python_full_version >= '3.6.0'",
+            "markers": "python_version >= '3.6'",
            "version": "==2.13.0"
        },
        "pymdown-extensions": {
            "hashes": [
-                "sha256:0f8fb7b74a37a61cc34e90b2c91865458b713ec774894ffad64353a5fce85cfc",
-                "sha256:ac698c15265680db5eb13cd4342abfcde2079ac01e5486028f47a1b41547b859"
+                "sha256:1bd4a173095ef8c433b831af1f3cb13c10883be0c100ae613560668e594651f7",
+                "sha256:8e62688a8b1128acd42fa823f3d429d22f4284b5e6dd4d3cd56721559a5a211b"
            ],
            "markers": "python_version >= '3.7'",
-            "version": "==9.9"
+            "version": "==9.8"
        },
        "pyparsing": {
            "hashes": [
@ -238,7 +237,7 @@
                "sha256:e61ceaab6f49fb8bdfaa0f92c4b57bcfbea54c09277b1b4f7ac376bfb7a7c174",
                "sha256:f84fbc98b019fef2ee9a1cb3ce93e3187a6df0b2538a651bfb890254ba9f90b5"
            ],
-            "markers": "python_full_version >= '3.6.0'",
+            "markers": "python_version >= '3.6'",
            "version": "==6.0"
        },
        "pyyaml-env-tag": {
@ -246,7 +245,7 @@
                "sha256:70092675bda14fdec33b31ba77e7543de9ddc88f2e5b99160396572d11525bdb",
                "sha256:af31106dec8a4d68c60207c1886031cbf839b68aa7abccdb19868200532c2069"
            ],
-            "markers": "python_full_version >= '3.6.0'",
+            "markers": "python_version >= '3.6'",
            "version": "==0.1"
        },
        "requests": {
@ -267,45 +266,42 @@
        },
        "urllib3": {
            "hashes": [
-                "sha256:47cc05d99aaa09c9e72ed5809b60e7ba354e64b59c9c173ac3018642d8bb41fc",
-                "sha256:c083dd0dce68dbfbe1129d5271cb90f9447dea7d52097c6e0126120c521ddea8"
+                "sha256:3fa96cf423e6987997fc326ae8df396db2a8b7c667747d47ddd8ecba91f4a74e",
+                "sha256:b930dd878d5a8afb066a637fbb35144fe7901e3b209d1cd4f524bd0e9deee997"
            ],
-            "markers": "python_version >= '2.7' and python_version not in '3.0, 3.1, 3.2, 3.3, 3.4, 3.5'",
-            "version": "==1.26.13"
+            "markers": "python_version >= '2.7' and python_version not in '3.0, 3.1, 3.2, 3.3, 3.4, 3.5' and python_version < '4'",
+            "version": "==1.26.12"
        },
        "watchdog": {
            "hashes": [
-                "sha256:1893d425ef4fb4f129ee8ef72226836619c2950dd0559bba022b0818c63a7b60",
-                "sha256:1a410dd4d0adcc86b4c71d1317ba2ea2c92babaf5b83321e4bde2514525544d5",
-                "sha256:1f2b0665c57358ce9786f06f5475bc083fea9d81ecc0efa4733fd0c320940a37",
-                "sha256:1f8eca9d294a4f194ce9df0d97d19b5598f310950d3ac3dd6e8d25ae456d4c8a",
-                "sha256:27e49268735b3c27310883012ab3bd86ea0a96dcab90fe3feb682472e30c90f3",
-                "sha256:28704c71afdb79c3f215c90231e41c52b056ea880b6be6cee035c6149d658ed1",
-                "sha256:2ac0bd7c206bb6df78ef9e8ad27cc1346f2b41b1fef610395607319cdab89bc1",
-                "sha256:2af1a29fd14fc0a87fb6ed762d3e1ae5694dcde22372eebba50e9e5be47af03c",
-                "sha256:3a048865c828389cb06c0bebf8a883cec3ae58ad3e366bcc38c61d8455a3138f",
-                "sha256:441024df19253bb108d3a8a5de7a186003d68564084576fecf7333a441271ef7",
-                "sha256:56fb3f40fc3deecf6e518303c7533f5e2a722e377b12507f6de891583f1b48aa",
-                "sha256:619d63fa5be69f89ff3a93e165e602c08ed8da402ca42b99cd59a8ec115673e1",
-                "sha256:74535e955359d79d126885e642d3683616e6d9ab3aae0e7dcccd043bd5a3ff4f",
-                "sha256:76a2743402b794629a955d96ea2e240bd0e903aa26e02e93cd2d57b33900962b",
-                "sha256:83cf8bc60d9c613b66a4c018051873d6273d9e45d040eed06d6a96241bd8ec01",
-                "sha256:920a4bda7daa47545c3201a3292e99300ba81ca26b7569575bd086c865889090",
-                "sha256:9e99c1713e4436d2563f5828c8910e5ff25abd6ce999e75f15c15d81d41980b6",
-                "sha256:a5bd9e8656d07cae89ac464ee4bcb6f1b9cecbedc3bf1334683bed3d5afd39ba",
-                "sha256:ad0150536469fa4b693531e497ffe220d5b6cd76ad2eda474a5e641ee204bbb6",
-                "sha256:af4b5c7ba60206759a1d99811b5938ca666ea9562a1052b410637bb96ff97512",
-                "sha256:c7bd98813d34bfa9b464cf8122e7d4bec0a5a427399094d2c17dd5f70d59bc61",
-                "sha256:ceaa9268d81205876bedb1069f9feab3eccddd4b90d9a45d06a0df592a04cae9",
-                "sha256:cf05e6ff677b9655c6e9511d02e9cc55e730c4e430b7a54af9c28912294605a4",
-                "sha256:d0fb5f2b513556c2abb578c1066f5f467d729f2eb689bc2db0739daf81c6bb7e",
-                "sha256:d6ae890798a3560688b441ef086bb66e87af6b400a92749a18b856a134fc0318",
-                "sha256:e5aed2a700a18c194c39c266900d41f3db0c1ebe6b8a0834b9995c835d2ca66e",
-                "sha256:e722755d995035dd32177a9c633d158f2ec604f2a358b545bba5bed53ab25bca",
-                "sha256:ed91c3ccfc23398e7aa9715abf679d5c163394b8cad994f34f156d57a7c163dc"
+                "sha256:083171652584e1b8829581f965b9b7723ca5f9a2cd7e20271edf264cfd7c1412",
+                "sha256:117ffc6ec261639a0209a3252546b12800670d4bf5f84fbd355957a0595fe654",
+                "sha256:186f6c55abc5e03872ae14c2f294a153ec7292f807af99f57611acc8caa75306",
+                "sha256:195fc70c6e41237362ba720e9aaf394f8178bfc7fa68207f112d108edef1af33",
+                "sha256:226b3c6c468ce72051a4c15a4cc2ef317c32590d82ba0b330403cafd98a62cfd",
+                "sha256:247dcf1df956daa24828bfea5a138d0e7a7c98b1a47cf1fa5b0c3c16241fcbb7",
+                "sha256:255bb5758f7e89b1a13c05a5bceccec2219f8995a3a4c4d6968fe1de6a3b2892",
+                "sha256:43ce20ebb36a51f21fa376f76d1d4692452b2527ccd601950d69ed36b9e21609",
+                "sha256:4f4e1c4aa54fb86316a62a87b3378c025e228178d55481d30d857c6c438897d6",
+                "sha256:5952135968519e2447a01875a6f5fc8c03190b24d14ee52b0f4b1682259520b1",
+                "sha256:64a27aed691408a6abd83394b38503e8176f69031ca25d64131d8d640a307591",
+                "sha256:6b17d302850c8d412784d9246cfe8d7e3af6bcd45f958abb2d08a6f8bedf695d",
+                "sha256:70af927aa1613ded6a68089a9262a009fbdf819f46d09c1a908d4b36e1ba2b2d",
+                "sha256:7a833211f49143c3d336729b0020ffd1274078e94b0ae42e22f596999f50279c",
+                "sha256:8250546a98388cbc00c3ee3cc5cf96799b5a595270dfcfa855491a64b86ef8c3",
+                "sha256:97f9752208f5154e9e7b76acc8c4f5a58801b338de2af14e7e181ee3b28a5d39",
+                "sha256:9f05a5f7c12452f6a27203f76779ae3f46fa30f1dd833037ea8cbc2887c60213",
+                "sha256:a735a990a1095f75ca4f36ea2ef2752c99e6ee997c46b0de507ba40a09bf7330",
+                "sha256:ad576a565260d8f99d97f2e64b0f97a48228317095908568a9d5c786c829d428",
+                "sha256:b530ae007a5f5d50b7fbba96634c7ee21abec70dc3e7f0233339c81943848dc1",
+                "sha256:bfc4d351e6348d6ec51df007432e6fe80adb53fd41183716017026af03427846",
+                "sha256:d3dda00aca282b26194bdd0adec21e4c21e916956d972369359ba63ade616153",
+                "sha256:d9820fe47c20c13e3c9dd544d3706a2a26c02b2b43c993b62fcd8011bcc0adb3",
+                "sha256:ed80a1628cee19f5cfc6bb74e173f1b4189eb532e705e2a13e3250312a62e0c9",
+                "sha256:ee3e38a6cc050a8830089f79cbec8a3878ec2fe5160cdb2dc8ccb6def8552658"
            ],
-            "markers": "python_full_version >= '3.6.0'",
-            "version": "==2.2.0"
+            "markers": "python_version >= '3.6'",
+            "version": "==2.1.9"
        }
    },
    "develop": {}
--- a/docs/README.md
+++ b/docs/README.md
@ -2,27 +2,33 @@

 You don't need to build and test the docs as long as you make sure the syntax is correct. But in case you do want to build the docs, feel free to do so.

-```sh
-# Make sure you're in the same directory as this README
-# From the root of the Akkoma repo, you'll need to do
-cd docs
+You'll need to install mkdocs for which you can check the [mkdocs installation guide](https://www.mkdocs.org/#installation). Generally it's best to install it using `pip`. You'll also need to install the correct dependencies.

-# Optionally use a virtual environment
-python3 -m venv venv
-source venv/bin/activate
+### Example using a Debian based distro

-# Install dependencies
-pip install -r requirements.txt
+#### 1. Install pipenv and dependencies

-# Run an http server who rebuilds when files change
-# Accessable on http://127.0.0.1:8000
-mkdocs serve
-
-# Build the docs
-# The static html pages will have been created in the folder "site"
-# You can serve them from a server by pointing your server software (nginx, apache...) to this location
-mkdocs build
-
-# To get out of the virtual environment, you do
-deactivate
+```shell
+pip install pipenv
+pipenv sync
 ```
+
+#### 2. (Optional) Activate the virtual environment
+
+Since dependencies are installed in a virtual environment, you can't use them directly. To use them you should either prefix the command with `pipenv run`, or activate the virtual environment for current shell by executing `pipenv shell` once.
+
+#### 3. Build the docs using the script
+
+```shell
+[pipenv run] make all
+```
+
+#### 4. Serve the files
+
+A folder `site` containing the static html pages will have been created. You can serve them from a server by pointing your server software (nginx, apache...) to this location. During development, you can run locally with
+
+```shell
+[pipenv run] mkdocs serve
+```
+
+This handles setting up an http server and rebuilding when files change. You can then access the docs on <http://127.0.0.1:8000>
--- a/docs/docs/administration/CLI_tasks/config.md
+++ b/docs/docs/administration/CLI_tasks/config.md
@ -155,51 +155,3 @@ This forcibly removes all saved values in the database.
    ```sh
    mix pleroma.config [--force] reset
    ```
-
-## Dumping specific configuration values to JSON
-
-If you want to bulk-modify configuration values (for example, for MRF modifications),
-it may be easier to dump the values to JSON and then modify them in a text editor.
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl config dump_to_file group key path
-    # For example, to dump the MRF simple configuration:
-    ./bin/pleroma_ctl config dump_to_file pleroma mrf_simple /tmp/mrf_simple.json
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.config dump_to_file group key path 
-    # For example, to dump the MRF simple configuration:
-    mix pleroma.config dump_to_file pleroma mrf_simple /tmp/mrf_simple.json
-    ```
-
-## Loading specific configuration values from JSON
-
-**Note:** This will overwrite any existing value in the database, and can
-cause crashes if you do not have exactly the correct formatting.
-
-Once you have modified the JSON file, you can load it back into the database.
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl config load_from_file path
-    # For example, to load the MRF simple configuration:
-    ./bin/pleroma_ctl config load_from_file /tmp/mrf_simple.json
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.config load_from_file path
-    # For example, to load the MRF simple configuration:
-    mix pleroma.config load_from_file /tmp/mrf_simple.json
-    ```
-
-**NOTE** an instance reboot is needed for many changes to take effect,
-you may want to visit `/api/v1/pleroma/admin/restart` on your instance
-to soft-restart the instance.
--- a/docs/docs/administration/CLI_tasks/database.md
+++ b/docs/docs/administration/CLI_tasks/database.md
@ -21,18 +21,16 @@ Replaces embedded objects with references to them in the `objects` table. Only n
    mix pleroma.database remove_embedded_objects [option ...]
    ```

+
 ### Options
 - `--vacuum` - run `VACUUM FULL` after the embedded objects are replaced with their references

 ## Prune old remote posts from the database

-This will prune remote posts older than 90 days (configurable with [`config :pleroma, :instance, remote_post_retention_days`](../../configuration/cheatsheet.md#instance)) from the database. Pruned posts may be refetched in some cases.
-
-!!! note
-    The disk space will only be reclaimed after a proper vacuum. By default Postgresql does this for you on a regular basis, but if your instance has been running for a long time and there are many rows deleted, it may be advantageous to use `VACUUM FULL` (e.g. by using the `--vacuum` option).
+This will prune remote posts older than 90 days (configurable with [`config :pleroma, :instance, remote_post_retention_days`](../../configuration/cheatsheet.md#instance)) from the database, they will be refetched from source when accessed.

 !!! danger
-    You may run out of disk space during the execution of the task or vacuuming if you don't have about 1/3rds of the database size free. Vacuum causes a substantial increase in I/O traffic, and may lead to a degraded experience while it is running.
+    The disk space will only be reclaimed after `VACUUM FULL`. You may run out of disk space during the execution of the task or vacuuming if you don't have about 1/3rds of the database size free.

 === "OTP"

@ -47,41 +45,7 @@ This will prune remote posts older than 90 days (configurable with [`config :ple
    ```

 ### Options
-
- `--keep-threads` - Don't prune posts when they are part of a thread where at least one post has seen local interaction (e.g. one of the posts is a local post, or is favourited by a local user, or has been repeated by a local user...). It also wont delete posts when at least one of the posts in that thread is kept (e.g. because one of the posts has seen recent activity).
- `--keep-non-public` - Keep non-public posts like DM's and followers-only, even if they are remote.
- `--limit` - limits how many remote posts get pruned. This limit does **not** apply to any of the follow up jobs. If wanting to keep the database load in check it is thus advisable to run the standalone `prune_orphaned_activities` task with a limit afterwards instead of passing `--prune-orphaned-activities` to this task.
- `--prune-orphaned-activities` - Also prune orphaned activities afterwards. Activities are things like Like, Create, Announce, Flag (aka reports)... They can significantly help reduce the database size.
- `--vacuum` - Run `VACUUM FULL` after the objects are pruned. This should not be used on a regular basis, but is useful if your instance has been running for a long time before pruning.
-
-## Prune orphaned activities from the database
-
-This will prune activities which are no longer referenced by anything.
-Such activities might be the result of running `prune_objects` without `--prune-orphaned-activities`.
-The same notes and warnings apply as for `prune_objects`.
-
-The task will print out how many rows were freed in total in its last
-line of output in the form `Deleted 345 rows`.  
-When running the job in limited batches this can be used to determine
-when all orphaned activities have been deleted.
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl database prune_orphaned_activities [option ...]
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.database prune_orphaned_activities [option ...]
-    ```
-
-### Options
-
- `--limit n` - Only delete up to `n` activities in each query making up this job, i.e. if this job runs two queries at most `2n` activities will be deleted. Running this task repeatedly in limited batches can help maintain the instance’s responsiveness while still freeing up some space.
- `--no-singles` - Do not delete activites referencing single objects
- `--no-arrays` - Do not delete activites referencing an array of objects
+- `--vacuum` - run `VACUUM FULL` after the objects are pruned

 ## Create a conversation for all existing DMs

@ -129,9 +93,6 @@ Can be safely re-run

 ## Vacuum the database

-!!! note
-    By default Postgresql has an autovacuum deamon running. While the tasks described here can help in some cases, they shouldn't be needed on a regular basis. See [the Postgresql docs on vacuuming](https://www.postgresql.org/docs/current/sql-vacuum.html) for more information on this.
-
 ### Analyze

 Running an `analyze` vacuum job can improve performance by updating statistics used by the query planner. **It is safe to cancel this.**
@ -198,23 +159,3 @@ Change `default_text_search_config` for database and (if necessary) text_search_
    ```

 See [PostgreSQL documentation](https://www.postgresql.org/docs/current/textsearch-configuration.html) and `docs/configuration/howto_search_cjk.md` for more detail.
-
-## Pruning old activities
-
-Over time, transient `Delete` activities and `Tombstone` objects
-can accumulate in your database, inflating its size. This is not ideal. 
-There is a periodic task to prune these transient objects, 
-but on first run this may take a while on older instances to catch up
-to the current day.
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl database prune_task
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.database prune_task
-    ```
--- a/docs/docs/administration/CLI_tasks/diagnostics.md
+++ b/docs/docs/administration/CLI_tasks/diagnostics.md
@ -1,30 +0,0 @@
-# Diagnostics
-
-A few tasks to help with debugging, troubleshooting, and diagnosing problems.
-
-They mostly relate to common postgres queries. 
-
-## Home timeline query plan
-
-This task will print a query plan for the home timeline of a given user.
-
-=== "OTP"
-
-    `./bin/pleroma_ctl diagnostics home_timeline <nickname>`
-
-=== "From Source"
-
-    `mix pleroma.diagnostics home_timeline <nickname>`
-
-## User timeline query plan
-
-This task will print a query plan for the user timeline of a given user,
-from the perspective of another given user.
-
-=== "OTP"
-
-    `./bin/pleroma_ctl diagnostics user_timeline <nickname> <viewing_nickname>`
-
-=== "From Source"
-    
-    `mix pleroma.diagnostics user_timeline <nickname> <viewing_nickname>`
--- a/docs/docs/administration/CLI_tasks/frontend.md
+++ b/docs/docs/administration/CLI_tasks/frontend.md
@ -21,28 +21,29 @@ Currently, known `<frontend>` values are:
 - [admin-fe](https://akkoma.dev/AkkomaGang/admin-fe)
 - [mastodon-fe](https://akkoma.dev/AkkomaGang/masto-fe)
 - [pleroma-fe](https://akkoma.dev/AkkomaGang/pleroma-fe)
+- [soapbox-fe](https://gitlab.com/soapbox-pub/soapbox-fe)

 You can still install frontends that are not configured, see below.

-## Example installations for a known frontend (Stable-Version)
+## Example installations for a known frontend

 For a frontend configured under the `available` key, it's enough to install it by name.

 === "OTP"

    ```sh
-    ./bin/pleroma_ctl frontend install pleroma-fe --ref stable
+    ./bin/pleroma_ctl frontend install pleroma-fe
    ```

 === "From Source"

    ```sh
-    mix pleroma.frontend install pleroma-fe --ref stable
+    mix pleroma.frontend install pleroma-fe
    ```

 This will download the latest build for the pre-configured `ref` and install it. It can then be configured as the one of the served frontends in the config file (see `primary` or `admin`).

-You can override any of the details. To install an Akkoma-FE build from a different URL, you could do this:
+You can override any of the details. To install a Pleroma-FE build from a different URL, you could do this:

 === "OTP"

--- a/docs/docs/administration/CLI_tasks/instance.md
+++ b/docs/docs/administration/CLI_tasks/instance.md
@ -37,8 +37,7 @@ If any of the options are left unspecified, you will be prompted interactively.
 - `--static-dir <path>` - the directory custom public files should be read from (custom emojis, frontend bundle overrides, robots.txt, etc.)
 - `--listen-ip <ip>` - the ip the app should listen to, defaults to 127.0.0.1
 - `--listen-port <port>` - the port the app should listen to, defaults to 4000
- `--strip-uploads-metadata <Y|N>` - use ExifTool to strip uploads of metadata when possible
- `--read-uploads-description <Y|N>` - use ExifTool to read image descriptions from uploads
+- `--strip-uploads <Y|N>` - use ExifTool to strip uploads of sensitive location data
 - `--anonymize-uploads <Y|N>` - randomize uploaded filenames
 - `--dedupe-uploads <Y|N>` - store files based on their hash to reduce data storage requirements if duplicates are uploaded with different filenames
 - `--skip-release-env` - skip generation the release environment file
--- a/docs/docs/administration/CLI_tasks/robots_txt.md
+++ b/docs/docs/administration/CLI_tasks/robots_txt.md
@ -11,7 +11,7 @@ If you want to generate a restrictive `robots.txt`, you can run the following mi
 === "OTP"

    ```sh
-    ./bin/pleroma_ctl robotstxt disallow_all
+    ./bin/pleroma_ctl robots_txt disallow_all
    ```

 === "From Source"
--- a/docs/docs/administration/CLI_tasks/security.md
+++ b/docs/docs/administration/CLI_tasks/security.md
@ -1,56 +0,0 @@
-# Security-related tasks
-
-{! administration/CLI_tasks/general_cli_task_info.include !}
-
-!!! danger
-    Many of these tasks were written in response to a patched exploit.
-    It is recommended to run those very soon after installing its respective security update.
-    Over time with db migrations they might become less accurate or be removed altogether.
-    If you never ran an affected version, there’s no point in running them.
-
-## Spoofed AcitivityPub objects exploit (2024-03, fixed in 3.11.1)
-
-### Search for uploaded spoofing payloads
-
-Scans local uploads for spoofing payloads.
-If the instance is not using the local uploader it was not affected.
-Attachments wil be scanned anyway in case local uploader was used in the past.
-
-!!! note
-    This cannot reliably detect payloads attached to deleted posts.
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl security spoof-uploaded
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.security spoof-uploaded
-    ```
-
-### Search for counterfeit posts in database
-
-Scans all notes in the database for signs of being spoofed.
-
-!!! note
-    Spoofs targeting local accounts can be detected rather reliably
-    (with some restrictions documented in the task’s logs).
-    Counterfeit posts from remote users cannot. A best-effort attempt is made, but
-    a thorough attacker can avoid this and it may yield a small amount of false positives.
-
-    Should you find counterfeit posts of local users, let other admins know so they can delete the too.
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl security spoof-inserted
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.security spoof-inserted
-    ```
--- a/docs/docs/administration/backup.md
+++ b/docs/docs/administration/backup.md
@ -4,54 +4,38 @@

 1. Stop the Akkoma service.
 2. Go to the working directory of Akkoma (default is `/opt/akkoma`)
-3. Run `sudo -Hu postgres pg_dump -d akkoma --format=custom -f </path/to/backup_location/akkoma.pgdump>`[¹] (make sure the postgres user has write access to the destination file)
-4. Copy `akkoma.pgdump`, `config/config.exs`[²], `uploads` folder, and [static directory](../configuration/static_dir.md) to your backup destination. If you have other modifications, copy those changes too.
+3. Run `sudo -Hu postgres pg_dump -d <akkoma_db> --format=custom -f </path/to/backup_location/akkoma.pgdump>` (make sure the postgres user has write access to the destination file)
+4. Copy `akkoma.pgdump`, `config/prod.secret.exs`, `config/setup_db.psql` (if still available) and the `uploads` folder to your backup destination. If you have other modifications, copy those changes too.
 5. Restart the Akkoma service.

-[¹]: We assume the database name is "akkoma". If not, you can find the correct name in your configuration files.  
-[²]: If you have a from source installation, you need `config/prod.secret.exs` instead of `config/config.exs`. The `config/config.exs` file also exists, but in case of from source installations, it only contains the default values and it is tracked by Git, so you don't need to back it up.  
-
 ## Restore/Move

 1. Optionally reinstall Akkoma (either on the same server or on another server if you want to move servers).
 2. Stop the Akkoma service.
 3. Go to the working directory of Akkoma (default is `/opt/akkoma`)
 4. Copy the above mentioned files back to their original position.
-5. Drop the existing database and user[¹]. `sudo -Hu postgres psql -c 'DROP DATABASE akkoma;';` `sudo -Hu postgres psql -c 'DROP USER akkoma;'`
-6. Restore the database schema and akkoma role[¹] (replace the password with the one you find in the configuration file), `sudo -Hu postgres psql -c "CREATE USER akkoma WITH ENCRYPTED PASSWORD '<database-password-wich-you-can-find-in-your-configuration-file>';"` `sudo -Hu postgres psql -c "CREATE DATABASE akkoma OWNER akkoma;"`.
-7. Now restore the Akkoma instance's data into the empty database schema[¹]: `sudo -Hu postgres pg_restore -d akkoma -v -1 </path/to/backup_location/akkoma.pgdump>`
-8. If you installed a newer Akkoma version, you should run the database migrations `./bin/pleroma_ctl migrate`[²].
+5. Drop the existing database and user if restoring in-place. `sudo -Hu postgres psql -c 'DROP DATABASE <akkoma_db>;';` `sudo -Hu postgres psql -c 'DROP USER <akkoma_db>;'`
+6. Restore the database schema and akkoma postgres role the with the original `setup_db.psql` if you have it: `sudo -Hu postgres psql -f config/setup_db.psql`.
+
+  Alternatively, run the `mix pleroma.instance gen` task again. You can ignore most of the questions, but make the database user, name, and password the same as found in your backup of `config/prod.secret.exs`. Then run the restoration of the akkoma role and schema with of the generated `config/setup_db.psql` as instructed above. You may delete the `config/generated_config.exs` file as it is not needed.
+
+7. Now restore the Akkoma instance's data into the empty database schema: `sudo -Hu postgres pg_restore -d <akkoma_db> -v -1 </path/to/backup_location/akkoma.pgdump>`
+8. If you installed a newer Akkoma version, you should run `mix ecto.migrate`[^1]. This task performs database migrations, if there were any.
 9. Restart the Akkoma service.
 10. Run `sudo -Hu postgres vacuumdb --all --analyze-in-stages`. This will quickly generate the statistics so that postgres can properly plan queries.
-11. If setting up on a new server, configure Nginx by using the `installation/nginx/akkoma.nginx` configuration sample or reference the Akkoma installation guide which contains the Nginx configuration instructions.
+11. If setting up on a new server configure Nginx by using the `installation/akkoma.nginx` config sample or reference the Akkoma installation guide for your OS which contains the Nginx configuration instructions.

-[¹]: We assume the database name and user are both "akkoma". If not, you can find the correct name in your configuration files.  
-[²]: If you have a from source installation, the command is `MIX_ENV=prod mix ecto.migrate`. Note that we prefix with `MIX_ENV=prod` to use the `config/prod.secret.exs` configuration file.  
+[^1]: Prefix with `MIX_ENV=prod` to run it using the production config file.

 ## Remove

 1. Optionally you can remove the users of your instance. This will trigger delete requests for their accounts and posts. Note that this is 'best effort' and doesn't mean that all traces of your instance will be gone from the fediverse.
    * You can do this from the admin-FE where you can select all local users and delete the accounts using the *Moderate multiple users* dropdown.
-    * You can also list local users and delete them individually using the CLI tasks for [Managing users](./CLI_tasks/user.md).
+    * You can also list local users and delete them individualy using the CLI tasks for [Managing users](./CLI_tasks/user.md).
 2. Stop the Akkoma service `systemctl stop akkoma`
-3. Disable Akkoma from systemd `systemctl disable akkoma`
+3. Disable akkoma from systemd `systemctl disable akkoma`
 4. Remove the files and folders you created during installation (see installation guide). This includes the akkoma, nginx and systemd files and folders.
 5. Reload nginx now that the configuration is removed `systemctl reload nginx`
-6. Remove the database and database user[¹] `sudo -Hu postgres psql -c 'DROP DATABASE akkoma;';` `sudo -Hu postgres psql -c 'DROP USER akkoma;'`
+6. Remove the database and database user `sudo -Hu postgres psql -c 'DROP DATABASE <akkoma_db>;';` `sudo -Hu postgres psql -c 'DROP USER <akkoma_db>;'`
 7. Remove the system user `userdel akkoma`
 8. Remove the dependencies that you don't need anymore (see installation guide). Make sure you don't remove packages that are still needed for other software that you have running!
-
-[¹]: We assume the database name and user are both "akkoma". If not, you can find the correct name in your config files.  
-
-## Docker installations
-
-If running behind Docker, it is required to run the above commands inside of a running database container.  
-
-### Example
-Running `docker compose run --rm db pg_dump <...>` will fail and return:
-```
-pg_dump: error: connection to server on socket "/run/postgresql/.s.PGSQL.5432" failed: No such file or directory 
-Is the server running locally and accepting connections on that socket?"
-```
-However, first starting just the database container with `docker compose up db -d`, and then running `docker compose exec db pg_dump -d akkoma --format=custom -f </your/backup/dir/akkoma.pgdump>` will successfully generate a database dump.  
-Then to make the file accessible on the host system you can run `docker compose cp db:</your/backup/dir/akkoma.pgdump> </your/target/location>` to copy if from the container.
--- a/docs/docs/administration/monitoring.md
+++ b/docs/docs/administration/monitoring.md
@ -1,45 +0,0 @@
-# Monitoring Akkoma
-
-If you run akkoma, you may be inclined to collect metrics to ensure your instance is running smoothly,
-and that there's nothing quietly failing in the background.
-
-To facilitate this, akkoma exposes a dashboard and prometheus metrics to be scraped.
-
-## Prometheus
-
-See: [export\_prometheus\_metrics](../../configuration/cheatsheet#instance)
-
-To scrape prometheus metrics, we need an oauth2 token with the `admin:metrics` scope.
-
-consider using [constanze](https://akkoma.dev/AkkomaGang/constanze) to make this easier -
-
-```bash
-constanze token --client-app --scopes "admin:metrics" --client-name "Prometheus"
-```
-
-or see `scripts/create_metrics_app.sh` in the source tree for the process to get this token.
-
-Once you have your token of the form `Bearer $ACCESS_TOKEN`, you can use that in your prometheus config:
-
-```yaml
- job_name: akkoma
-  scheme: https
-  authorization:
-    credentials: $ACCESS_TOKEN # this should have the bearer prefix removed
-  metrics_path: /api/v1/akkoma/metrics
-  static_configs:
-  - targets:
-    - example.com
-```
-
-## Dashboard
-
-Administrators can access a live dashboard under `/phoenix/live_dashboard`
-giving an overview of uptime, software versions, database stats and more.
-
-The dashboard also includes a variation of the prometheus metrics, however
-they do not exactly match due to respective limitations of the dashboard
-and the prometheus exporter.
-Even more important, the dashboard collects metrics locally in the browser
-only while the page is open and cannot give a view on their past history.
-For proper monitoring it is recommended to set up prometheus.
--- a/docs/docs/administration/updating.md
+++ b/docs/docs/administration/updating.md
@ -1,36 +1,17 @@
 # Updating your instance

-You should **always check the [release notes/changelog](https://akkoma.dev/AkkomaGang/akkoma/src/branch/stable/CHANGELOG.md)** in case there are config deprecations, special update steps, etc.
+You should **always check the [release notes/changelog](https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/CHANGELOG.md)** in case there are config deprecations, special update steps, etc.

 Besides that, doing the following is generally enough:
-## Switch to the akkoma user
-```sh
-# Using sudo
-sudo -su akkoma
-
-# Using doas
-doas -su akkoma
-
-# Using su
-su -s "$SHELL" akkoma
-```

 ## For OTP installations
+
 ```sh
-# Download latest stable release
-./bin/pleroma_ctl update --branch stable
+# Download the new release
+su akkoma -s $SHELL -lc "./bin/pleroma_ctl update" 

-# Stop akkoma
-./bin/pleroma stop # or using the system service manager (e.g. systemctl stop akkoma)
-
-# Run database migrations
-./bin/pleroma_ctl migrate
-
-# Start akkoma
-./bin/pleroma daemon # or using the system service manager (e.g. systemctl start akkoma)
-
-# Update frontend(s). See Frontend Configuration doc for more information.
-./bin/pleroma_ctl frontend install pleroma-fe --ref stable
+# Migrate the database, you are advised to stop the instance before doing that
+su akkoma -s $SHELL -lc "./bin/pleroma_ctl migrate"
 ```

 If you selected an alternate flavour on installation, 
@ -38,30 +19,13 @@ you _may_ need to specify `--flavour`, in the same way as
 [when installing](../../installation/otp_en#detecting-flavour).

 ## For from source installations (using git)
-Run as the `akkoma` user:

-```sh
-# fetch changes
-git fetch
-# check out the latest tag
-git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1)
+1. Go to the working directory of Akkoma (default is `/opt/akkoma`)
+2. Run `git pull` [^1]. This pulls the latest changes from upstream.
+3. Run `mix deps.get` [^1]. This pulls in any new dependencies.
+4. Stop the Akkoma service.
+5. Run `mix ecto.migrate` [^1] [^2]. This task performs database migrations, if there were any.
+6. Start the Akkoma service.

-# Run with production configuration
-export MIX_ENV=prod
-
-# Download and compile dependencies
-mix deps.get
-mix compile
-
-# Stop akkoma (replace with your system service manager's equivalent if different)
-sudo systemctl stop akkoma
-
-# Run database migrations
-mix ecto.migrate
-
-# Start akkoma (replace with your system service manager's equivalent if different)
-sudo systemctl start akkoma
-
-# Update Akkoma-FE frontend to latest stable. For other Frontends see Frontend Configuration doc for more information.
-mix pleroma.frontend install pleroma-fe --ref stable
-```
+[^1]: Depending on which install guide you followed (for example on Debian/Ubuntu), you want to run `git` and `mix` tasks as `akkoma` user by adding `sudo -Hu akkoma` before the command.
+[^2]: Prefix with `MIX_ENV=prod` to run it using the production config file.
--- a/docs/docs/clients.md
+++ b/docs/docs/clients.md
@ -1,17 +1,6 @@
 # Akkoma Clients
-This is a list of clients that are known to work with Akkoma.
-
-!!! warning
-    **Clients listed here are not officially supported by the Akkoma project.**
-    Some Akkoma features may be unsupported by these clients.
-
-## Multiplatform
-### Kaiteki
- Homepage: <https://kaiteki.app/>
- Source Code: <https://github.com/Kaiteki-Fedi/Kaiteki>
- Contact: [@kaiteki@social.kaiteki.app](https://social.kaiteki.app/@kaiteki)
- Platforms: Web, Windows, Linux, Android
- Features: MastoAPI, Supports multiple backends
+Note: Additional clients may work, but these are known to work with Akkoma.
+Apps listed here might not support all of Akkoma's features.

 ## Desktop
 ### Whalebird
@ -36,11 +25,17 @@ This is a list of clients that are known to work with Akkoma.
 - Features: MastoAPI, Streaming Ready, Moderation, Text Formatting

 ### Husky
- Source code: <https://codeberg.org/husky/husky>
+- Source code: <https://git.sr.ht/~captainepoch/husky>
 - Contact: [@captainepoch@stereophonic.space](https://stereophonic.space/captainepoch)
 - Platforms: Android
 - Features: MastoAPI, No Streaming, Emoji Reactions, Text Formatting, FE Stickers

+### Fedi
+- Homepage: <https://www.fediapp.com/>
+- Source Code: Proprietary, but gratis
+- Platforms: iOS, Android
+- Features: MastoAPI, Pleroma-specific features like Reactions
+
 ### Tusky
 - Homepage: <https://tuskyapp.github.io/>
 - Source Code: <https://github.com/tuskyapp/Tusky>
@ -48,18 +43,12 @@ This is a list of clients that are known to work with Akkoma.
 - Platforms: Android
 - Features: MastoAPI, No Streaming

-### Subway Tooter
- Source Code: <https://github.com/tateisu/SubwayTooter/>
- Contact: [@SubwayTooter@mastodon.juggler.jp](https://mastodon.juggler.jp/@SubwayTooter)
- Platforms: Android
- Features: MastoAPI, Editing, Emoji Reactions (including custom emoji)
-
 ## Alternative Web Interfaces
-### Enafore
- An actively developed fork of Pinafore with improved Akkoma support
- Homepage: <https://enafore.social/>
- Source Code: <https://github.com/enafore/enafore>
- Contact: [@enfore@enafore.social](https://meta.enafore.social/@enafore)
+### Pinafore
+- Homepage: <https://pinafore.social/>
+- Source Code: <https://github.com/nolanlawson/pinafore>
+- Contact: [@pinafore@mastodon.technology](https://mastodon.technology/users/pinafore)
+- Note: Pleroma support is a secondary goal
 - Features: MastoAPI, No Streaming

 ### Sengi
--- a/docs/docs/configuration/cheatsheet.md
+++ b/docs/docs/configuration/cheatsheet.md
@ -33,8 +33,7 @@ To add configuration to your config file, you can copy it from the base config.
 * `federation_incoming_replies_max_depth`: Max. depth of reply-to activities fetching on incoming federation, to prevent out-of-memory situations while fetching very long threads. If set to `nil`, threads of any depth will be fetched. Lower this value if you experience out-of-memory crashes.
 * `federation_reachability_timeout_days`: Timeout (in days) of each external federation target being unreachable prior to pausing federating to it.
 * `allow_relay`: Permits remote instances to subscribe to all public posts of your instance. This may increase the visibility of your instance.
-* `public`: Allows unauthenticated access to public resources on your instance. This is essentially used as the default value for `:restrict_unauthenticated`. 
-   See `restrict_unauthenticated` for more details.
+* `public`: Makes the client API in authenticated mode-only except for user-profiles. Useful for disabling the Local Timeline and The Whole Known Network. Note that there is a dependent setting restricting or allowing unauthenticated access to specific resources, see `restrict_unauthenticated` for more details.
 * `quarantined_instances`: *DEPRECATED* ActivityPub instances where activities will not be sent. They can still reach there via other means, we just won't send them.
 * `allowed_post_formats`: MIME-type list of formats allowed to be posted (transformed into HTML).
 * `extended_nickname_format`: Set to `true` to use extended local nicknames format (allows underscores/dashes). This will break federation with
@ -62,9 +61,6 @@ To add configuration to your config file, you can copy it from the base config.
 * `password_reset_token_validity`: The time after which reset tokens aren't accepted anymore, in seconds (default: one day).
 * `local_bubble`: Array of domains representing instances closely related to yours. Used to populate the `bubble` timeline. e.g `["example.com"]`, (default: `[]`)
 * `languages`: List of Language Codes used by the instance. This is used to try and set a default language from the frontend. It will try and find the first match between the languages set here and the user's browser languages. It will default to the first language in this setting if there is no match.. (default `["en"]`)
-* `export_prometheus_metrics`: Enable prometheus metrics, served at `/api/v1/akkoma/metrics`, requiring the `admin:metrics` oauth scope.
-* `privileged_staff`: Set to `true` to give moderators access to a few higher responsibility actions.
-* `federated_timeline_available`: Set to `false` to remove access to the federated timeline for all users.

 ## :database
 * `improved_hashtag_timeline`: Setting to force toggle / force disable improved hashtags timeline. `:enabled` forces hashtags to be fetched from `hashtags` table for hashtags timeline. `:disabled` forces object-embedded hashtags to be used (slower). Keep it `:auto` for automatic behaviour (it is auto-set to `:enabled` [unless overridden] when HashtagsTableMigrator completes).
@ -106,60 +102,29 @@ To add configuration to your config file, you can copy it from the base config.
 ## Message rewrite facility

 ### :mrf
-* `transparency`: Make the content of your Message Rewrite Facility settings public (via nodeinfo).
-* `transparency_exclusions`: Exclude specific instance names from MRF transparency.  The use of the exclusions feature will be disclosed in nodeinfo as a boolean value.
-* `transparency_obfuscate_domains`: Show domains with `*` in the middle, to censor them if needed. For example, `ridingho.me` will show as `rid*****.me`
 * `policies`: Message Rewrite Policy, either one or a list. Here are the ones available by default:
    * `Pleroma.Web.ActivityPub.MRF.NoOpPolicy`: Doesn’t modify activities (default).
    * `Pleroma.Web.ActivityPub.MRF.DropPolicy`: Drops all activities. It generally doesn’t makes sense to use in production.
-    * `Pleroma.Web.ActivityPub.MRF.ActivityExpirationPolicy`: Sets a default expiration on all posts made by users of the local instance. Requires `Pleroma.Workers.PurgeExpiredActivity` to be enabled for processing the scheduled delections.
-      (See [`:mrf_activity_expiration`](#mrf_activity_expiration))
-    * `Pleroma.Web.ActivityPub.MRF.AntiFollowbotPolicy`: Drops follow requests from followbots. Users can still allow bots to follow them by first following the bot.
-    * `Pleroma.Web.ActivityPub.MRF.AntiLinkSpamPolicy`: Rejects posts from likely spambots by rejecting posts from new users that contain links.
+    * `Pleroma.Web.ActivityPub.MRF.SimplePolicy`: Restrict the visibility of activities from certains instances (See [`:mrf_simple`](#mrf_simple)).
+    * `Pleroma.Web.ActivityPub.MRF.TagPolicy`: Applies policies to individual users based on tags, which can be set using pleroma-fe/admin-fe/any other app that supports Pleroma Admin API. For example it allows marking posts from individual users nsfw (sensitive).
+    * `Pleroma.Web.ActivityPub.MRF.SubchainPolicy`: Selectively runs other MRF policies when messages match (See [`:mrf_subchain`](#mrf_subchain)).
+    * `Pleroma.Web.ActivityPub.MRF.RejectNonPublic`: Drops posts with non-public visibility settings (See [`:mrf_rejectnonpublic`](#mrf_rejectnonpublic)).
    * `Pleroma.Web.ActivityPub.MRF.EnsureRePrepended`: Rewrites posts to ensure that replies to posts with subjects do not have an identical subject and instead begin with re:.
-    * `Pleroma.Web.ActivityPub.MRF.ForceBotUnlistedPolicy`: Makes all bot posts to disappear from public timelines.
-    * `Pleroma.Web.ActivityPub.MRF.HellthreadPolicy`: Blocks messages with too many mentions.
-      (See [`mrf_hellthread`](#mrf_hellthread))
-    * `Pleroma.Web.ActivityPub.MRF.KeywordPolicy`: Rejects or removes from the federated timeline or replaces keywords. (See [`:mrf_keyword`](#mrf_keyword)).
+    * `Pleroma.Web.ActivityPub.MRF.AntiLinkSpamPolicy`: Rejects posts from likely spambots by rejecting posts from new users that contain links.
    * `Pleroma.Web.ActivityPub.MRF.MediaProxyWarmingPolicy`: Crawls attachments using their MediaProxy URLs so that the MediaProxy cache is primed.
    * `Pleroma.Web.ActivityPub.MRF.MentionPolicy`: Drops posts mentioning configurable users. (See [`:mrf_mention`](#mrf_mention)).
-    * `Pleroma.Web.ActivityPub.MRF.NoEmptyPolicy`: Drops local activities which have no actual content.
-       (e.g. no attachments and only consists of mentions)
-    * `Pleroma.Web.ActivityPub.MRF.NoPlaceholderTextPolicy`: Strips content placeholders from posts
-      (such as the dot from mastodon)
-    * `Pleroma.Web.ActivityPub.MRF.ObjectAgePolicy`: Rejects or delists posts based on their age when received. (See [`:mrf_object_age`](#mrf_object_age)).
-    * `Pleroma.Web.ActivityPub.MRF.RejectNewlyCreatedAccountNotesPolicy`: Rejects posts of users the server only recently learned about for a while. Great to block spam accounts. (See [`:mrf_reject_newly_created_account_notes`](#mrf_reject_newly_created_account_notes))
-    * `Pleroma.Web.ActivityPub.MRF.RejectNonPublic`: Drops posts with non-public visibility settings (See [`:mrf_rejectnonpublic`](#mrf_rejectnonpublic)).
-    * `Pleroma.Web.ActivityPub.MRF.SimplePolicy`: Restrict the visibility of activities from certains instances (See [`:mrf_simple`](#mrf_simple)).
-    * `Pleroma.Web.ActivityPub.MRF.StealEmojiPolicy`: Steals all eligible emoji encountered in posts from remote instances
-      (See [`:mrf_steal_emoji`](#mrf_steal_emoji))
-    * `Pleroma.Web.ActivityPub.MRF.SubchainPolicy`: Selectively runs other MRF policies when messages match (See [`:mrf_subchain`](#mrf_subchain)).
-    * `Pleroma.Web.ActivityPub.MRF.TagPolicy`: Applies policies to individual users based on tags, which can be set using pleroma-fe/admin-fe/any other app that supports Pleroma Admin API. For example it allows marking posts from individual users nsfw (sensitive).
-    * `Pleroma.Web.ActivityPub.MRF.UserAllowListPolicy`: Drops all posts except from users specified in a list.
-      (See [`:mrf_user_allowlist`](#mrf_user_allowlist))
    * `Pleroma.Web.ActivityPub.MRF.VocabularyPolicy`: Restricts activities to a configured set of vocabulary. (See [`:mrf_vocabulary`](#mrf_vocabulary)).
-
-Additionally the following MRFs will *always* be aplied and cannot be disabled:
-
-* `Pleroma.Web.ActivityPub.MRF.DirectMessageDisabledPolicy`: Strips users limiting who can send them DMs from the recipients of non-eligible DMs
-* `Pleroma.Web.ActivityPub.MRF.HashtagPolicy`: Depending on a post’s hashtags it can be rejected, get its sensitive flags force-enabled or removed from the global timeline
-    (See [`:mrf_hashtag`](#mrf_hashtag))
-* `Pleroma.Web.ActivityPub.MRF.InlineQuotePolicy`: Append a link to a post that quotes another post with the link to the quoted post, to ensure that software that does not understand quotes can have full context.
-    (See [`:mrf_inline_quote`](#mrf_inline_quote))
-* `Pleroma.Web.ActivityPub.MRF.NormalizeMarkup`: Pass inbound HTML through a scrubber to make sure it doesn't have anything unusual in it.
-    (See [`:mrf_normalize_markup`](#mrf_normalize_markup))
-
+    * `Pleroma.Web.ActivityPub.MRF.ObjectAgePolicy`: Rejects or delists posts based on their age when received. (See [`:mrf_object_age`](#mrf_object_age)).
+    * `Pleroma.Web.ActivityPub.MRF.ActivityExpirationPolicy`: Sets a default expiration on all posts made by users of the local instance. Requires `Pleroma.Workers.PurgeExpiredActivity` to be enabled for processing the scheduled delections.
+    * `Pleroma.Web.ActivityPub.MRF.ForceBotUnlistedPolicy`: Makes all bot posts to disappear from public timelines.
+    * `Pleroma.Web.ActivityPub.MRF.FollowBotPolicy`: Automatically follows newly discovered users from the specified bot account. Local accounts, locked accounts, and users with "#nobot" in their bio are respected and excluded from being followed.
+    * `Pleroma.Web.ActivityPub.MRF.AntiFollowbotPolicy`: Drops follow requests from followbots. Users can still allow bots to follow them by first following the bot.
+    * `Pleroma.Web.ActivityPub.MRF.KeywordPolicy`: Rejects or removes from the federated timeline or replaces keywords. (See [`:mrf_keyword`](#mrf_keyword)).
+* `transparency`: Make the content of your Message Rewrite Facility settings public (via nodeinfo).
+* `transparency_exclusions`: Exclude specific instance names from MRF transparency.  The use of the exclusions feature will be disclosed in nodeinfo as a boolean value.
+* `transparency_obfuscate_domains`: Show domains with `*` in the middle, to censor them if needed. For example, `ridingho.me` will show as `rid*****.me`

 ## Federation
-### :activitypub
-* `unfollow_blocked`: Whether blocks result in people getting unfollowed
-* `outgoing_blocks`: Whether to federate blocks to other instances
-* `blockers_visible`: Whether a user can see the posts of users who blocked them
-* `deny_follow_blocked`: Whether to disallow following an account that has blocked the user in question
-* `sign_object_fetches`: Sign object fetches with HTTP signatures
-* `authorized_fetch_mode`: Require HTTP signatures for AP fetches
-* `max_collection_objects`: The maximum number of objects to fetch from a remote AP collection.
-
 ### MRF policies

 !!! note
@ -175,7 +140,6 @@ Additionally the following MRFs will *always* be aplied and cannot be disabled:
 * `report_removal`: List of instances to reject reports from and the reason for doing so.
 * `avatar_removal`: List of instances to strip avatars from and the reason for doing so.
 * `banner_removal`: List of instances to strip banners from and the reason for doing so.
-* `background_removal`: List of instances to strip user backgrounds from and the reason for doing so.
 * `reject_deletes`: List of instances to reject deletions from and the reason for doing so.

 #### :mrf_subchain
@ -238,9 +202,7 @@ config :pleroma, :mrf_user_allowlist, %{
 #### :mrf_steal_emoji
 * `hosts`: List of hosts to steal emojis from
 * `rejected_shortcodes`: Regex-list of shortcodes to reject
-* `size_limit`: File size limit (in bytes), checked before download if possible (and remote server honest),
-   otherwise or again checked before saving emoji to the disk
-* `download_unknown_size`: whether to download an emoji when the remote server doesn’t report its size in advance
+* `size_limit`: File size limit (in bytes), checked before an emoji is saved to the disk

 #### :mrf_activity_expiration

@ -256,24 +218,19 @@ Notes:
 - The hashtags in the configuration do not have a leading `#`.
 - This MRF Policy is always enabled, if you want to disable it you have to set empty lists

-#### :mrf_reject_newly_created_account_notes
-After initially encountering an user, all their posts
-will be rejected for the configured time (in seconds).
-Only drops posts. Follows, reposts, etc. are not affected.
+#### :mrf_follow_bot

-* `age`: Time below which to reject (in seconds)
+* `follower_nickname`: The name of the bot account to use for following newly discovered users. Using `followbot` or similar is strongly suggested.

-An example: (86400 seconds = 24 hours)

-```elixir
-config :pleroma, :mrf_reject_newly_created_account_notes, age: 86400
-```
-
-#### :mrf_inline_quote
-* `prefix`: what prefix to prepend to quoted URLs
-
-#### :mrf_normalize_markup
-* `scrub_policy`: the scrubbing module to use (by default a built-in HTML sanitiser)
+### :activitypub
+* `unfollow_blocked`: Whether blocks result in people getting unfollowed
+* `outgoing_blocks`: Whether to federate blocks to other instances
+* `blockers_visible`: Whether a user can see the posts of users who blocked them
+* `deny_follow_blocked`: Whether to disallow following an account that has blocked the user in question
+* `sign_object_fetches`: Sign object fetches with HTTP signatures
+* `authorized_fetch_mode`: Require HTTP signatures for AP fetches
+* `max_collection_objects`: The maximum number of objects to fetch from a remote AP collection.

 ## Pleroma.User

@ -290,11 +247,11 @@ config :pleroma, :mrf_reject_newly_created_account_notes, age: 86400

 ### :frontend_configurations

-This can be used to configure a keyword list that keeps the configuration data for any kind of frontend. By default, settings for `pleroma_fe` and `masto_fe` are configured. You can find the documentation for `pleroma_fe` configuration into [Akkoma-FE configuration and customization for instance administrators](https://docs-fe.akkoma.dev/stable/CONFIGURATION/#options).
+This can be used to configure a keyword list that keeps the configuration data for any kind of frontend. By default, settings for `pleroma_fe` and `masto_fe` are configured. You can find the documentation for `pleroma_fe` configuration into [Pleroma-FE configuration and customization for instance administrators](https://docs-fe.akkoma.dev/stable/CONFIGURATION/#options).

 Frontends can access these settings at `/api/v1/pleroma/frontend_configurations`

-To add your own configuration for Akkoma-FE, use it like this:
+To add your own configuration for Pleroma-FE, use it like this:

 ```elixir
 config :pleroma, :frontend_configurations,
@ -338,7 +295,7 @@ config :pleroma, :frontends,

 * `:primary` - The frontend that will be served at `/`
 * `:admin` - The frontend that will be served at `/pleroma/admin`
-* `:swagger` - Config for developers to act as an API reference to be served at `/pleroma/swaggerui/` (trailing slash _needed_). Disabled by default.
+* `:swagger` - Config for developers to act as an API reference to be served at `/akkoma/swaggerui/` (trailing slash _needed_). Disabled by default.
 * `:mastodon` - The mastodon-fe configuration. This shouldn't need to be changed. This is served at `/web` when installed.

 ### :static\_fe
@ -400,8 +357,7 @@ This section describe PWA manifest instance-specific values. Currently this opti
 ## :media_proxy

 * `enabled`: Enables proxying of remote media to the instance’s proxy
-* `base_url`: The base URL to access a user-uploaded file.
-  Using a (sub)domain distinct from the instance endpoint is **strongly** recommended.
+* `base_url`: The base URL to access a user-uploaded file. Useful when you want to proxy the media files via another host/CDN fronts.
 * `proxy_opts`: All options defined in `Pleroma.ReverseProxy` documentation, defaults to `[max_body_length: (25*1_048_576)]`.
 * `whitelist`: List of hosts with scheme to bypass the mediaproxy (e.g. `https://example.com`)
 * `invalidation`: options for remove media from cache after delete object:
@ -574,6 +530,54 @@ Available caches:
 * `user_agent`: what user agent should we use? (default: `:default`), must be string or `:default`
 * `adapter`: array of adapter options

+### :hackney_pools
+
+Advanced. Tweaks Hackney (http client) connections pools.
+
+There's three pools used:
+
+* `:federation` for the federation jobs.
+  You may want this pool max_connections to be at least equal to the number of federator jobs + retry queue jobs.
+* `:media` for rich media, media proxy
+* `:upload` for uploaded media (if using a remote uploader and `proxy_remote: true`)
+
+For each pool, the options are:
+
+* `max_connections` - how much connections a pool can hold
+* `timeout` - retention duration for connections
+
+
+### :connections_pool
+
+*For `gun` adapter*
+
+Settings for HTTP connection pool.
+
+* `:connection_acquisition_wait` - Timeout to acquire a connection from pool.The total max time is this value multiplied by the number of retries.
+* `connection_acquisition_retries` - Number of attempts to acquire the connection from the pool if it is overloaded. Each attempt is timed `:connection_acquisition_wait` apart.
+* `:max_connections` - Maximum number of connections in the pool.
+* `:connect_timeout` - Timeout to connect to the host.
+* `:reclaim_multiplier` - Multiplied by `:max_connections` this will be the maximum number of idle connections that will be reclaimed in case the pool is overloaded.
+
+### :pools
+
+*For `gun` adapter*
+
+Settings for request pools. These pools are limited on top of `:connections_pool`.
+
+There are four pools used:
+
+* `:federation` for the federation jobs. You may want this pool's max_connections to be at least equal to the number of federator jobs + retry queue jobs.
+* `:media` - for rich media, media proxy.
+* `:upload` - for proxying media when a remote uploader is used and `proxy_remote: true`.
+* `:default` - for other requests.
+
+For each pool, the options are:
+
+* `:size` - limit to how much requests can be concurrently executed.
+* `:recv_timeout` - timeout while `gun` will wait for response
+* `:max_waiting` - limit to how much requests can be waiting for others to finish, after this is reached, subsequent requests will be dropped.
+
 ## Captcha

 ### Pleroma.Captcha
@ -602,11 +606,12 @@ the source code is here: [kocaptcha](https://github.com/koto-bank/kocaptcha). Th

 * `uploader`: Which one of the [uploaders](#uploaders) to use.
 * `filters`: List of [upload filters](#upload-filters) to use.
-* `link_name`: When enabled Akkoma will add a `name` parameter to the url of the upload, for example `https://instance.tld/media/corndog.png?name=corndog.png`. This is needed to provide the correct filename in Content-Disposition headers
-* `base_url`: The base URL to access a user-uploaded file; MUST be configured explicitly.
-  Using a (sub)domain distinct from the instance endpoint is **strongly** recommended. A good value might be `https://media.myakkoma.instance/media/`. 
+* `link_name`: When enabled Akkoma will add a `name` parameter to the url of the upload, for example `https://instance.tld/media/corndog.png?name=corndog.png`. This is needed to provide the correct filename in Content-Disposition headers when using filters like `Pleroma.Upload.Filter.Dedupe`
+* `base_url`: The base URL to access a user-uploaded file. Useful when you want to host the media files via another domain or are using a 3rd party S3 provider.
+* `proxy_remote`: If you're using a remote uploader, Akkoma will proxy media requests instead of redirecting to it.
 * `proxy_opts`: Proxy options, see `Pleroma.ReverseProxy` documentation.
 * `filename_display_max_length`: Set max length of a filename to display. 0 = no limit. Default: 30.
+* `default_description`: Sets which default description an image has if none is set explicitly. Options: nil (default) - Don't set a default, :filename - use the filename of the file, a string (e.g. "attachment") - Use this string

 !!! warning
    `strip_exif` has been replaced by `Pleroma.Upload.Filter.Mogrify`.
@ -643,35 +648,20 @@ config :ex_aws, :s3,

 ### Upload filters

-#### Pleroma.Upload.Filter.Dedupe
-
-**Always** active; cannot be turned off.
-Renames files to their hash and prevents duplicate files filling up the disk.
-No specific configuration.
-
 #### Pleroma.Upload.Filter.AnonymizeFilename

-This filter replaces the declared filename (not the path) of an upload.
+This filter replaces the filename (not the path) of an upload. For complete obfuscation, add
+`Pleroma.Upload.Filter.Dedupe` before AnonymizeFilename.

 * `text`: Text to replace filenames in links. If empty, `{random}.extension` will be used. You can get the original filename extension by using `{extension}`, for example `custom-file-name.{extension}`.

-#### Pleroma.Upload.Filter.Exiftool.StripMetadata
-
-This filter strips metadata with Exiftool leaving color profiles and orientation intact.
-
-* `purge`: List of Exiftool tag names or tag group names to purge
-* `preserve`: List of Exiftool tag names or tag group names to preserve even if they occur in the purge list
-
-
-#### Pleroma.Upload.Filter.Exiftool.ReadDescription
-
-This filter reads the ImageDescription and iptc:Caption-Abstract fields with Exiftool so clients can prefill the media description field.
+#### Pleroma.Upload.Filter.Dedupe

 No specific configuration.

-#### Pleroma.Upload.Filter.OnlyMedia
+#### Pleroma.Upload.Filter.Exiftool

-This filter rejects uploads that are not identified with Content-Type matching audio/\*, image/\*, or video/\*
+This filter only strips the GPS and location metadata with Exiftool leaving color profiles and attributes intact.

 No specific configuration.

@ -845,8 +835,17 @@ config :logger, :ex_syslogger,
  level: :info,
  ident: "pleroma",
  format: "$metadata[$level] $message"
+
+config :quack,
+  level: :warn,
+  meta: [:all],
+  webhook_url: "https://hooks.slack.com/services/YOUR-API-KEY-HERE"
 ```

+See the [Quack Github](https://github.com/azohra/quack) for more details
+
+
+
 ## Database options

 ### RUM indexing for full text search
@ -1012,15 +1011,6 @@ config :ueberauth, Ueberauth,
  ]
 ```

-You may also need to set up your frontend to use oauth logins. For example, for `akkoma-fe`:
-
-```elixir
-config :pleroma, :frontend_configurations,
-  pleroma_fe: %{
-    loginMethod: "token"
-  }
-```
-
 ## Link parsing

 ### :uri_schemes
@ -1102,7 +1092,7 @@ config :pleroma, :database_config_whitelist, [

 ### :restrict_unauthenticated

-Restrict access for unauthenticated users to timelines (public and federated), user profiles and posts.
+Restrict access for unauthenticated users to timelines (public and federated), user profiles and statuses.

 * `timelines`: public and federated timelines
  * `local`: public timeline
@ -1110,24 +1100,13 @@ Restrict access for unauthenticated users to timelines (public and federated), u
 * `profiles`: user profiles
  * `local`
  * `remote`
-* `activities`: posts
+* `activities`: statuses
  * `local`
  * `remote`

-#### When :instance, :public is `true`
+Note: when `:instance, :public` is set to `false`, all `:restrict_unauthenticated` items be effectively set to `true` by default. If you'd like to allow unauthenticated access to specific API endpoints on a private instance, please explicitly set `:restrict_unauthenticated` to non-default value in `config/prod.secret.exs`.

-When your instance is in "public" mode, all public resources (users, posts, timelines) are accessible to unauthenticated users.
-
-Turning any of the `:restrict_unauthenticated` options to `true` will restrict access to the corresponding resources.
-
-#### When :instance, :public is `false`
-
-When `:instance, :public` is set to `false`, all of the `:restrict_unauthenticated` options will effectively be set to `true` by default,
-meaning that only authenticated users will be able to access the corresponding resources.
-
-If you'd like to allow unauthenticated access to specific resources, you can turn these settings to `false`.
-
-**Note**: setting `restrict_unauthenticated/timelines/local` to `true` has no practical sense if `restrict_unauthenticated/timelines/federated` is set to `false` (since local public activities will still be delivered to unauthenticated users as part of federated timeline).
+Note: setting `restrict_unauthenticated/timelines/local` to `true` has no practical sense if `restrict_unauthenticated/timelines/federated` is set to `false` (since local public activities will still be delivered to unauthenticated users as part of federated timeline).

 ## Pleroma.Web.ApiSpec.CastAndValidate

@ -1187,7 +1166,7 @@ Each job has these settings:
 ### Translation Settings

 Settings to automatically translate statuses for end users. Currently supported
-translation services are DeepL and LibreTranslate. The supported command line tool is [Argos Translate](https://github.com/argosopentech/argos-translate).
+translation services are DeepL and LibreTranslate.

 Translations are available at `/api/v1/statuses/:id/translations/:language`, where
 `language` is the target language code (e.g `en`)
@ -1196,7 +1175,7 @@ Translations are available at `/api/v1/statuses/:id/translations/:language`, whe

 - `:enabled` - enables translation
 - `:module` - Sets module to be used
-  - Either `Pleroma.Akkoma.Translators.DeepL`, `Pleroma.Akkoma.Translators.LibreTranslate`, or `Pleroma.Akkoma.Translators.ArgosTranslate`
+  - Either `Pleroma.Akkoma.Translators.DeepL` or `Pleroma.Akkoma.Translators.LibreTranslate`

 ### `:deepl`

@ -1208,9 +1187,3 @@ Translations are available at `/api/v1/statuses/:id/translations/:language`, whe

 - `:url` - URL of LibreTranslate instance
 - `:api_key` - API key for LibreTranslate
-
-### `:argos_translate`
-
- `:command_argos_translate` - command for `argos-translate`. Can be the command if it's in your PATH, or the full path to the file  (default: `argos-translate`).
- `:command_argospm` - command for `argospm`. Can be the command if it's in your PATH, or the full path to the file (default: `argospm`).
- `:strip_html` - Strip html from the post before translating it (default: `true`).
--- a/docs/docs/configuration/custom_emoji.md
+++ b/docs/docs/configuration/custom_emoji.md
@ -67,29 +67,3 @@ Priority of tags assigns in emoji.txt and custom.txt:
 Priority for globs:

 `special group setting in config.exs > default setting in config.exs`
-
-## Stealing emoji
-
-Managing your emoji can be hard work, and you just want to have the cool emoji your friends use? As usual, crime comes to the rescue!
-
-You can use the `Pleroma.Web.ActivityPub.MRF.StealEmojiPolicy` [Message Rewrite Facility](../configuration/cheatsheet.md#mrf) to automatically add to your instance emoji that messages from specific servers contain. Note that this happens on message processing, so the emoji will be added only after your instance receives some interaction containing emoji _after_ configuring this.
-
-To activate this you have to [configure](../configuration/cheatsheet.md#mrf_steal_emoji) it in your configuration file. For example if you wanted to steal any emoji that is not related to cinnamon and not larger than about 10K from `coolemoji.space` and `spiceenthusiasts.biz`, you would add the following:
-```elixir
-config :pleroma, :mrf,
-  policies: [
-    Pleroma.Web.ActivityPub.MRF.StealEmojiPolicy
-  ]
-
-config :pleroma, :mrf_steal_emoji,
-  hosts: [
-    "coolemoji.space",
-    "spiceenthusiasts.biz"
-  ],
-  rejected_shortcodes: [
-    ".*cinnamon.*"
-  ],
-  size_limit: 10000
-```
-
-Note that this may not obey emoji licensing restrictions. It's extremely unlikely that anyone will care, but keep this in mind for when Nintendo starts their own instance.
--- a/docs/docs/configuration/frontend_management.md
+++ b/docs/docs/configuration/frontend_management.md
@ -26,7 +26,7 @@ config :pleroma, :frontends,
  }
 ```

-This would serve the frontend from the folder at `$instance_static/frontends/pleroma/stable`. You have to copy the frontend into this folder yourself. You can choose the name and ref any way you like, but they will be used by mix tasks to automate installation in the future, the name referring to the project and the ref referring to a commit.
+This would serve the frontend from the the folder at `$instance_static/frontends/pleroma/stable`. You have to copy the frontend into this folder yourself. You can choose the name and ref any way you like, but they will be used by mix tasks to automate installation in the future, the name referring to the project and the ref referring to a commit.

 Refer to [the frontend CLI task](../../administration/CLI_tasks/frontend) for how to install the frontend's files

@ -60,4 +60,4 @@ config :pleroma, :frontends,

 Then run the [pleroma.frontend cli task](../../administration/CLI_tasks/frontend) with the name of `swagger-ui` to install the distribution files.

-You will now be able to view documentation at `/pleroma/swaggerui`
+You will now be able to view documentation at `/akkoma/swaggerui`
--- a/docs/docs/configuration/hardening.md
+++ b/docs/docs/configuration/hardening.md
@ -17,16 +17,6 @@ This sets the Akkoma application server to only listen to the localhost interfac

 This sets the `secure` flag on Akkoma’s session cookie. This makes sure, that the cookie is only accepted over encrypted HTTPs connections. This implicitly renames the cookie from `pleroma_key` to `__Host-pleroma-key` which enforces some restrictions. (see [cookie prefixes](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie#Cookie_prefixes))

-### `Pleroma.Upload, :uploader, :base_url`
-
-> Recommended value: *anything on a different domain than the instance endpoint; e.g. https://media.myinstance.net/*
-
-Uploads are user controlled and (unless you’re running a true single-user
-instance) should therefore not be considered trusted. But the domain is used
-as a pivilege boundary e.g. by HTTP content security policy and ActivityPub.
-Having uploads on the same domain enabled several past vulnerabilities
-able to be exploited by malicious users.
-
 ### `:http_security`

 > Recommended value: `true`
@ -65,11 +55,11 @@ An additional “Strict transport security” header will be sent with the confi

 > Recommended value: `same-origin`

-If you click on a link, your browser’s request to the other site will include from where it is coming from. The “Referrer policy” header tells the browser how and if it should send this information. (see [Referrer policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy)). `no-referrer` can be used if a referrer is not needed for improved privacy.
+If you click on a link, your browser’s request to the other site will include from where it is coming from. The “Referrer policy” header tells the browser how and if it should send this information. (see [Referrer policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy))

 ## systemd

-A systemd unit example is provided at `installation/akkoma.service`.
+A systemd unit example is provided at `installation/pleroma.service`.

 ### PrivateTmp

--- a/docs/docs/configuration/integrations/howto_ejabberd.md
+++ b/docs/docs/configuration/integrations/howto_ejabberd.md
--- a/docs/docs/configuration/howto_mediaproxy.md
+++ b/docs/docs/configuration/howto_mediaproxy.md
@ -6,18 +6,29 @@ With the `mediaproxy` function you can use nginx to cache this content, so users

 ## Activate it

-* Set up a subdomain for the proxy with its nginx config on the same machine
-* Edit the nginx config for the upload/MediaProxy subdomain to point to the subdomain that has been set up
+* Edit your nginx config and add the following location: 
+```
+location /proxy {
+        proxy_cache akkoma_media_cache;
+        proxy_cache_lock on;
+        proxy_pass http://localhost:4000;
+}
+```
+Also add the following on top of the configuration, outside of the `server` block:
+```
+proxy_cache_path /tmp/akkoma-media-cache levels=1:2 keys_zone=akkoma_media_cache:10m max_size=10g inactive=720m use_temp_path=off;
+```
+If you came here from one of the installation guides, take a look at the example configuration `/installation/nginx/akkoma.nginx`, where this part is already included.
+
 * Append the following to your `prod.secret.exs` or `dev.secret.exs` (depends on which mode your instance is running):
-```elixir
-# Replace media.example.td with the subdomain you set up earlier
+```
 config :pleroma, :media_proxy,
      enabled: true,
      proxy_opts: [
            redirect_on_failure: true
-      ],
-      base_url: "https://media.example.tld"
+      ]
+      #base_url: "https://cache.akkoma.social"
 ```
-You **really** should use a subdomain to serve proxied files; while we will fix bugs resulting from this, serving arbitrary remote content on your main domain namespace is a significant attack surface.
+If you want to use a subdomain to serve the files, uncomment `base_url`, change the url and add a comma after `true` in the previous line.

 * Restart nginx and Akkoma
--- a/docs/docs/configuration/integrations/howto_mongooseim.md
+++ b/docs/docs/configuration/integrations/howto_mongooseim.md
--- a/docs/docs/configuration/howto_theming_your_instance.md
+++ b/docs/docs/configuration/howto_theming_your_instance.md
@ -6,7 +6,7 @@ To add a custom theme to your instance, you'll first need to get a custom theme,

 ### Create your own theme

-* You can create your own theme using the Akkoma FE by going to settings (gear on the top right) and choose the Theme tab. Here you have the options to create a personal theme.
+* You can create your own theme using the Pleroma FE by going to settings (gear on the top right) and choose the Theme tab. Here you have the options to create a personal theme.
 * To download your theme, you can do Save preset
 * If you want to upload a theme to customise it further, you can upload it using Load preset

@ -60,7 +60,7 @@ Example of `my-awesome-theme.json` where we add the name "My Awesome Theme"

 ### Set as default theme

-Now we can set the new theme as default in the [Pleroma FE configuration](https://docs-fe.akkoma.dev/stable/CONFIGURATION/).
+Now we can set the new theme as default in the [Pleroma FE configuration](https://docs-fe.akkoma.dev/stable/CONFIGURATION).

 Example of adding the new theme in the back-end config files
 ```elixir
--- a/docs/docs/configuration/i2p.md
+++ b/docs/docs/configuration/i2p.md
@ -130,26 +130,59 @@ config :pleroma, :http_security,
  enabled: false
 ```

-In the Nginx config, add the following into the `location /` block:
-```nginx
+Use this as the Nginx config:
+```
+proxy_cache_path /tmp/akkoma-media-cache levels=1:2 keys_zone=akkoma_media_cache:10m max_size=10g inactive=720m use_temp_path=off;
+# The above already exists in a clearnet instance's config.
+# If not, add it.
+
+server {
+    listen 127.0.0.1:14447;
+    server_name youri2paddress;
+
+    # Comment to enable logs
+    access_log /dev/null;
+    error_log /dev/null;
+
+    gzip_vary on;
+    gzip_proxied any;
+    gzip_comp_level 6;
+    gzip_buffers 16 8k;
+    gzip_http_version 1.1;
+    gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript application/activity+json application/atom+xml;
+
+    client_max_body_size 16m;
+
+    location / {
+
        add_header X-XSS-Protection "0";
        add_header X-Permitted-Cross-Domain-Policies none;
        add_header X-Frame-Options DENY;
        add_header X-Content-Type-Options nosniff;
        add_header Referrer-Policy same-origin;
-```

-Change the `listen` directive to the following:
-```nginx
-listen 127.0.0.1:14447;
-```
+        proxy_http_version 1.1;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection "upgrade";
+        proxy_set_header Host $http_host;

-Set `server_name` to your i2p address.
+        proxy_pass http://localhost:4000;

-Reload Nginx:
+        client_max_body_size 16m;
+    }
+
+    location /proxy {
+        proxy_cache akkoma_media_cache;
+        proxy_cache_lock on;
+        proxy_ignore_client_abort on;
+        proxy_pass http://localhost:4000;
+    }
+}
 ```
-systemctl restart i2pd.service --no-block
-systemctl reload nginx.service
+reload Nginx:
+```
+systemctl stop i2pd.service --no-block
+systemctl start i2pd.service
 ```
 *Notice:* The stop command initiates a graceful shutdown process, i2pd stops after finishing to route transit tunnels (maximum 10 minutes).

--- a/docs/docs/configuration/mrf.md
+++ b/docs/docs/configuration/mrf.md
@ -15,6 +15,18 @@ The MRF provides user-configurable policies. The default policy is `NoOpPolicy`,

 It is possible to use multiple, active MRF policies at the same time.

+## Quarantine Instances
+
+You have the ability to prevent from private / followers-only messages from federating with specific instances. Which means they will only get the public or unlisted messages from your instance.
+
+If, for example, you're using `MIX_ENV=prod` aka using production mode, you would open your configuration file located in `config/prod.secret.exs` and edit or add the option under your `:instance` config object. Then you would specify the instance within quotes.
+
+```elixir
+config :pleroma, :instance,
+  [...]
+  quarantined_instances: ["instance.example", "other.example"]
+```
+
 ## Using `SimplePolicy`

 `SimplePolicy` is capable of handling most common admin tasks.
@ -29,13 +41,12 @@ config :pleroma, :mrf,

 Once `SimplePolicy` is enabled, you can configure various groups in the `:mrf_simple` config object. These groups are:

-* `reject`: Servers in this group will have their messages rejected. Also outbound messages will not be sent to these servers.
+* `reject`: Servers in this group will have their messages rejected.
 * `accept`: If not empty, only messages from these instances will be accepted (whitelist federation).
 * `media_nsfw`: Servers in this group will have the #nsfw tag and sensitive setting injected into incoming messages which contain media.
 * `media_removal`: Servers in this group will have media stripped from incoming messages.
 * `avatar_removal`: Avatars from these servers will be stripped from incoming messages.
 * `banner_removal`: Banner images from these servers will be stripped from incoming messages.
-* `background_removal`: User background images from these servers will be stripped from incoming messages.
 * `report_removal`: Servers in this group will have their reports (flags) rejected.
 * `federated_timeline_removal`: Servers in this group will have their messages unlisted from the public timelines by flipping the `to` and `cc` fields.
 * `reject_deletes`: Deletion requests will be rejected from these servers.
@ -62,32 +73,6 @@ config :pleroma, :mrf_simple,

 The effects of MRF policies can be very drastic. It is important to use this functionality carefully. Always try to talk to an admin before writing an MRF policy concerning their instance.

-## Hiding or Obfuscating Policies
-
-You can opt out of publicly displaying all MRF policies or only hide or obfuscate selected domains.
-
-To just hide everything set:
-
-```elixir
-config :pleroma, :mrf,
-  ...
-  transparency: false,
-```
-
-To hide or obfuscate only select entries, use:
-
-```elixir
-config :pleroma, :mrf,
-  ...
-  transparency_obfuscate_domains: ["handholdi.ng", "badword.com"],
-  transparency_exclusions: [{"ghost.club", "even a fragment is too spoopy for humans"}]
-```
-
-## More MRF Policies
-
-See the [documentation cheatsheet](cheatsheet.md)
-for all available MRF policies and their options.
-
 ## Writing your own MRF Policy

 As discussed above, the MRF system is a modular system that supports pluggable policies. This means that an admin may write a custom MRF policy in Elixir or any other language that runs on the Erlang VM, by specifying the module name in the `policies` config setting.
--- a/docs/docs/configuration/onion_federation.md
+++ b/docs/docs/configuration/onion_federation.md
@ -74,23 +74,56 @@ config :pleroma, :http_security,
  enabled: false
 ```

-In the Nginx config, add the following into the `location /` block:
-```nginx
+Use this as the Nginx config:
+```
+proxy_cache_path /tmp/akkoma-media-cache levels=1:2 keys_zone=akkoma_media_cache:10m max_size=10g inactive=720m use_temp_path=off;
+# The above already exists in a clearnet instance's config.
+# If not, add it.
+
+server {
+    listen 127.0.0.1:8099;
+    server_name youronionaddress;
+
+    # Comment to enable logs
+    access_log /dev/null;
+    error_log /dev/null;
+
+    gzip_vary on;
+    gzip_proxied any;
+    gzip_comp_level 6;
+    gzip_buffers 16 8k;
+    gzip_http_version 1.1;
+    gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript application/activity+json application/atom+xml;
+
+    client_max_body_size 16m;
+
+    location / {
+
        add_header X-XSS-Protection "0";
        add_header X-Permitted-Cross-Domain-Policies none;
        add_header X-Frame-Options DENY;
        add_header X-Content-Type-Options nosniff;
        add_header Referrer-Policy same-origin;
+
+        proxy_http_version 1.1;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection "upgrade";
+        proxy_set_header Host $http_host;
+
+        proxy_pass http://localhost:4000;
+
+        client_max_body_size 16m;
+    }
+
+    location /proxy {
+        proxy_cache akkoma_media_cache;
+        proxy_cache_lock on;
+        proxy_ignore_client_abort on;
+        proxy_pass http://localhost:4000;
+    }
+}
 ```
-
-Change the `listen` directive to the following:
-```nginx
-listen 127.0.0.1:8099;
-```
-
-Set the `server_name` to your onion address.
-
-Reload Nginx:
+reload Nginx:
 ```
 systemctl reload nginx
 ```
--- a/docs/docs/configuration/optimisation/varnish_cache.md
+++ b/docs/docs/configuration/optimisation/varnish_cache.md
@ -1,54 +0,0 @@
-# Using a Varnish Cache
-
-Varnish is a layer that sits between your web server and your backend application -
-it does something similar to nginx caching, but tends to be optimised for speed over
-all else.
-
-To set up a varnish cache, first you'll need to install varnish. 
-
-This will vary by distribution, and since this is a rather advanced guide,
-no copy-paste instructions are provided. It's probably in your distribution's
-package manager, though. `apt-get install varnish` and so on.
-
-Once you have varnish installed, you'll need to configure it to work with akkoma.
-
-Copy the configuration file to the varnish configuration directory:
-
-    cp installation/akkoma.vcl /etc/varnish/akkoma.vcl
-
-You may want to check if varnish added a `default.vcl` file to the same directory,
-if so you can just remove it without issue.
-
-Then boot up varnish, probably `systemctl start varnish` or `service varnish start`.
-
-Now you should be able to `curl -D- localhost:6081` and see a bunch of
-akkoma javascript.
-
-Once that's out of the way, we can point our webserver at varnish. This
-
-=== "Nginx"
-
-    upstream phoenix {
-        server 127.0.0.1:6081 max_fails=5 fail_timeout=60s;
-    }
-
-
-=== "Caddy"
-
-    reverse_proxy 127.0.0.1:6081
-
-Now hopefully it all works
-
-If you get a HTTPS redirect loop, you may need to remove this part of the VCL
-
-```vcl
-if (std.port(server.ip) != 443) {
-      set req.http.X-Forwarded-Proto = "http";
-      set req.http.x-redir = "https://" + req.http.host + req.url;
-      return (synth(750, ""));
-} else {
-  set req.http.X-Forwarded-Proto = "https";
-}
-```
-
-This will allow your webserver alone to handle redirects.
--- a/docs/docs/configuration/optimisation/optimizing_beam.md
+++ b/docs/docs/configuration/optimisation/optimizing_beam.md
@ -25,14 +25,11 @@ Tuning the BEAM requires you provide a config file normally called [vm.args](htt

 `ExecStart=/usr/bin/elixir --erl '-args_file /opt/akkoma/config/vm.args' -S /usr/bin/mix phx.server`

-If using an OTP release, set the `RELEASE_VM_ARGS` environment variable to the path to the vm.args file.
-
 Check your OS documentation to adopt a similar strategy on other platforms.

 ### Virtual Machine and/or few CPU cores

-Disable the busy-waiting. This should generally be done if you're on a platform that does burst scheduling, like AWS, or if you're running other
-services on the same machine.
+Disable the busy-waiting. This should generally only be done if you're on a platform that does burst scheduling, like AWS.

 **vm.args:**

@ -42,8 +39,6 @@ services on the same machine.
 +sbwtdio none
 ```

-These settings are enabled by default for OTP releases
-
 ### Dedicated Hardware

 Enable more busy waiting, increase the internal maximum limit of BEAM processes and ports. You can use this if you run on dedicated hardware, but it is not necessary.
--- a/docs/docs/configuration/postgresql.md
+++ b/docs/docs/configuration/postgresql.md
@ -4,10 +4,45 @@ Akkoma performance is largely dependent on performance of the underlying databas

 ## PGTune

-[PgTune](https://pgtune.leopard.in.ua) can be used to get recommended settings. Make sure to set the DB type to "Online transaction processing system" for optimal performance. Also set the number of connections to between 25 and 30. This will allow each connection to have access to more resources while still leaving some room for running maintenance tasks while the instance is still running. 
+[PgTune](https://pgtune.leopard.in.ua) can be used to get recommended settings. Be sure to set "Number of Connections" to 20, otherwise it might produce settings hurtful to database performance. It is also recommended to not use "Network Storage" option.

-It is also recommended to not use "Network Storage" option.
+## Disable generic query plans

-If your server runs other services, you may want to take that into account. E.g. if you have 4G ram, but 1G of it is already used for other services, it may be better to tell PGTune you only have 3G.
+When PostgreSQL receives a query, it decides on a strategy for searching the requested data, this is called a query plan. The query planner has two modes: generic and custom. Generic makes a plan for all queries of the same shape, ignoring the parameters, which is then cached and reused. Custom, on the contrary, generates a unique query plan based on query parameters.

-In the end, PGTune only provides recomended settings, you can always try to finetune further.
+By default PostgreSQL has an algorithm to decide which mode is more efficient for particular query, however this algorithm has been observed to be wrong on some of the queries Akkoma sends, leading to serious performance loss. Therefore, it is recommended to disable generic mode.
+
+
+Akkoma already avoids generic query plans by default, however the method it uses is not the most efficient because it needs to be compatible with all supported PostgreSQL versions. For PostgreSQL 12 and higher additional performance can be gained by adding the following to Akkoma configuration:
+```elixir
+config :pleroma, Pleroma.Repo,
+  prepare: :named,
+  parameters: [
+    plan_cache_mode: "force_custom_plan"
+  ]
+```
+
+A more detailed explaination of the issue can be found at <https://blog.soykaf.com/post/postgresql-elixir-troubles/>.
+
+## Example configurations
+
+Here are some configuration suggestions for PostgreSQL 10+.
+
+### 1GB RAM, 1 CPU
+```
+shared_buffers = 256MB
+effective_cache_size = 768MB
+maintenance_work_mem = 64MB
+work_mem = 13107kB
+```
+
+### 2GB RAM, 2 CPU
+```
+shared_buffers = 512MB
+effective_cache_size = 1536MB
+maintenance_work_mem = 128MB
+work_mem = 26214kB
+max_worker_processes = 2
+max_parallel_workers_per_gather = 1
+max_parallel_workers = 2
+```
--- a/docs/docs/configuration/search.md
+++ b/docs/docs/configuration/search.md
@ -33,7 +33,6 @@ indexes faster when it can process many posts in a single batch.
 > config :pleroma, Pleroma.Search.Meilisearch,
 >    url: "http://127.0.0.1:7700/",
 >    private_key: "private key",
->    search_key: "search key",
 >    initial_indexing_chunk_size: 100_000

 Information about setting up meilisearch can be found in the
@ -46,7 +45,7 @@ is hardly usable on a somewhat big instance.
 ### Private key authentication (optional)

 To set the private key, use the `MEILI_MASTER_KEY` environment variable when starting. After setting the _master key_,
-you have to get the _private key_ and possibly _search key_, which are actually used for authentication.
+you have to get the _private key_, which is actually used for authentication.

 === "OTP"
    ```sh
@ -58,11 +57,7 @@ you have to get the _private key_ and possibly _search key_, which are actually
    mix pleroma.search.meilisearch show-keys <your master key here>
    ```

-You will see a "Default Admin API Key", this is the key you actually put into
-your configuration file as `private_key`. You should also see a
-"Default Search API key", put this into your config as `search_key`.
-If your version of Meilisearch only showed the former,
-just leave `search_key` completely unset in Akkoma's config.
+You will see a "Default Admin API Key", this is the key you actually put into your configuration file.

 ### Initial indexing

--- a/docs/docs/configuration/static_dir.md
+++ b/docs/docs/configuration/static_dir.md
@ -100,12 +100,3 @@ the `frontends` directory.
 ## Styling rendered pages

 To overwrite the CSS stylesheet of the OAuth form and other static pages, you can upload your own CSS file to `instance/static/static.css`. This will completely replace the CSS used by those pages, so it might be a good idea to copy the one from `priv/static/instance/static.css` and make your changes.
-
-## Overriding pleroma-fe styles
-
-To overwrite the CSS stylesheet of pleroma-fe, you can put a file at
-`$static_dir/static/custom.css` containing your styles. These will be loaded
-with the rest of the CSS.
-
-You will probably have to put `!important` on most/all your styles to override the
-default ones, due to the specificity precedence of CSS.
--- a/docs/docs/configuration/storing_remote_media.md
+++ b/docs/docs/configuration/storing_remote_media.md
@ -6,46 +6,33 @@ as soon as the post is received by your instance.

 ## Nginx

-The following are excerpts from the [suggested nginx config](https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/installation/nginx/akkoma.nginx) that demonstrates the necessary config for the media proxy to work.
-
-A `proxy_cache_path` must be defined, for example:
-
 ```
    proxy_cache_path /long/term/storage/path/akkoma-media-cache levels=1:2
        keys_zone=akkoma_media_cache:10m inactive=1y use_temp_path=off;
-```

-The `proxy_cache_path` must then be configured for use with media proxy paths:
-
-```
    location ~ ^/(media|proxy) {
        proxy_cache        akkoma_media_cache;
        slice              1m;
        proxy_cache_key    $host$uri$is_args$args$slice_range;
        proxy_set_header   Range $slice_range;
-        proxy_cache_valid  200 206 301 304 1h;
-        proxy_cache_lock   on;
+        proxy_http_version 1.1;
+        proxy_cache_valid  206 301 302 304 1h;
+        proxy_cache_valid  200 1y;
+        proxy_cache_use_stale error timeout invalid_header updating;
        proxy_ignore_client_abort on;
        proxy_buffering    on;
        chunked_transfer_encoding on;
-        proxy_pass         http://phoenix;
-    }
+        proxy_ignore_headers Cache-Control Expires;
+        proxy_hide_header  Cache-Control Expires;
+        proxy_pass         http://127.0.0.1:4000;
    }
 ```

-Ensure that `proxy_http_version 1.1;` is set for the above `location` block. In the suggested config, this is already the case.
-
 ## Akkoma

-### File-based Configuration
-
-If you're using static file configuration, add the `MediaProxyWarmingPolicy` to your MRF policies. For example:
+Add to your `prod.secret.exs`:

 ```
 config :pleroma, :mrf,
  policies: [Pleroma.Web.ActivityPub.MRF.MediaProxyWarmingPolicy]
 ```
-
-### Database Configuration
-
-In the admin interface, add `MediaProxyWarmingPolicy` to the `Policies` option under `Settings` → `MRF`.
--- a/docs/docs/development/API/admin_api.md
+++ b/docs/docs/development/API/admin_api.md
@ -2,7 +2,7 @@

 Authentication is required and the user must be an admin.

-Backwards-compatibility for admin API endpoints without version prefixes (`/api/pleroma/admin/*`) has been removed as of Akkoma 3.6.0. Please use `/api/v1/pleroma/admin/*` instead.
+The `/api/v1/pleroma/admin/*` path is backwards compatible with `/api/pleroma/admin/*` (`/api/pleroma/admin/*` will be deprecated in the future).

 ## `GET /api/v1/pleroma/admin/users`

@ -1033,6 +1033,7 @@ Most of the settings will be applied in `runtime`, this means that you don't nee
  - `:pools`
 - partially settings inside these keys:
  - `:seconds_valid` in `Pleroma.Captcha`
+  - `:proxy_remote` in `Pleroma.Upload`
  - `:upload_limit` in `:instance`

 - Params:
@ -1055,13 +1056,14 @@ Most of the settings will be applied in `runtime`, this means that you don't nee

 Example of setting without keyword in value:
 ```elixir
-config :tesla, :adapter, {Tesla.Adapter.Finch, name: MyFinch}
+config :tesla, :adapter, Tesla.Adapter.Hackney
 ```

 List of settings which support only full update by key:
 ```elixir
@full_key_update [
    {:pleroma, :ecto_repos},
+    {:quack, :meta},
    {:mime, :types},
    {:cors_plug, [:max_age, :methods, :expose, :headers]},
    {:auto_linker, :opts},
@ -1081,6 +1083,22 @@ List of settings which support only full update by subkey:
  ]
 ```

+*Settings without explicit key must be sended in separate config object params.*
+```elixir
+config :quack,
+  level: :debug,
+  meta: [:all],
+  ...
+```
+```json
+{
+  "configs": [
+    {"group": ":quack", "key": ":level", "value": ":debug"},
+    {"group": ":quack", "key": ":meta", "value": [":all"]},
+    ...
+  ]
+}
+```
 - Request:

 ```json
@ -1093,6 +1111,7 @@ List of settings which support only full update by subkey:
        {"tuple": [":uploader", "Pleroma.Uploaders.Local"]},
        {"tuple": [":filters", ["Pleroma.Upload.Filter.Dedupe"]]},
        {"tuple": [":link_name", true]},
+        {"tuple": [":proxy_remote", false]},
        {"tuple": [":proxy_opts", [
          {"tuple": [":redirect_on_failure", false]},
          {"tuple": [":max_body_length", 1048576]},
--- a/docs/docs/development/API/akkoma_api.md
+++ b/docs/docs/development/API/akkoma_api.md
@ -1,146 +0,0 @@
-# Akkoma API
-
-Request authentication (if required) and parameters work the same as for [Pleroma API](pleroma_api.md).
-
-## `/api/v1/akkoma/preferred_frontend/available`
-### Returns the available frontends which can be picked as the preferred choice
-* Method: `GET`
-* Authentication: not required
-* Params: none
-* Response: JSON
-* Example response:
-```json
-["pleroma-fe/stable"]
-```
-
-!!! note
-    There’s also a browser UI under `/akkoma/frontend`
-    for interactively querying and changing this.
-
-## `/api/v1/akkoma/preferred_frontend`
-### Configures the preferred frontend of this session
-* Method: `PUT`
-* Authentication: not required
-* Params:
-    * `frontend_name`: STRING containing one of the available frontends
-* Response: JSON
-* Example response:
-```json
-{"frontend_name":"pleroma-fe/stable"}
-```
-
-!!! note
-    There’s also a browser UI under `/akkoma/frontend`
-    for interactively querying and changing this.
-
-## `/api/v1/akkoma/metrics`
-### Provides metrics for Prometheus to scrape
-* Method: `GET`
-* Authentication: required (admin:metrics)
-* Params: none
-* Response: text
-* Example response:
-```
-# HELP pleroma_remote_users_total
-# TYPE pleroma_remote_users_total gauge
-pleroma_remote_users_total 25
-# HELP pleroma_local_statuses_total
-# TYPE pleroma_local_statuses_total gauge
-pleroma_local_statuses_total 17
-# HELP pleroma_domains_total
-# TYPE pleroma_domains_total gauge
-pleroma_domains_total 4
-# HELP pleroma_local_users_total
-# TYPE pleroma_local_users_total gauge
-pleroma_local_users_total 3
-...
-```
-
-## `/api/v1/akkoma/translation/languages`
-### Returns available source and target languages for automated text translation
-* Method: `GET`
-* Authentication: required
-* Params: none
-* Response: JSON
-* Example response:
-```json
-{
-  "source": [
-    {"code":"LV", "name":"Latvian"},
-    {"code":"ZH", "name":"Chinese (traditional)"},
-    {"code":"EN-US", "name":"English (American)"}
-  ],
-  "target": [
-    {"code":"EN-GB", "name":"English (British)"},
-    {"code":"JP", "name":"Japanese"}
-  ]
-}
-```
-
-## `/api/v1/akkoma/frontend_settings/:frontend_name`
-### Lists all configuration profiles of the selected frontend for the current user
-* Method: `GET`
-* Authentication: required
-* Params: none
-* Response: JSON
-* Example response:
-```json
-[
-  {"name":"default","version":31}
-]
-```
-
-## `/api/v1/akkoma/frontend_settings/:frontend_name/:profile_name`
-### Returns the full selected frontend settings profile of the current user
-* Method: `GET`
-* Authentication: required
-* Params: none
-* Response: JSON
-* Example response:
-```json
-{
-  "version": 31,
-  "settings": {
-    "streaming": true,
-    "conversationDisplay": "tree",
-    ...
-  }
-}
-```
-
-## `/api/v1/akkoma/frontend_settings/:frontend_name/:profile_name`
-### Updates the frontend settings profile
-* Method: `PUT`
-* Authentication: required
-* Params:
-    * `version`: INTEGER
-    * `settings`: JSON object containing the entire new settings
-* Response: JSON
-* Example response:
-```json
-{
-  "streaming": false,
-  "conversationDisplay": "tree",
-  ...
-}
-```
-
-!!! note
-    The `version` field must be increased by exactly one on each update
-
-## `/api/v1/akkoma/frontend_settings/:frontend_name/:profile_name`
-### Drops the specified frontend settings profile
-* Method: `DELETE`
-* Authentication: required
-* Params: none
-* Response: JSON
-* Example response:
-```json
-{"deleted":"ok"}
-```
-
-
-## `/api/v1/timelines/bubble`
-### Returns a timeline for the local and closely related instances
-Works like all other Mastodon-API timeline queries with the documented
-[Akkoma-specific additions and tweaks](./differences_in_mastoapi_responses.md#timelines).
--- a/docs/docs/development/API/differences_in_mastoapi_responses.md
+++ b/docs/docs/development/API/differences_in_mastoapi_responses.md
@ -1,6 +1,6 @@
 # Differences in Mastodon API responses from vanilla Mastodon

-A Akkoma instance can be identified by "<Mastodon version> (compatible; Akkoma <version>)" present in `version` field in response from `/api/v1/instance`
+A Akkoma instance can be identified by "<Mastodon version> (compatible; Pleroma <version>)" present in `version` field in response from `/api/v1/instance`

 ## Flake IDs

@ -8,32 +8,23 @@ Akkoma uses 128-bit ids as opposed to Mastodon's 64 bits. However, just like Mas

 ## Timelines

-In addition to Mastodon’s timelines, there is also a “bubble timeline” showing
-posts from the local instance and a set of closely related instances as chosen
-by the administrator. It is available under `/api/v1/timelines/bubble`.
-
 Adding the parameter `with_muted=true` to the timeline queries will also return activities by muted (not by blocked!) users.

 Adding the parameter `exclude_visibilities` to the timeline queries will exclude the statuses with the given visibilities. The parameter accepts an array of visibility types (`public`, `unlisted`, `private`, `direct`), e.g., `exclude_visibilities[]=direct&exclude_visibilities[]=private`.

-Adding the parameter `reply_visibility` to the public, bubble or home timelines queries will filter replies. Possible values: without parameter (default) shows all replies, `following` - replies directed to you or users you follow, `self` - replies directed to you.
+Adding the parameter `reply_visibility` to the public and home timelines queries will filter replies. Possible values: without parameter (default) shows all replies, `following` - replies directed to you or users you follow, `self` - replies directed to you.

 Adding the parameter `instance=lain.com` to the public timeline will show only statuses originating from `lain.com` (or any remote instance).

-All but the direct timeline accept these parameters:
+Home, public, hashtag & list timelines accept these parameters:

 - `only_media`: show only statuses with media attached
- `remote`: show only remote statuses
-
-Home, public, hashtag & list timelines further accept:
-
 - `local`: show only local statuses
-
+- `remote`: show only remote statuses

 ## Statuses

 - `visibility`: has additional possible values `list` and `local` (for local-only statuses)
- `emoji_reactions`: additional field since Akkoma 3.2.0; identical to `pleroma/emoji_reactions`

 Has these additional fields under the `pleroma` object:

@ -45,9 +36,7 @@ Has these additional fields under the `pleroma` object:
 - `spoiler_text`: a map consisting of alternate representations of the `spoiler_text` property with the key being its mimetype. Currently, the only alternate representation supported is `text/plain`
 - `expires_at`: a datetime (iso8601) that states when the post will expire (be deleted automatically), or empty if the post won't expire
 - `thread_muted`: true if the thread the post belongs to is muted
- `emoji_reactions`: A list with emoji / reaction maps. The format is `{name: "☕", count: 2, me: true, account_ids: ["UserID1", "UserID2"]}`.
-  The `account_ids` property was added in Akkoma 3.2.0.
-  Further info about all reacting users at once, can be found using the `/statuses/:id/reactions` endpoint.
+- `emoji_reactions`: A list with emoji / reaction maps. The format is `{name: "☕", count: 1, me: true}`. Contains no information about the reacting users, for that use the `/statuses/:id/reactions` endpoint.
 - `parent_visible`: If the parent of this post is visible to the user or not.
 - `pinned_at`: a datetime (iso8601) when status was pinned, `null` otherwise.

@ -121,12 +110,6 @@ Has these additional fields under the `pleroma` object:
 - `notification_settings`: object, can be absent. See `/api/v1/pleroma/notification_settings` for the parameters/keys returned.
 - `favicon`: nullable URL string, Favicon image of the user's instance

-Has these additional fields under the `akkoma` object:
-
- `instance`: nullable object with metadata about the user’s instance
- `status_ttl_days`: nullable int, default time after which statuses are deleted
- `permit_followback`: boolean, whether follows from followed accounts are auto-approved
-
 ### Source

 Has these additional fields under the `pleroma` object:
@ -231,11 +214,6 @@ Returns: array of Status.

 The maximum number of statuses is limited to 100 per request.

-## PUT `/api/v1/statuses/:id/emoji_reactions/:emoji`
-
-This endpoint is an extension of the Fedibird Mastodon fork.
-It behaves identical to PUT `/api/v1/pleroma/statuses/:id/reactions/:emoji`.
-
 ## PATCH `/api/v1/accounts/update_credentials`

 Additional parameters can be added to the JSON body/Form data:
--- a/docs/docs/development/API/prometheus.md
+++ b/docs/docs/development/API/prometheus.md
@ -5,16 +5,27 @@ Akkoma includes support for exporting metrics via the [prometheus_ex](https://gi
 Config example:

 ```
-config :pleroma, :instance,
-  export_prometheus_metrics: true
+config :prometheus, Pleroma.Web.Endpoint.MetricsExporter,
+  enabled: true,
+  auth: {:basic, "myusername", "mypassword"},
+  ip_whitelist: ["127.0.0.1"],
+  path: "/api/pleroma/app_metrics",
+  format: :text
 ```

-## `/api/v1/akkoma/metrics`
+* `enabled` (Akkoma extension) enables the endpoint
+* `ip_whitelist` (Akkoma extension) could be used to restrict access only to specified IPs
+* `auth` sets the authentication (`false` for no auth; configurable to HTTP Basic Auth, see [prometheus-plugs](https://github.com/deadtrickster/prometheus-plugs#exporting) documentation)
+* `format` sets the output format (`:text` or `:protobuf`)
+* `path` sets the path to app metrics page 
+
+
+## `/api/pleroma/app_metrics`

 ### Exports Prometheus application metrics

 * Method: `GET`
-* Authentication: required
+* Authentication: not required by default (see configuration options above)
 * Params: none
 * Response: text

@ -26,7 +37,7 @@ The following is a config example to use with [Grafana](https://grafana.com)

 ```
  - job_name: 'beam'
-    metrics_path: /api/v1/akkoma/metrics
+    metrics_path: /api/pleroma/app_metrics
    scheme: https
    static_configs:
    - targets: ['otp.akkoma.dev']
--- a/docs/docs/development/ap_extensions.md
+++ b/docs/docs/development/ap_extensions.md
@ -4,6 +4,7 @@
 The following endpoints are additionally present into our actors.

 - `oauthRegistrationEndpoint` (`http://litepub.social/ns#oauthRegistrationEndpoint`)
+- `uploadMedia` (`https://www.w3.org/ns/activitystreams#uploadMedia`)

 ### oauthRegistrationEndpoint

@ -11,279 +12,6 @@ Points to MastodonAPI `/api/v1/apps` for now.

 See <https://docs.joinmastodon.org/methods/apps/>

-## Emoji reactions
-
-Emoji reactions are implemented as a new activity type `EmojiReact`.
-A single user is allowed to react multiple times with different emoji to the
-same post. However, they may only react at most once with the same emoji.
-Repeated reaction from the same user with the same emoji are to be ignored.
-Emoji reactions are also distinct from `Like` activities and a user may both
-`Like` and react to a post.
-
-!!! note
-    Misskey also supports emoji reactions, but the implementations differs.
-    It equates likes and reactions and only allows a single reaction per post.
-
-The emoji is placed in the `content` field of the activity
-and the `object` property points to the note reacting to.
-
-Emoji can either be any Unicode emoji sequence or a custom emoji.
-The latter must place their shortcode, including enclosing colons,
-into `content` and put the emoji object inside the `tag` property.
-The `tag` property MAY be omitted for Unicode emoji.
-
-An example reaction with a Unicode emoji:
-```json
-{
-  "@context": [
-    "https://www.w3.org/ns/activitystreams",
-    "https://example.org/schemas/litepub-0.1.jsonld",
-    {
-      "@language": "und"
-    }
-  ],
-  "type": "EmojiReact",
-  "id": "https://example.org/activities/23143872a0346141",
-  "actor": "https://example.org/users/akko",
-  "nickname": "akko",
-  "to": ["https://remote.example/users/diana", "https://example.org/users/akko/followers"],
-  "cc": ["https://www.w3.org/ns/activitystreams#Public"],
-  "content": "🧡",
-  "object": "https://remote.example/objects/9f0e93499d8314a9"
-}
-```
-
-An example reaction with a custom emoji:
-```json
-{
-  "@context": [
-    "https://www.w3.org/ns/activitystreams",
-    "https://example.org/schemas/litepub-0.1.jsonld",
-    {
-      "@language": "und"
-    }
-  ],
-  "type": "EmojiReact",
-  "id": "https://example.org/activities/d75586dec0541650",
-  "actor": "https://example.org/users/akko",
-  "nickname": "akko",
-  "to": ["https://remote.example/users/diana", "https://example.org/users/akko/followers"],
-  "cc": ["https://www.w3.org/ns/activitystreams#Public"],
-  "content": ":mouse:",
-  "object": "https://remote.example/objects/9f0e93499d8314a9",
-  "tag": [{
-    "type": "Emoji",
-    "id": null,
-    "name": "mouse",
-    "icon": {
-      "type": "Image",
-      "url": "https://example.org/emoji/mouse/mouse.png"
-    }
-  }]
-}
-```
-
-!!! note
-    Although an emoji reaction can only contain a single emoji,
-    for compatibility with older versions of Pleroma and Akkoma,
-    it is recommended to wrap the emoji object in a single-element array.
-
-When reacting with a remote custom emoji do not include the remote domain in `content`’s shortcode
-*(unlike in our REST API which needs the domain)*:
-```json
-{
-  "@context": [
-    "https://www.w3.org/ns/activitystreams",
-    "https://example.org/schemas/litepub-0.1.jsonld",
-    {
-      "@language": "und"
-    }
-  ],
-  "type": "EmojiReact",
-  "id": "https://example.org/activities/7993dcae98d8d5ec",
-  "actor": "https://example.org/users/akko",
-  "nickname": "akko",
-  "to": ["https://remote.example/users/diana", "https://example.org/users/akko/followers"],
-  "cc": ["https://www.w3.org/ns/activitystreams#Public"],
-  "content": ":hug:",
-  "object": "https://remote.example/objects/9f0e93499d8314a9",
-  "tag": [{
-    "type": "Emoji",
-    "id": "https://other.example/emojis/hug",
-    "name": "hug",
-    "icon": {
-      "type": "Image",
-      "url": "https://other.example/files/b71cea432b3fad67.webp"
-    }
-  }]
-}
-```
-
-Emoji reactions can be retracted using a standard `Undo` activity:
-```json
-{
-  "@context": [
-    "https://www.w3.org/ns/activitystreams",
-    "http://example.org/schemas/litepub-0.1.jsonld",
-    {
-      "@language": "und"
-    }
-  ],
-  "type": "Undo",
-  "id": "http://example.org/activities/4685792e-efb6-4309-b508-ae4f355dd695",
-  "actor": "https://example.org/users/akko",
-  "to": ["https://remote.example/users/diana", "https://example.org/users/akko/followers"],
-  "cc": ["https://www.w3.org/ns/activitystreams#Public"],
-  "object": "https://example.org/activities/23143872a0346141"
-}
-```
-
-## User profile backgrounds
-
-Akkoma federates user profile backgrounds the same way as Sharkey.
-
-An actors ActivityPub representation contains an additional
-`backgroundUrl` property containing an `Image` object. This property
-belongs to the `"sharkey": "https://joinsharkey.org/ns#"` namespace.
-
-## Quote Posts
-
-Akkoma allows referencing a single other note as a quote,
-which will be prominently displayed in the interface.
-
-The quoted post is referenced by its ActivityPub id in the `quoteUri` property.
-
-!!! note
-    Old Misskey only understood and modern Misskey still prefers
-    the `_misskey_quote` property for this. Similar some other older
-    software used `quoteUrl` or `quoteURL`.  
-    All current implementations with quote support understand `quoteUri`.
-
-Example:
-```json
-{
-  "@context": [
-    "https://www.w3.org/ns/activitystreams",
-    "https://example.org/schemas/litepub-0.1.jsonld",
-    {
-      "@language": "und"
-    }
-  ],
-  "type": "Note",
-  "id": "https://example.org/activities/85717e587f95d5c0",
-  "actor": "https://example.org/users/akko",
-  "to": ["https://remote.example/users/diana", "https://example.org/users/akko/followers"],
-  "cc": ["https://www.w3.org/ns/activitystreams#Public"],
-  "context": "https://example.org/contexts/1",
-  "content": "Look at that!",
-  "quoteUri": "http://remote.example/status/85717e587f95d5c0",
-  "contentMap": {
-    "en": "Look at that!"
-  },
-  "source": {
-    "content": "Look at that!",
-    "mediaType": "text/plain"
-  },
-  "published": "2024-04-06T23:40:28Z",
-  "updated": "2024-04-06T23:40:28Z",
-  "attachemnt": [],
-  "tag": []
-}
-```
-
-## Threads
-
-Akkoma assigns all posts of the same thread the same `context`. This is a
-standard ActivityPub property but its meaning is left vague. Akkoma will
-always treat posts with identical `context` as part of the same thread.
-
-`context` must not be assumed to hold any meaning or be dereferencable.
-
-Incoming posts without `context` will be assigned a new context.
-
-!!! note
-    Mastodon uses the non-standard `conversation` property for the same purpose
-    *(named after an older OStatus property)*. For incoming posts without
-    `context` but with `converstions` Akkoma will use the value from
-    `conversations` to fill in `context`.
-    For outgoing posts Akkoma will duplicate the context into `conversation`.
-
-## Post Source
-
-Unlike Mastodon, Akkoma supports drafting posts in multiple source formats
-besides plaintext, like Markdown or MFM. The original input is preserved
-in the standard ActivityPub `source` property *(not supported by Mastodon)*.
-Still, `content` will always be present and contain the prerendered HTML form.
-
-Supported `mediaType` include:
- `text/plain`
- `text/markdown`
- `text/bbcode`
- `text/x.misskeymarkdown`
-
-## Post Language
-
-!!! note
-    This is also supported in and compatible with Mastodon, but since
-    joinmastodon.org doesn’t document it yet it is included here.
-    [GoToSocial](https://docs.gotosocial.org/en/latest/federation/federating_with_gotosocial/#content-contentmap-and-language)
-    has a more refined version of this which can correctly deal with multiple language entries.
-
-A post can indicate its language by including a `contentMap` object
-which contains a sub key named after the language’s ISO 639-1 code
-and it’s content identical to the post’s `content` field.
-
-Currently Akkoma, just like Mastodon, only properly supports a single language entry,
-in case of multiple entries a random language will be picked.  
-Furthermore, Akkoma currently only reads the `content` field
-and never the value from `contentMap`.
-
-## Local post scope
-
-Post using this scope will never federate to other servers
-but for the sake of completeness it is listed here.
-
-In addition to the usual scopes *(public, unlisted, followers-only, direct)*
-Akkoma supports an “unlisted” post scope. Such posts will not federate to
-other instances and only be shown to logged-in users on the same instance.
-It is included into the local timeline.  
-This may be useful to discuss or announce instance-specific policies and topics.
-
-A post is addressed to the local scope by including `<base url of instance>/#Public`
-in its `to` field. E.g. if the instance is on `https://example.org` it would use
-`https://example.org/#Public`.
-
-An implementation creating a new post MUST NOT address both the local and
-general public scope `as:Public` at the same time. A post addressing the local
-scope MUST NOT be sent to other instances or be possible to fetch by other
-instances regardless of potential other listed addressees.
-
-When receiving a remote post addressing both the public scope and what appears
-to be a local-scope identifier, the post SHOULD be treated without assigning any
-special meaning to the potential local-scope identifier.
-
-!!! note
-    Misskey-derivatives have a similar concept of non-federated posts,
-    however those are also shown publicly on the local web interface
-    and are thus visible to non-members.
-
-## List post scope
-
-Messages originally addressed to a custom list will contain
-a `listMessage` field with an unresolvable pseudo ActivityPub id.
-
-# Deprecated and Removed Extensions
-
-The following extensions were used in the past but have been dropped.
-Documentation is retained here as a reference and since old objects might
-still contains related fields.
-
-## Actor endpoints
-
-The following endpoints used to be present:
-
- `uploadMedia` (`https://www.w3.org/ns/activitystreams#uploadMedia`)
-
 ### uploadMedia

 Inspired by <https://www.w3.org/wiki/SocialCG/ActivityPub/MediaUpload>, it is part of the ActivityStreams namespace because it used to be part of the ActivityPub specification and got removed from it.
@ -292,8 +20,9 @@ Content-Type: multipart/form-data

 Parameters:
 - (required) `file`: The file being uploaded
- (optional) `description`: A plain-text description of the media, for accessibility purposes.
+- (optionnal) `description`: A plain-text description of the media, for accessibility purposes.

 Response: HTTP 201 Created with the object into the body, no `Location` header provided as it doesn't have an `id`

-The object given in the response should then be inserted into an Object's `attachment` field.
+The object given in the reponse should then be inserted into an Object's `attachment` field.
+
--- a/docs/docs/development/index.md
+++ b/docs/docs/development/index.md
@ -1,48 +1 @@
-# Contributing to Akkoma
-
-You wish to add a new feature in Akkoma, but don't know how to proceed? This guide takes you through the various steps of the development and contribution process.
-
-If you're looking for stuff to implement or fix, check the [bug-tracker](https://akkoma.dev/AkkomaGang/akkoma/issues) or [forum](https://meta.akkoma.dev/c/requests/5).
-
-Come say hi to us in the [#akkoma-dev chat room](./../#irc)!
-
-## Akkoma Clients
-
-Akkoma is the back-end. Clients have their own repositories and often separate projects. You can check what clients work with Akkoma [on the clients page](../clients/). If you maintain a working client not listed yet, feel free to make a PR [to these docs](./#docs)!
-
-For resources on APIs and such, check the sidebar of this page.
-
-## Docs
-
-The docs are written in Markdown, including certain extensions, and can be found [in the docs folder of the Akkoma repo](https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/docs/). The content itself is stored in the `docs` subdirectory.
-
-## Technology
-
-Akkoma is written in [Elixir](https://elixir-lang.org/) and uses [Postgresql](https://www.postgresql.org/) for database. We use [Git](https://git-scm.com/) for collaboration and tracking code changes. Furthermore it can typically run on [Unix and Unix-like OS'es](https://en.wikipedia.org/wiki/Unix-like). For development, you should use an OS which [can run Akkoma](../installation/debian_based_en/).
-
-It's good to have at least some basic understanding of at least Git and Elixir. If this is completely new for you, there's some [videos explaining Git](https://git-scm.com/doc) and Codeberg has a nice article explaining the typical [pull requests Git flow](https://docs.codeberg.org/collaborating/pull-requests-and-git-flow/). For Elixir, you can follow Elixir's own [Getting Started guide](https://elixir-lang.org/getting-started/introduction.html).
-
-## Setting up a development environment
-
-The best way to start is getting the software to run from source so you can start poking on it. Check out the [guides for setting up an Akkoma instance for development](setting_up_akkoma_dev/#setting-up-a-akkoma-development-environment).
-
-## General overview
-### Modules
-
-Akkoma has several modules. There are modules for [uploading](https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/lib/pleroma/uploaders), [upload filters](https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/lib/pleroma/upload/filter), [translators](https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/lib/pleroma/akkoma/translators)... The most famous ones are without a doubt the [MRF policies](https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/lib/pleroma/web/activity_pub/mrf). Modules are often self contained and a good way to start with development because you don't have to think about much more than just the module itself. We even have an example on [writing your own MRF policy](/configuration/mrf/#writing-your-own-mrf-policy)!
-
-Another easy entry point is the [mix tasks](https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/lib/mix/tasks/pleroma). They too are often self contained and don't need you to go through much of the code.
-
-### Activity Streams/Activity Pub
-
-Akkoma uses Activity Streams for both federation, as well as internal representation. It may be interesting to at least go over the specifications of [Activity Pub](https://www.w3.org/TR/activitypub/), [Activity Streams 2.0](https://www.w3.org/TR/activitystreams-core/), and [Activity Streams Vocabulary](https://www.w3.org/TR/activitystreams-vocabulary/). Note that these are not enough to have a full grasp of how everything works, but should at least give you the basics to understand how messages are passed between and inside Akkoma instances.
-
-## Don't forget
-
-When you make changes, you're expected to create [a Pull Request](https://akkoma.dev/AkkomaGang/akkoma/pulls). You don't have to wait until you finish to create the PR, but please do prefix the title of the PR with "WIP: " for as long as you're still working on it. The sooner you create your PR, the sooner people know what you are working on and the sooner you can get feedback and, if needed, help. You can then simply keep working on it until you are finished.
-
-When doing changes, don't forget to add it to the relevant parts of the [CHANGELOG.md](https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/CHANGELOG.md).
-
-You're expected to write [tests](https://elixirschool.com/en/lessons/testing/basics). While code is generally stored in the `lib` directory, tests are stored in the `test` directory using a similar folder structure. Feel free to peak at other tests to see how they are done. Obviously tests are expected to pass and properly test the functionality you added. If you feel really confident, you could even try to [write a test first and then write the code needed to make it pass](https://en.wikipedia.org/wiki/Test-driven_development)!
-
-Code is formatted using the default formatter that comes with Elixir. You can format a file with e.g. `mix format /path/to/file.ex`. To check if everything is properly formatted, you can run `mix format --check-formatted`.
+This section contains notes and guidelines for developers.
--- a/docs/docs/development/nodeinfo_extensions.md
+++ b/docs/docs/development/nodeinfo_extensions.md
@ -1,141 +0,0 @@
-# Nodeinfo Extensions
-
-Akkoma currently implements version 2.0 and 2.1 of nodeinfo spec,
-but provides the following additional fields.
-
-## metadata
-
-The spec leaves the content of `metadata` up to implementations
-and indeed Akkoma adds many fields here apart from the commonly
-found `nodeName` and `nodeDescription` fields.
-
-### accountActivationRequired
-Whether or not users need to confirm their email before completing registration.
-*(boolean)*
-
-!!! note
-    Not to be confused with account approval, where each registration needs to
-    be manually approved by an admin. Account approval has no nodeinfo entry.
-
-### features
-
-Array of strings denoting supported server features. E.g. a server supporting
-quote posts should include a `"quote_posting"` entry here.
-
-A non-exhaustive list of possible features:
- `polls`
- `quote_posting`
- `editing`
- `bubble_timeline`
- `pleroma_emoji_reactions` *(Unicode emoji)*
- `custom_emoji_reactions`
- `akkoma_api`
- `akkoma:machine_translation`
- `mastodon_api`
- `pleroma_api`
-
-### federatedTimelineAvailable
-Whether or not the “federated timeline”, i.e. a timeline containing posts from
-the entire known network, is made available.
-*(boolean)*
-
-### federation
-This section is optional and can contain various custom keys describing federation policies.
-The following are required to be presented:
- `enabled` *(boolean)* whether the server federates at all
-
-A non-exhaustive list of optional keys:
- `exclusions` *(boolean)* whether some federation policies are withheld
- `mrf_simple` *(object)* describes how the Simple MRF policy is configured
-
-### fieldsLimits
-A JSON object documenting restriction for user account info fields.
-All properties are integers.
-
- `maxFields` maximum number of account info fields local users can create
- `maxRemoteFields` maximum number of account info fields remote users can have
-   before the user gets rejected or fields truncated
- `nameLength` maximum length of a field’s name
- `valueLength` maximum length of a field’s value
-
-### invitesEnabled
-Whether or not signing up via invite codes is possible.
-*(boolean)*
-
-### localBubbleInstances
-Array of domains (as strings) of other instances chosen
-by the admin which are shown in the bubble timeline.
-
-### mailerEnabled
-Whether or not the instance can send out emails.
-*(boolean)*
-
-### nodeDescription
-Human-friendly description of this instance
-*(string)*
-
-### nodeName
-Human-friendly name of this instance
-*(string)*
-
-### pollLimits
-JSON object containing limits for polls created by local users.
-All values are integers.
- `max_options` maximum number of poll options
- `max_option_chars` maximum characters per poll option
- `min_expiration` minimum time in seconds a poll must be open for
- `max_expiration` maximum time a poll is allowed to be open for
-
-### postFormats
-Array of strings containing media types for supported post source formats.
-A non-exhaustive list of possible values:
- `text/plain`
- `text/markdown`
- `text/bbcode`
- `text/x.misskeymarkdown`
-
-### private
-Whether or not unauthenticated API access is permitted.
-*(boolean)*
-
-### privilegedStaff
-Whether or not moderators are trusted to perform some
-additional tasks like e.g. issuing password reset emails.
-
-### publicTimelineVisibility
-JSON object containing boolean-valued keys reporting
-if a given timeline can be viewed without login.
- `local`
- `federated`
- `bubble`
-
-### restrictedNicknames
-Array of strings listing nicknames forbidden to be used during signup.
-
-### skipThreadContainment
-Whether broken threads are filtered out
-*(boolean)*
-
-### staffAccounts
-Array containing ActivityPub IDs of local accounts
-with some form of elevated privilege on the instance.
-
-### suggestions
-JSON object containing info on whether the interaction-based
-Mastodon `/api/v1/suggestions` feature is enabled and optionally
-additional implementation-defined fields with more details
-on e.g. how suggested users are selected.
-
-!!! note
-    This has no relation to the newer /api/v2/suggestions API
-    which also (or exclusively) contains staff-curated entries.
-
- `enabled` *(boolean)* whether or not user recommendations are enabled
-
-### uploadLimits
-JSON object documenting various upload-related size limits.
-All values are integers and in bytes.
- `avatar` maximum size of uploaded user avatars
- `banner` maximum size of uploaded user profile banners
- `background` maximum size of uploaded user profile backgrounds
- `general` maximum size for all other kinds of uploads
--- a/docs/docs/development/setting_up_akkoma_dev.md
+++ b/docs/docs/development/setting_up_akkoma_dev.md
@ -5,32 +5,17 @@ Akkoma requires some adjustments from the defaults for running the instance loca
 ## Installing

 1. Install Akkoma as explained in [the docs](../installation/debian_based_en.md), with some exceptions:
-    * No need to create a dedicated akkoma user, it's easier to just use your own user
    * You can use your own fork of the repository and add akkoma as a remote `git remote add akkoma 'https://akkoma.dev/AkkomaGang/akkoma.git'`
+    * You can skip systemd and nginx and all that stuff
+    * No need to create a dedicated akkoma user, it's easier to just use your own user
+    * For the DB you can still choose a dedicated user, the mix tasks set it up for you so it's no extra work for you
    * For domain you can use `localhost`
-    * For the DB you can still choose a dedicated user. The mix tasks sets it up, so it's no extra work for you
    * instead of creating a `prod.secret.exs`, create `dev.secret.exs`
    * No need to prefix with `MIX_ENV=prod`. We're using dev and that's the default MIX_ENV
-    * You can skip nginx and systemd
-    * For front-end, you'll probably want to install and use the develop branch instead of the stable branch. There's no guarantee that the stable branch of the FE will always work on the develop branch of the BE.
 2. Change the dev.secret.exs
-    * Change the FE settings to use the installed branch (see also [Frontend Management](/configuration/frontend_management/))
    * Change the scheme in `config :pleroma, Pleroma.Web.Endpoint` to http (see examples below)
    * If you want to change other settings, you can do that too
-3. You can now start the server with `mix phx.server`. Once it's build and started, you can access the instance on `http://<host>:<port>` (e.g.http://localhost:4000 ) and should be able to do everything locally you normally can.
-
-Example on how to install pleroma-fe and admin-fe using it's develop branch
-```sh
-mix pleroma.frontend install pleroma-fe --ref develop
-mix pleroma.frontend install admin-fe --ref develop
-```
-
-Example config to use the pleroma-fe and admin-fe installed from the develop branch
-```elixir
-config :pleroma, :frontends,
-  primary: %{"name" => "pleroma-fe", "ref" => "develop"},
-  admin: %{"name" => "admin-fe", "ref" => "develop"}
-```
+3. You can now start the server `mix phx.server`. Once it's build and started, you can access the instance on `http://<host>:<port>` (e.g.http://localhost:4000 ) and should be able to do everything locally you normaly can.

 Example config to change the scheme to http. Change the port if you want to run on another port.
 ```elixir
@ -109,4 +94,4 @@ Update Akkoma as explained in [the docs](../administration/updating.md). Just ma

 ## Working on multiple branches

-If you develop on a separate branch, it's possible you did migrations that aren't merged into another branch you're working on. In that case, it's probably best to set up multiple Akkoma instances each with their own database. If you finished with a branch and want to switch back to develop to start a new branch from there, you can drop the database and recreate the database (e.g. by using `config/setup_db.psql`). The commands to drop and recreate the database can be found in [the docs](../administration/backup.md).
+If you develop on a separate branch, it's possible you did migrations that aren't merged into another branch you're working on. If you have multiple things you're working on, it's probably best to set up multiple Akkoma instances each with their own database. If you finished with a branch and want to switch back to develop to start a new branch from there, you can drop the database and recreate the database (e.g. by using `config/setup_db.psql`). The commands to drop and recreate the database can be found in [the docs](../administration/backup.md).
--- a/docs/docs/css/fonts/Tiresias_Infofont.ttf
+++ b/docs/docs/css/fonts/Tiresias_Infofont.ttf
--- a/docs/docs/css/fonts/Tiresias_PCfont.ttf
+++ b/docs/docs/css/fonts/Tiresias_PCfont.ttf
--- a/docs/docs/images/akko_badday.png
+++ b/docs/docs/images/akko_badday.png
--- a/docs/docs/images/favicon.ico
+++ b/docs/docs/images/favicon.ico
--- a/docs/docs/images/favicon.png
+++ b/docs/docs/images/favicon.png
--- a/docs/docs/images/logo.png
+++ b/docs/docs/images/logo.png
--- a/docs/docs/index.md
+++ b/docs/docs/index.md
@ -3,7 +3,7 @@
 # Introduction to Akkoma
 ## What is Akkoma?
 Akkoma is a federated social networking platform, compatible with Mastodon and other ActivityPub implementations. It is free software licensed under the AGPLv3.
-It actually consists of two components: a backend, named simply Akkoma, and a user-facing frontend, named Akkoma-FE. It also includes the Mastodon frontend, if that's your thing.
+It actually consists of two components: a backend, named simply Akkoma, and a user-facing frontend, named Pleroma-FE. It also includes the Mastodon frontend, if that's your thing.
 It's part of what we call the fediverse, a federated network of instances which speak common protocols and can communicate with each other.
 One account on an instance is enough to talk to the entire fediverse!

@ -31,11 +31,11 @@ Installation instructions can be found in the installation section of these docs
 ## I got an account, now what?
 Great! Now you can explore the fediverse! Open the login page for your Akkoma instance (e.g. <https://otp.akkoma.dev>) and login with your username and password. (If you don't have an account yet, click on Register)

-### Akkoma-FE
-The default front-end used by Akkoma is Akkoma-FE. You can find more information on what it is and how to use it in the [Introduction to Akkoma-FE](https://docs-fe.akkoma.dev/stable/).
+### Pleroma-FE
+The default front-end used by Akkoma is Pleroma-FE. You can find more information on what it is and how to use it in the [Introduction to Pleroma-FE](https://docs-fe.akkoma.dev/stable/).

 ### Mastodon interface
-If the Akkoma-FE interface isn't your thing, or you're just trying something new but you want to keep using the familiar Mastodon interface, we got that too!
+If the Pleroma-FE interface isn't your thing, or you're just trying something new but you want to keep using the familiar Mastodon interface, we got that too!
 Just add a "/web" after your instance url (e.g. <https://otp.akkoma.dev/web>) and you'll end on the Mastodon web interface, but with a Akkoma backend! MAGIC!
 The Mastodon interface is from the Glitch-soc fork. For more information on the Mastodon interface you can check the [Mastodon](https://docs.joinmastodon.org/) and [Glitch-soc](https://glitch-soc.github.io/docs/) documentation.

--- a/docs/docs/installation/alpine_linux_en.md
+++ b/docs/docs/installation/alpine_linux_en.md
@ -84,12 +84,12 @@ doas adduser -S -s /bin/false -h /opt/akkoma -H -G akkoma akkoma

 **Note**: To execute a single command as the Akkoma system user, use `doas -u akkoma command`. You can also switch to a shell by using `doas -su akkoma`. If you don’t have and want `doas` on your system, you can use `su` as root user (UID 0) for a single command by using `su -l akkoma -s $SHELL -c 'command'` and `su -l akkoma -s $SHELL` for starting a shell.

-* Git clone the AkkomaBE repository from stable-branch and make the Akkoma user the owner of the directory:
+* Git clone the AkkomaBE repository and make the Akkoma user the owner of the directory:

 ```shell
 doas mkdir -p /opt/akkoma
 doas chown -R akkoma:akkoma /opt/akkoma
-doas -u akkoma git clone https://akkoma.dev/AkkomaGang/akkoma.git -b stable /opt/akkoma
+doas -u akkoma git clone https://akkoma.dev/AkkomaGang/akkoma.git /opt/akkoma
 ```

 * Change to the new directory:
@ -109,7 +109,7 @@ doas -u akkoma mix deps.get
  * This may take some time, because parts of akkoma get compiled first.
  * After that it will ask you a few questions about your instance and generates a configuration file in `config/generated_config.exs`.

-* Check the configuration and if all looks right, rename it, so Akkoma will load it (`prod.secret.exs` for productive instances):
+* Check the configuration and if all looks right, rename it, so Akkoma will load it (`prod.secret.exs` for productive instance, `dev.secret.exs` for development instances):

 ```shell
 doas -u akkoma mv config/{generated_config.exs,prod.secret.exs}
@ -145,13 +145,47 @@ If you want to open your newly installed instance to the world, you should run n
 doas apk add nginx
 ```

+* Setup your SSL cert, using your method of choice or certbot. If using certbot, first install it:
+
+```shell
+doas apk add certbot
+```
+
+and then set it up:
+
+```shell
+doas mkdir -p /var/lib/letsencrypt/
+doas certbot certonly --email <your@emailaddress> -d <yourdomain> --standalone
+```
+
+If that doesn’t work, make sure, that nginx is not already running. If it still doesn’t work, try setting up nginx first (change ssl “on” to “off” and try again).
+
 * Copy the example nginx configuration to the nginx folder

 ```shell
 doas cp /opt/akkoma/installation/nginx/akkoma.nginx /etc/nginx/conf.d/akkoma.conf
 ```

-* Before starting nginx edit the configuration and change it to your needs. You must change change `server_name`. You can use `nano` (install with `apk add nano` if missing).
+* Before starting nginx edit the configuration and change it to your needs. You must change change `server_name` and the paths to the certificates. You can use `nano` (install with `apk add nano` if missing).
+
+```
+server {
+    server_name    your.domain;
+    listen         80;
+    ...
+}
+
+server {
+    server_name your.domain;
+    listen 443 ssl http2;
+    ...
+    ssl_trusted_certificate   /etc/letsencrypt/live/your.domain/chain.pem;
+    ssl_certificate           /etc/letsencrypt/live/your.domain/fullchain.pem;
+    ssl_certificate_key       /etc/letsencrypt/live/your.domain/privkey.pem;
+    ...
+}
+```
+
 * Enable and start nginx:

 ```shell
@ -159,37 +193,10 @@ doas rc-update add nginx
 doas rc-service nginx start
 ```

-* Setup your SSL cert, using your method of choice or certbot. If using certbot, first install it:
+If you need to renew the certificate in the future, uncomment the relevant location block in the nginx config and run:

 ```shell
-doas apk add certbot certbot-nginx
-```
-
-and then set it up:
-
-```shell
-doas mkdir -p /var/lib/letsencrypt/
-doas certbot --email <your@emailaddress> -d <yourdomain> -d <media_domain> --nginx
-```
-
-If that doesn't work the first time, add `--dry-run` to further attempts to avoid being ratelimited as you identify the issue, and do not remove it until the dry run succeeds. A common source of problems are nginx config syntax errors; this can be checked for by running `nginx -t`.
-
-To automatically renew, set up a cron job like so:
-
-```shell
-# Enable the crond service
-doas rc-update add crond
-doas rc-service crond start
-
-# Test that renewals work
-doas certbot renew --cert-name yourinstance.tld --nginx --dry-run
-
-# Add the renewal task to cron
-echo '#!/bin/sh
-certbot renew --cert-name yourinstance.tld --nginx
-' | doas tee /etc/periodic/daily/renew-akkoma-cert
-doas chmod +x /etc/periodic/daily/renew-akkoma-cert
-
+doas certbot certonly --email <your@emailaddress> -d <yourdomain> --webroot -w /var/lib/letsencrypt/
 ```

 #### OpenRC service
--- a/docs/docs/installation/arch_linux_en.md
+++ b/docs/docs/installation/arch_linux_en.md
@ -75,12 +75,12 @@ sudo useradd -r -s /bin/false -m -d /var/lib/akkoma -U akkoma

 **Note**: To execute a single command as the Akkoma system user, use `sudo -Hu akkoma command`. You can also switch to a shell by using `sudo -Hu akkoma $SHELL`. If you don’t have and want `sudo` on your system, you can use `su` as root user (UID 0) for a single command by using `su -l akkoma -s $SHELL -c 'command'` and `su -l akkoma -s $SHELL` for starting a shell.

-* Git clone the AkkomaBE repository from stable-branch and make the Akkoma user the owner of the directory:
+* Git clone the AkkomaBE repository and make the Akkoma user the owner of the directory:

 ```shell
 sudo mkdir -p /opt/akkoma
 sudo chown -R akkoma:akkoma /opt/akkoma
-sudo -Hu akkoma git clone https://akkoma.dev/AkkomaGang/akkoma.git -b stable /opt/akkoma
+sudo -Hu akkoma git clone https://akkoma.dev/AkkomaGang/akkoma.git /opt/akkoma
 ```

 * Change to the new directory:
@ -100,7 +100,7 @@ sudo -Hu akkoma mix deps.get
  * This may take some time, because parts of akkoma get compiled first.
  * After that it will ask you a few questions about your instance and generates a configuration file in `config/generated_config.exs`.

-* Check the configuration and if all looks right, rename it, so Akkoma will load it (`prod.secret.exs` for productive instances):
+* Check the configuration and if all looks right, rename it, so Akkoma will load it (`prod.secret.exs` for productive instance, `dev.secret.exs` for development instances):

 ```shell
 sudo -Hu akkoma mv config/{generated_config.exs,prod.secret.exs}
@ -136,17 +136,16 @@ If you want to open your newly installed instance to the world, you should run n
 sudo pacman -S nginx
 ```

-* Copy the example nginx configuration:
+* Create directories for available and enabled sites:

 ```shell
-sudo cp /opt/akkoma/installation/nginx/akkoma.nginx /etc/nginx/conf.d/akkoma.conf
+sudo mkdir -p /etc/nginx/sites-{available,enabled}
 ```

-* Before starting nginx edit the configuration and change it to your needs (e.g. change servername, change cert paths)
-* Enable and start nginx:
+* Append the following line at the end of the `http` block in `/etc/nginx/nginx.conf`:

-```shell
-sudo systemctl enable --now nginx.service
+```Nginx
+include sites-enabled/*;
 ```

 * Setup your SSL cert, using your method of choice or certbot. If using certbot, first install it:
@ -159,18 +158,32 @@ and then set it up:

 ```shell
 sudo mkdir -p /var/lib/letsencrypt/
-sudo certbot --email <your@emailaddress> -d <yourdomain> -d <media_domain> --nginx
+sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --standalone
 ```

-If that doesn't work the first time, add `--dry-run` to further attempts to avoid being ratelimited as you identify the issue, and do not remove it until the dry run succeeds. A common source of problems are nginx config syntax errors; this can be checked for by running `nginx -t`.
+If that doesn’t work, make sure, that nginx is not already running. If it still doesn’t work, try setting up nginx first (change ssl “on” to “off” and try again).

-To make sure renewals work, enable the appropriate systemd timer:
+---
+
+* Copy the example nginx configuration and activate it:

 ```shell
-sudo systemctl enable --now certbot-renew.timer
+sudo cp /opt/akkoma/installation/nginx/akkoma.nginx /etc/nginx/sites-available/akkoma.nginx
+sudo ln -s /etc/nginx/sites-available/akkoma.nginx /etc/nginx/sites-enabled/akkoma.nginx
 ```

-Certificate renewal should be handled automatically by Certbot from now on.
+* Before starting nginx edit the configuration and change it to your needs (e.g. change servername, change cert paths)
+* Enable and start nginx:
+
+```shell
+sudo systemctl enable --now nginx.service
+```
+
+If you need to renew the certificate in the future, uncomment the relevant location block in the nginx config and run:
+
+```shell
+sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --webroot -w /var/lib/letsencrypt/
+```

 #### Other webserver/proxies

--- a/docs/docs/installation/debian_based_en.md
+++ b/docs/docs/installation/debian_based_en.md
@ -4,7 +4,7 @@

 ## Installation

-This guide will assume you are on Debian 12 (“bookworm”) or later. This guide should also work with Ubuntu 22.04 (“Jammy Jellyfish”) and later. It also assumes that you have administrative rights, either as root or a user with [sudo permissions](https://www.digitalocean.com/community/tutorials/how-to-add-delete-and-grant-sudo-privileges-to-users-on-a-debian-vps). If you want to run this guide with root, ignore the `sudo` at the beginning of the lines, unless it calls a user like `sudo -Hu akkoma`; in this case, use `su <username> -s $SHELL -c 'command'` instead.
+This guide will assume you are on Debian 11 (“bullseye”) or later. This guide should also work with Ubuntu 18.04 (“Bionic Beaver”) and later. It also assumes that you have administrative rights, either as root or a user with [sudo permissions](https://www.digitalocean.com/community/tutorials/how-to-add-delete-and-grant-sudo-privileges-to-users-on-a-debian-vps). If you want to run this guide with root, ignore the `sudo` at the beginning of the lines, unless it calls a user like `sudo -Hu akkoma`; in this case, use `su <username> -s $SHELL -c 'command'` instead.

 {! installation/generic_dependencies.include !}

@ -23,67 +23,15 @@ sudo apt full-upgrade
 sudo apt install git build-essential postgresql postgresql-contrib cmake libmagic-dev
 ```

-### Create the akkoma user
-
-* Add a new system user for the Akkoma service:
-
-```shell
-sudo useradd -r -s /bin/false -m -d /var/lib/akkoma -U akkoma
-```
-
-**Note**: To execute a single command as the Akkoma system user, use `sudo -Hu akkoma command`. You can also switch to a shell by using `sudo -Hu akkoma $SHELL`. If you don’t have and want `sudo` on your system, you can use `su` as root user (UID 0) for a single command by using `su -l akkoma -s $SHELL -c 'command'` and `su -l akkoma -s $SHELL` for starting a shell.
-
 ### Install Elixir and Erlang

-If your distribution packages a recent enough version of Elixir, you can install it directly from the distro repositories and skip to the next section of the guide:
+* Install Elixir and Erlang (you might need to use backports or [asdf](https://github.com/asdf-vm/asdf) on old systems):

 ```shell
+sudo apt update
 sudo apt install elixir erlang-dev erlang-nox
 ```

-Otherwise use [asdf](https://github.com/asdf-vm/asdf) to install the latest versions of Elixir and Erlang.
-
-First, install some dependencies needed to build Elixir and Erlang:
-```shell
-sudo apt install curl unzip build-essential autoconf m4 libncurses5-dev libssh-dev unixodbc-dev xsltproc libxml2-utils libncurses-dev
-```
-
-Then login to the `akkoma` user and install asdf:
-```shell
-git clone https://github.com/asdf-vm/asdf.git ~/.asdf --branch v0.11.3
-```
-
-Add the following lines to `~/.bashrc`:
-```shell
-. "$HOME/.asdf/asdf.sh"
-# asdf completions
-. "$HOME/.asdf/completions/asdf.bash"
-```
-
-Restart the shell:
-```shell
-exec $SHELL
-```
-
-Next install Erlang:
-```shell
-asdf plugin add erlang https://github.com/asdf-vm/asdf-erlang.git
-export KERL_CONFIGURE_OPTIONS="--disable-debug --without-javac"
-asdf install erlang 25.3.2.5
-asdf global erlang 25.3.2.5
-```
-
-Now install Elixir:
-```shell
-asdf plugin-add elixir https://github.com/asdf-vm/asdf-elixir.git
-asdf install elixir 1.15.4-otp-25
-asdf global elixir 1.15.4-otp-25
-```
-
-Confirm that Elixir is installed correctly by checking the version:
-```shell
-elixir --version
-```

 ### Optional packages: [`docs/installation/optional/media_graphics_packages.md`](../installation/optional/media_graphics_packages.md)

@ -93,12 +41,20 @@ sudo apt install imagemagick ffmpeg libimage-exiftool-perl

 ### Install AkkomaBE

-* Log into the `akkoma` user and clone the AkkomaBE repository from the stable branch and make the Akkoma user the owner of the directory:
+* Add a new system user for the Akkoma service:
+
+```shell
+sudo useradd -r -s /bin/false -m -d /var/lib/akkoma -U akkoma
+```
+
+**Note**: To execute a single command as the Akkoma system user, use `sudo -Hu akkoma command`. You can also switch to a shell by using `sudo -Hu akkoma $SHELL`. If you don’t have and want `sudo` on your system, you can use `su` as root user (UID 0) for a single command by using `su -l akkoma -s $SHELL -c 'command'` and `su -l akkoma -s $SHELL` for starting a shell.
+
+* Git clone the AkkomaBE repository and make the Akkoma user the owner of the directory:

 ```shell
 sudo mkdir -p /opt/akkoma
 sudo chown -R akkoma:akkoma /opt/akkoma
-sudo -Hu akkoma git clone https://akkoma.dev/AkkomaGang/akkoma.git -b stable /opt/akkoma
+sudo -Hu akkoma git clone https://akkoma.dev/AkkomaGang/akkoma.git /opt/akkoma
 ```

 * Change to the new directory:
@ -118,7 +74,7 @@ sudo -Hu akkoma mix deps.get
  * This may take some time, because parts of akkoma get compiled first.
  * After that it will ask you a few questions about your instance and generates a configuration file in `config/generated_config.exs`.

-* Check the configuration and if all looks right, rename it, so Akkoma will load it (`prod.secret.exs` for productive instances):
+* Check the configuration and if all looks right, rename it, so Akkoma will load it (`prod.secret.exs` for productive instance, `dev.secret.exs` for development instances):

 ```shell
 sudo -Hu akkoma mv config/{generated_config.exs,prod.secret.exs}
@ -155,6 +111,23 @@ If you want to open your newly installed instance to the world, you should run n
 sudo apt install nginx
 ```

+* Setup your SSL cert, using your method of choice or certbot. If using certbot, first install it:
+
+```shell
+sudo apt install certbot
+```
+
+and then set it up:
+
+```shell
+sudo mkdir -p /var/lib/letsencrypt/
+sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --standalone
+```
+
+If that doesn’t work, make sure, that nginx is not already running. If it still doesn’t work, try setting up nginx first (change ssl “on” to “off” and try again).
+
+---
+
 * Copy the example nginx configuration and activate it:

 ```shell
@ -169,23 +142,12 @@ sudo ln -s /etc/nginx/sites-available/akkoma.nginx /etc/nginx/sites-enabled/akko
 sudo systemctl enable --now nginx.service
 ```

-* Setup your SSL cert, using your method of choice or certbot. If using certbot, first install it:
+If you need to renew the certificate in the future, uncomment the relevant location block in the nginx config and run:

 ```shell
-sudo apt install certbot python3-certbot-nginx
+sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --webroot -w /var/lib/letsencrypt/
 ```

-and then set it up:
-
-```shell
-sudo mkdir -p /var/lib/letsencrypt/
-sudo certbot --email <your@emailaddress> -d <yourdomain> -d <media_domain> --nginx
-```
-
-If that doesn't work the first time, add `--dry-run` to further attempts to avoid being ratelimited as you identify the issue, and do not remove it until the dry run succeeds. A common source of problems are nginx config syntax errors; this can be checked for by running `nginx -t`.
-
-Certificate renewal should be handled automatically by Certbot from now on.
-
 #### Other webserver/proxies

 You can find example configurations for them in `/opt/akkoma/installation/`.
--- a/docs/docs/installation/docker_en.md
+++ b/docs/docs/installation/docker_en.md
@ -10,7 +10,7 @@ If you want to migrate from or OTP to docker, check out [the migration guide](./

 ### Prepare the system

-* Install docker and docker compose
+* Install docker and docker-compose
  * [Docker](https://docs.docker.com/engine/install/) 
  * [Docker-compose](https://docs.docker.com/compose/install/)
  * This will usually just be a repository installation and a package manager invocation.
@ -26,7 +26,7 @@ echo "DOCKER_USER=$(id -u):$(id -g)" >> .env
 ```

 This probably won't need to be changed, it's only there to set basic environment
-variables for the docker compose file.
+variables for the docker-compose file.

 ### Building the container

@ -51,8 +51,7 @@ mkdir pgdata
 ```

 This will ask you a few questions - the defaults are fine for most things,
-the database hostname is `db`, the database password is `akkoma`
-(not auto generated), and you will want to set the ip to `0.0.0.0`.
+the database hostname is `db`, and you will want to set the ip to `0.0.0.0`.

 Now we'll want to copy over the config it just created

@ -65,9 +64,9 @@ cp config/generated_config.exs config/prod.secret.exs
 We need to run a few commands on the database container, this isn't too bad

 ```bash
-docker compose run --rm --user akkoma -d db 
+docker-compose run --rm --user akkoma -d db 
 # Note down the name it gives here, it will be something like akkoma_db_run
-docker compose run --rm akkoma psql -h db -U akkoma -f config/setup_db.psql
+docker-compose run --rm akkoma psql -h db -U akkoma -f config/setup_db.psql
 docker stop akkoma_db_run # Replace with the name you noted down
 ```

@ -84,17 +83,17 @@ We're going to run it in the foreground on the first run, just to make sure
 everything start up.

 ```bash
-docker compose up
+docker-compose up
 ```

 If everything went well, you should be able to access your instance at http://localhost:4000

-You can `ctrl-c` out of the docker compose now to shutdown the server.
+You can `ctrl-c` out of the docker-compose now to shutdown the server.

 ### Running in the background

 ```bash
-docker compose up -d
+docker-compose up -d
 ```

 ### Create your first user
@ -125,27 +124,8 @@ cp docker-resources/Caddyfile.example docker-resources/Caddyfile

 Then edit the TLD in your caddyfile to the domain you're serving on.

-Copy the commented out `caddy` section in `docker-compose.yml` into a new file called `docker-compose.override.yml` like so:
-```yaml
-version: "3.7"
-
-services:
-  proxy:
-    image: caddy:2-alpine
-    restart: unless-stopped
-    links:
-      - akkoma
-    ports: [
-       "443:443",
-       "80:80"
-    ]
-    volumes:
-      - ./docker-resources/Caddyfile:/etc/caddy/Caddyfile
-      - ./caddy-data:/data
-      - ./caddy-config:/config
-```
-
-then run `docker compose up -d` again.
+Uncomment the `caddy` section in the docker-compose file,
+then run `docker-compose up -d` again.

 #### Running a reverse proxy on the host

@ -171,15 +151,9 @@ git pull
 ./docker-resources/manage.sh mix deps.get
 ./docker-resources/manage.sh mix compile
 ./docker-resources/manage.sh mix ecto.migrate
-docker compose restart akkoma db
+docker-compose restart akkoma db
 ```

-### Modifying the Docker services
-If you want to modify the services defined in the docker compose file, you can
-create a new file called `docker-compose.override.yml`. There you can add any
-overrides or additional services without worrying about git conflicts when a
-new release comes out.
-
 #### Further reading

 {! installation/further_reading.include !}
--- a/docs/docs/installation/fedora_based_en.md
+++ b/docs/docs/installation/fedora_based_en.md
@ -30,10 +30,11 @@ sudo dnf install git gcc g++ make cmake file-devel postgresql-server postgresql-

 * Enable and initialize Postgres:
 ```shell
+sudo systemctl enable postgresql.service
 sudo postgresql-setup --initdb --unit postgresql
 # Allow password auth for postgres
 sudo sed -E -i 's|(host +all +all +127.0.0.1/32 +)ident|\1md5|' /var/lib/pgsql/data/pg_hba.conf
-sudo systemctl enable --now postgresql.service
+sudo systemctl start postgresql.service
 ```

 ### Install Elixir and Erlang
@ -58,7 +59,7 @@ sudo dnf install ffmpeg
 * Install ImageMagick and ExifTool for image manipulation:

 ```shell
-sudo dnf install ImageMagick perl-Image-ExifTool
+sudo dnf install Imagemagick perl-Image-ExifTool
 ```


@ -73,12 +74,12 @@ sudo useradd -r -s /bin/false -m -d /var/lib/akkoma -U akkoma

 **Note**: To execute a single command as the Akkoma system user, use `sudo -Hu akkoma command`. You can also switch to a shell by using `sudo -Hu akkoma $SHELL`. If you don’t have and want `sudo` on your system, you can use `su` as root user (UID 0) for a single command by using `su -l akkoma -s $SHELL -c 'command'` and `su -l akkoma -s $SHELL` for starting a shell.

-* Git clone the AkkomaBE repository from stable-branch and make the Akkoma user the owner of the directory:
+* Git clone the AkkomaBE repository and make the Akkoma user the owner of the directory:

 ```shell
 sudo mkdir -p /opt/akkoma
 sudo chown -R akkoma:akkoma /opt/akkoma
-sudo -Hu akkoma git clone https://akkoma.dev/AkkomaGang/akkoma.git -b stable /opt/akkoma
+sudo -Hu akkoma git clone https://akkoma.dev/AkkomaGang/akkoma.git /opt/akkoma
 ```

 * Change to the new directory:
@ -98,7 +99,7 @@ sudo -Hu akkoma mix deps.get
  * This may take some time, because parts of akkoma get compiled first.
  * After that it will ask you a few questions about your instance and generates a configuration file in `config/generated_config.exs`.

-* Check the configuration and if all looks right, rename it, so Akkoma will load it (`prod.secret.exs` for productive instances):
+* Check the configuration and if all looks right, rename it, so Akkoma will load it (`prod.secret.exs` for productive instance, `dev.secret.exs` for development instances):

 ```shell
 sudo -Hu akkoma mv config/{generated_config.exs,prod.secret.exs}
@ -135,6 +136,23 @@ If you want to open your newly installed instance to the world, you should run n
 sudo dnf install nginx
 ```

+* Setup your SSL cert, using your method of choice or certbot. If using certbot, first install it:
+
+```shell
+sudo dnf install certbot
+```
+
+and then set it up:
+
+```shell
+sudo mkdir -p /var/lib/letsencrypt/
+sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --standalone
+```
+
+If that doesn’t work, make sure, that nginx is not already running. If it still doesn’t work, try setting up nginx first (change ssl “on” to “off” and try again).
+
+---
+
 * Copy the example nginx configuration and activate it:

 ```shell
@ -148,23 +166,12 @@ sudo cp /opt/akkoma/installation/nginx/akkoma.nginx /etc/nginx/conf.d/akkoma.con
 sudo systemctl enable --now nginx.service
 ```

-* Setup your SSL cert, using your method of choice or certbot. If using certbot, first install it:
+If you need to renew the certificate in the future, uncomment the relevant location block in the nginx config and run:

 ```shell
-sudo dnf install certbot python3-certbot-nginx
+sudo certbot certonly --email <your@emailaddress> -d <yourdomain> --webroot -w /var/lib/letsencrypt/
 ```

-and then set it up:
-
-```shell
-sudo certbot --email <your@emailaddress> -d <yourdomain> -d <media_domain> --nginx
-```
-
-If that doesn't work the first time, add `--dry-run` to further attempts to avoid being ratelimited as you identify the issue, and do not remove it until the dry run succeeds. A common source of problems are nginx config syntax errors; this can be checked for by running `nginx -t`.
-
-Certificate renewal should be handled automatically by Certbot from now on.
-
-
 #### Other webserver/proxies

 You can find example configurations for them in `/opt/akkoma/installation/`.
--- a/docs/docs/installation/frontends.include
+++ b/docs/docs/installation/frontends.include
@ -6,9 +6,7 @@ probably install frontends.
 These are no longer bundled with the distribution and need an extra
 command to install.

-You **must** run frontend management tasks as the akkoma user,
-the same way you downloaded the build or cloned the git repo before.
-But otherwise, for most installations, the following will suffice:
+For most installations, the following will suffice:

 === "OTP" 
    ```sh
@ -30,3 +28,4 @@ But otherwise, for most installations, the following will suffice:
    ```

 For more customised installations, refer to [Frontend Management](../../configuration/frontend_management)
+
--- a/docs/docs/installation/generic_dependencies.include
+++ b/docs/docs/installation/generic_dependencies.include
@ -1,8 +1,8 @@
 ## Required dependencies

-* PostgreSQL 12+
-* Elixir 1.14+ (currently tested up to 1.16)
-* Erlang OTP 25+ (currently tested up to OTP26)
+* PostgreSQL 9.6+
+* Elixir 1.12+ (1.13+ recommended)
+* Erlang OTP 22.2+
 * git
 * file / libmagic
 * gcc (clang might also work)
--- a/docs/docs/installation/gentoo_en.md
+++ b/docs/docs/installation/gentoo_en.md
@ -18,12 +18,6 @@ dev-db/postgresql uuid

 You could opt to add `USE="uuid"` to `/etc/portage/make.conf` if you'd rather set this as a global USE flags, but this flags does unrelated things in other packages, so keep that in mind if you elect to do so.

-If you are planning to use `nginx`, as this guide suggests, you should also add the following flag to the same file.
-
-```text
-www-servers/nginx NGINX_MODULES_HTTP: slice
-```
-
 Double check your compiler flags in `/etc/portage/make.conf`. If you require any special compilation flags or would like to set up remote builds, now is the time to do so. Be sure that your CFLAGS and MAKEOPTS make sense for the platform you are using. It is not recommended to use above `-O2` or risky optimization flags for a production server.

 ### Installing a cron daemon
@ -201,6 +195,25 @@ Assuming you want to open your newly installed federated social network to, well
 include sites-enabled/*;
 ```

+* Setup your SSL cert, using your method of choice or certbot. If using certbot, install it if you haven't already:
+
+```shell
+ # emerge --ask app-crypt/certbot app-crypt/certbot-nginx
+```
+
+and then set it up:
+
+```shell
+ # mkdir -p /var/lib/letsencrypt/
+ # certbot certonly --email <your@emailaddress> -d <yourdomain> --standalone
+```
+
+If that doesn't work the first time, add `--dry-run` to further attempts to avoid being ratelimited as you identify the issue, and do not remove it until the dry run succeeds. If that doesn’t work, make sure, that nginx is not already running. If it still doesn’t work, try setting up nginx first (change ssl “on” to “off” and try again). Often the answer to issues with certbot is to use the `--nginx` flag once you have nginx up and running.
+
+If you are using any additional subdomains, such as for a media proxy, you can re-run the same command with the subdomain in question. When it comes time to renew later, you will not need to run multiple times for each domain, one renew will handle it.
+
+---
+
 * Copy the example nginx configuration and activate it:

 ```shell
@ -218,24 +231,9 @@ Pay special attention to the line that begins with `ssl_ecdh_curve`. It is stong

 ```shell
 # rc-update add nginx default
- # rc-service nginx start
+ # /etc/init.d/nginx start
 ```

-* Setup your SSL cert, using your method of choice or certbot. If using certbot, install it if you haven't already:
-
-```shell
- # emerge --ask app-crypt/certbot app-crypt/certbot-nginx
-```
-
-and then set it up:
-
-```shell
- # mkdir -p /var/lib/letsencrypt/
- # certbot --email <your@emailaddress> -d <yourdomain> -d <media_domain> --nginx
-```
-
-If that doesn't work the first time, add `--dry-run` to further attempts to avoid being ratelimited as you identify the issue, and do not remove it until the dry run succeeds. A common source of problems are nginx config syntax errors; this can be checked for by running `nginx -t`.
-
 If you are using certbot, it is HIGHLY recommend you set up a cron job that renews your certificate, and that you install the suggested `certbot-nginx` plugin. If you don't do these things, you only have yourself to blame when your instance breaks suddenly because you forgot about it.

 First, ensure that the command you will be installing into your crontab works.
@ -274,9 +272,7 @@ Even if you are using S3, Akkoma needs someplace to store media posted on your i
 # cp /home/akkoma/akkoma/installation/init.d/akkoma /etc/init.d/
 ```

-* Change the `/opt/akkoma` path in this file to `/home/akkoma/akkoma`
-
-* Be sure to take a look at this service file and make sure that all other paths fit your installation
+* Be sure to take a look at this service file and make sure that all paths fit your installation

 * Enable and start `akkoma`:

--- a/docs/docs/installation/migrating_to_akkoma.md
+++ b/docs/docs/installation/migrating_to_akkoma.md
@ -21,33 +21,6 @@ fork of Akkoma - luckily this isn't very hard.
 You'll need to update the backend, then possibly the frontend, depending
 on your setup.

-## Backup diverging features
-
-As time goes on Akkoma and Pleroma added or removed different features
-and reorganised the database in a different way. If you want to be able to
-migrate back to Pleroma without losing any affected data, you’ll want to
-make a backup before starting the migration.  
-If you're not interested in migrating back, skip this section
-*(although it might be a good idea to temporarily keep a full DB backup
-just in case something unexpected happens during migration)*
-
-As of 2024-02 you will want to keep a backup of:
-
- the entire `chats` and `chat_message_references` tables
-
-The following columns are not deleted by a migration to Akkoma, but a migration
-back to Pleroma or future Akkoma upgrades might affect them, so perhaps back them up as well:
-
- the `birthday` of users and their `show_birthday` setting
- the `expires_at` key of in the `user_relationships` table
-    *(used by temporary mutes)*
-
-The way cached instance metadata is stored differs, but since those
-will be refetched and updated anyway, there’s no need for a backup.
-
-Best check all newer migrations unique to Akkoma/Pleroma
-to get an up-to-date picture of what needs to be kept.
-
 ## From Source

 If you're running the source Akkoma install, you'll need to set the
@ -61,7 +34,16 @@ git pull -r
 # to run "git merge stable" instead (or develop if you want)
 ```

-And compile as usual.
+### WARNING - Migrating from Pleroma Develop
+If you are on pleroma develop, and have updated since 2022-08, you may have issues with database migrations.
+
+Please roll back the given migrations:
+
+```bash
+MIX_ENV=prod mix ecto.rollback --migrations-path priv/repo/optional_migrations/pleroma_develop_rollbacks -n3
+```
+
+Then compile, migrate and restart as usual.

 ## From OTP

@ -71,44 +53,15 @@ This will just be setting the update URL - find your flavour from the [mapping o
 export FLAVOUR=[the flavour you found above]

 ./bin/pleroma_ctl update --zip-url https://akkoma-updates.s3-website.fr-par.scw.cloud/stable/akkoma-$FLAVOUR.zip
+./bin/pleroma_ctl migrate
 ```

-When updating in the future, you can just use
+Then restart. When updating in the future, you canjust use

 ```bash
 ./bin/pleroma_ctl update --branch stable
 ```

-
-## Database Migrations
-### WARNING - Migrating from Pleroma past 2022-08
-If you are on Pleroma stable >= 2.5.0 or Pleroma develop, and
-have updated since 2022-08, you may have issues with database migrations.
-
-Please first roll back the given migrations:
-
-=== "OTP"
-    ```bash
-    ./bin/pleroma_ctl rollback --migrations-path priv/repo/optional_migrations/pleroma_develop_rollbacks -n5
-    ```
-=== "From Source"
-    ```bash
-    MIX_ENV=prod mix ecto.rollback --migrations-path priv/repo/optional_migrations/pleroma_develop_rollbacks -n5
-    ```
-
-### Applying Akkoma Database Migrations
-
-Just run
-
-=== "OTP"
-    ```bash
-    ./bin/pleroma_ctl migrate
-    ```
-=== "From Source"
-    ```bash
-    MIX_ENV=prod mix ecto.migrate
-    ```
-
 ## Frontend changes

 Akkoma comes with a few frontend changes as well as backend ones,
@ -165,16 +118,3 @@ To fix this, run:
    ```

 which will remove the config from the database. Things should work now.
-
-## Migrating back to Pleroma
-
-Akkoma is a hard fork of Pleroma. As such, migrating back is not guaranteed to always work. But if you want to migrate back to Pleroma, you can always try. Just note that you may run into unexpected issues and you're basically on your own. The following are some tips that may help, but note that these are barely tested, so proceed at your own risk.
-
-First you will need to roll back the database migrations. The latest migration both Akkoma and Pleroma still have in common should be 20210416051708, so roll back to that. If you run from source, that should be
-
-```sh
-MIX_ENV=prod mix ecto.rollback --to 20210416051708
-```
-
-Then switch back to Pleroma for updates (similar to how was done to migrate to Akkoma), and remove the front-ends. The front-ends are installed in the `frontends` folder in the [static directory](../configuration/static_dir.md). Once you are back to Pleroma, you will need to run the database migrations again. See the Pleroma documentation for this.
-After this use your previous backups to restore data from diverging features.
--- a/docs/docs/installation/migrating_to_docker_en.md
+++ b/docs/docs/installation/migrating_to_docker_en.md
@ -10,7 +10,7 @@ You probably should, in the first instance.

 ### Prepare the system

-* Install docker and docker compose
+* Install docker and docker-compose
    * [Docker](https://docs.docker.com/engine/install/)
    * [Docker-compose](https://docs.docker.com/compose/install/)
    * This will usually just be a repository installation and a package manager invocation.
@ -46,7 +46,7 @@ For *most* from-source installs it'll already be there.
 And the same with `uploads`, make sure your uploads (if you have them on disk) are
 located at `uploads/` in the akkoma source directory.

-If you have them on a different disk, you will need to mount that disk into the docker compose file,
+If you have them on a different disk, you will need to mount that disk into the docker-compose file,
 with an entry that looks like this:

 ```yaml
@ -66,7 +66,7 @@ echo "DOCKER_USER=$(id -u):$(id -g)" >> .env
 ```

 This probably won't need to be changed, it's only there to set basic environment
-variables for the docker compose file.
+variables for the docker-compose file.

 === "From source"

@ -126,21 +126,21 @@ mkdir pgdata
 Now we can import our database to the container.

 ```bash
-docker compose run --rm --user akkoma -d db 
-docker compose run --rm akkoma pg_restore -v -U akkoma -j $(grep -c ^processor /proc/cpuinfo) -d akkoma -h db akkoma_backup.sql
+docker-compose run --rm --user akkoma -d db 
+docker-compose run --rm akkoma pg_restore -v -U akkoma -j $(grep -c ^processor /proc/cpuinfo) -d akkoma -h db akkoma_backup.sql
 ```

 ### Reverse proxies

 If you're just reusing your old proxy, you may have to uncomment the line in
-the docker compose file under `ports`. You'll find it.
+the docker-compose file under `ports`. You'll find it.

 Otherwise, you can use the same setup as the [docker installation guide](./docker_en.md#reverse-proxies).

 ### Let's go

 ```bash
-docker compose up -d
+docker-compose up -d
 ```

 You should now be at the same point as you were before, but with a docker install.
--- a/docs/docs/installation/openbsd_en.md
+++ b/docs/docs/installation/openbsd_en.md
@ -1,6 +1,6 @@
 # Installing on OpenBSD

-This guide describes the installation and configuration of akkoma (and the required software to run it) on a single OpenBSD 7.2 server.
+This guide describes the installation and configuration of akkoma (and the required software to run it) on a single OpenBSD 6.6 server.

 For any additional information regarding commands and configuration files mentioned here, check the man pages [online](https://man.openbsd.org/) or directly on your server with the man command.

@ -12,8 +12,7 @@ For any additional information regarding commands and configuration files mentio
 To install them, run the following command (with doas or as root):

 ```
-pkg_add elixir gmake git postgresql-server postgresql-contrib cmake ffmpeg erlang-wx libmagic
-pkg_add erlang-wx # Choose the latest version as package version when promted
+pkg_add elixir gmake git postgresql-server postgresql-contrib cmake ffmpeg ImageMagick
 ```

 Akkoma requires a reverse proxy, OpenBSD has relayd in base (and is used in this guide) and packages/ports are available for nginx (www/nginx) and apache (www/apache-httpd). Independently of the reverse proxy, [acme-client(1)](https://man.openbsd.org/acme-client) can be used to get a certificate from Let's Encrypt.
@ -28,35 +27,32 @@ Per [`docs/installation/optional/media_graphics_packages.md`](../installation/op
 To install the above:

 ```
-pkg_add ffmpeg p5-Image-ExifTool
+pkg_add ImageMagick ffmpeg p5-Image-ExifTool
 ```

 #### Creating the akkoma user
-Akkoma will be run by a dedicated user, `_akkoma`. Before creating it, insert the following lines in `/etc/login.conf`:
+Akkoma will be run by a dedicated user, \_akkoma. Before creating it, insert the following lines in login.conf:
 ```
 akkoma:\
 	:datasize-max=1536M:\
 	:datasize-cur=1536M:\
 	:openfiles-max=4096
 ```
-This creates a `akkoma` login class and sets higher values than default for datasize and openfiles (see [login.conf(5)](https://man.openbsd.org/login.conf)), this is required to avoid having akkoma crash some time after starting.
+This creates a "akkoma" login class and sets higher values than default for datasize and openfiles (see [login.conf(5)](https://man.openbsd.org/login.conf)), this is required to avoid having akkoma crash some time after starting.

-Create the `_akkoma` user, assign it the akkoma login class and create its home directory (`/home/_akkoma/`): `useradd -m -L akkoma _akkoma`
+Create the \_akkoma user, assign it the akkoma login class and create its home directory (/home/\_akkoma/): `useradd -m -L akkoma _akkoma`

 #### Clone akkoma's directory
-Enter a shell as the `_akkoma` user. As root, run `su _akkoma -;cd`. Then clone the repository with `git clone https://akkoma.dev/AkkomaGang/akkoma.git`. Akkoma is now installed in `/home/_akkoma/akkoma/`, it will be configured and started at the end of this guide.
+Enter a shell as the \_akkoma user. As root, run `su _akkoma -;cd`. Then clone the repository with `git clone https://akkoma.dev/AkkomaGang/akkoma.git`. Akkoma is now installed in /home/\_akkoma/akkoma/, it will be configured and started at the end of this guide.

 #### PostgreSQL
-Create `_postgresql`'s user directory (it hasn't been created yet): `mdir var/postgresql/data`. To set it as home
-directory for user `_postgresql` run `usermod -d  /var/postgresql/data _postgresql`.
-
-Start a shell as the `_postgresql` user (as root run `su _postgresql -` then run the `initdb` command to initialize postgresql.
-You will need to specify pgdata directory to the default (`/var/postgresql/data`) with the `-D <path>` and set the user to postgres with the `-U <username>` flag. This can be done as follows:
+Start a shell as the \_postgresql user (as root run `su _postgresql -` then run the `initdb` command to initialize postgresql:
+You will need to specify pgdata directory to the default (/var/postgresql/data) with the `-D <path>` and set the user to postgres with the `-U <username>` flag. This can be done as follows:

 ```
 initdb -D /var/postgresql/data -U postgres
 ```
-If you are not using the default directory, you will have to update the `datadir` variable in the `/etc/rc.d/postgresql` script.
+If you are not using the default directory, you will have to update the `datadir` variable in the /etc/rc.d/postgresql script.

 When this is done, enable postgresql so that it starts on boot and start it. As root, run:
 ```
@ -72,7 +68,7 @@ httpd will have three fuctions:
  * serve a robots.txt file
  * get Let's Encrypt certificates, with acme-client

-Insert the following config in `/etc/httpd.conf`:
+Insert the following config in httpd.conf:
 ```
 # $OpenBSD: httpd.conf,v 1.17 2017/04/16 08:50:49 ajacoutot Exp $

@ -95,10 +91,13 @@ server "default" {
 	location "/robots.txt" { root "/htdocs/local/" }
 	location "/*" { block return 302 "https://$HTTP_HOST$REQUEST_URI" }
 }
+
+types {
+}
 ```
 Do not forget to change *<IPv4/6 address\>* to your server's address(es). If httpd should only listen on one protocol family, comment one of the two first *listen* options.

-Create the `/var/www/htdocs/local/` folder and write the content of your robots.txt in `/var/www/htdocs/local/robots.txt`.
+Create the /var/www/htdocs/local/ folder and write the content of your robots.txt in /var/www/htdocs/local/robots.txt.
 Check the configuration with `httpd -n`, if it is OK enable and start httpd (as root):
 ```
 rcctl enable httpd
@ -107,7 +106,7 @@ rcctl start httpd

 #### acme-client
 acme-client is used to get SSL/TLS certificates from Let's Encrypt.
-Insert the following configuration in `/etc/acme-client.conf`:
+Insert the following configuration in /etc/acme-client.conf:
 ```
 #
 # $OpenBSD: acme-client.conf,v 1.4 2017/03/22 11:14:14 benno Exp $
@ -128,7 +127,7 @@ domain <domain name> {
 }
 ```
 Replace *<domain name\>* by the domain name you'll use for your instance. As root, run `acme-client -n` to check the config, then `acme-client -ADv <domain name>` to create account and domain keys, and request a certificate for the first time.
-Make acme-client run everyday by adding it in `/etc/daily.local`. As root, run the following command: `echo "acme-client <domain name>" >> /etc/daily.local`.
+Make acme-client run everyday by adding it in /etc/daily.local. As root, run the following command: `echo "acme-client <domain name>" >> /etc/daily.local`.

 Relayd will look for certificates and keys based on the address it listens on (see next part), the easiest way to make them available to relayd is to create a link, as root run:
 ```
@ -139,7 +138,7 @@ This will have to be done for each IPv4 and IPv6 address relayd listens on.

 #### relayd
 relayd will be used as the reverse proxy sitting in front of akkoma.
-Insert the following configuration in `/etc/relayd.conf`:
+Insert the following configuration in /etc/relayd.conf:
 ```
 # $OpenBSD: relayd.conf,v 1.4 2018/03/23 09:55:06 claudio Exp $

@ -197,7 +196,7 @@ rcctl start relayd

 #### pf
 Enabling and configuring pf is highly recommended.
-In `/etc/pf.conf`, insert the following configuration:
+In /etc/pf.conf, insert the following configuration:
 ```
 # Macros
 if="<network interface>"
@ -221,30 +220,31 @@ pass in quick on $if inet6 proto icmp6 to ($if) icmp6-type { echoreq unreach par
 pass in quick on $if proto tcp to ($if) port { http https } # relayd/httpd
 pass in quick on $if proto tcp from $authorized_ssh_clients to ($if) port ssh
 ```
-Replace *<network interface\>* by your server's network interface name (which you can get with ifconfig). Consider replacing the content of the `authorized_ssh_clients` macro by, for example, your home IP address, to avoid SSH connection attempts from bots.
+Replace *<network interface\>* by your server's network interface name (which you can get with ifconfig). Consider replacing the content of the authorized\_ssh\_clients macro by, for exemple, your home IP address, to avoid SSH connection attempts from bots.

 Check pf's configuration by running `pfctl -nf /etc/pf.conf`, load it with `pfctl -f /etc/pf.conf` and enable pf at boot with `rcctl enable pf`.

 #### Configure and start akkoma
-Enter a shell as `_akkoma` (as root `su _akkoma -`) and enter akkoma's installation directory (`cd ~/akkoma/`).
+Enter a shell as \_akkoma (as root `su _akkoma -`) and enter akkoma's installation directory (`cd ~/akkoma/`).

 Then follow the main installation guide:

  * run `mix deps.get`
  * run `MIX_ENV=prod mix pleroma.instance gen` and enter your instance's information when asked
-  * copy `config/generated_config.exs` to `config/prod.secret.exs`. The default values should be sufficient but you should edit it and check that everything seems OK.
+  * copy config/generated\_config.exs to config/prod.secret.exs. The default values should be sufficient but you should edit it and check that everything seems OK.
  * exit your current shell back to a root one and run `psql -U postgres -f /home/_akkoma/akkoma/config/setup_db.psql` to setup the database.
-  * return to a `_akkoma` shell into akkoma's installation directory (`su _akkoma -;cd ~/akkoma`) and run `MIX_ENV=prod mix ecto.migrate`
+  * return to a \_akkoma shell into akkoma's installation directory (`su _akkoma -;cd ~/akkoma`) and run `MIX_ENV=prod mix ecto.migrate`

-As `_akkoma` in `/home/_akkoma/akkoma`, you can now run `LC_ALL=en_US.UTF-8 MIX_ENV=prod mix phx.server` to start your instance.
+As \_akkoma in /home/\_akkoma/akkoma, you can now run `LC_ALL=en_US.UTF-8 MIX_ENV=prod mix phx.server` to start your instance.
 In another SSH session/tmux window, check that it is working properly by running `ftp -MVo - http://127.0.0.1:4000/api/v1/instance`, you should get json output. Double-check that *uri*'s value is your instance's domain name.

 ##### Starting akkoma at boot
 An rc script to automatically start akkoma at boot hasn't been written yet, it can be run in a tmux session (tmux is in base).

+
 #### Create administrative user

-If your instance is up and running, you can create your first user with administrative rights with the following command as the `_akkoma` user.
+If your instance is up and running, you can create your first user with administrative rights with the following command as the \_akkoma user.
 ```
 LC_ALL=en_US.UTF-8 MIX_ENV=prod mix pleroma.user new <username> <your@emailaddress> --admin
 ```
--- a/docs/docs/installation/optional/media_graphics_packages.md
+++ b/docs/docs/installation/optional/media_graphics_packages.md
@ -1,33 +1,32 @@
 # Optional software packages needed for specific functionality

-For specific Akkoma functionality (which is disabled by default) some or all of the below packages are required:
-  * `ImageMagick`
+For specific Pleroma functionality (which is disabled by default) some or all of the below packages are required:
+  * `ImageMagic`
  * `ffmpeg`
  * `exiftool`
  
 Please refer to documentation in `docs/installation` on how to install them on specific OS.
  
-Note: the packages are not required with the current default settings of Akkoma.
+Note: the packages are not required with the current default settings of Pleroma.

 ## `ImageMagick`

 `ImageMagick` is a set of tools to create, edit, compose, or convert bitmap images.

-It is required for the following Akkoma features:
-  * `Pleroma.Upload.Filters.Mogrify`, `Pleroma.Upload.Filters.Mogrifun` upload filters (related config: `Pleroma.Upload/filters` in `config/config.exs`)
+It is required for the following Pleroma features:
+  * `Pleroma.Upload.Filters.Mogrify`, `Pleroma.Upload.Filters.Mogrifun` upload filters (related config: `Plaroma.Upload/filters` in `config/config.exs`)
  * Media preview proxy for still images (related config: `media_preview_proxy/enabled` in `config/config.exs`)
  
 ## `ffmpeg`

 `ffmpeg` is software to record, convert and stream audio and video.

-It is required for the following Akkoma features:
+It is required for the following Pleroma features:
  * Media preview proxy for videos (related config: `media_preview_proxy/enabled` in `config/config.exs`)

 ## `exiftool`

 `exiftool` is media files metadata reader/writer.

-It is required for the following Akkoma features:
-  * `Pleroma.Upload.Filters.Exiftool.StripMetadata` upload filter (related config: `Pleroma.Upload/filters` in `config/config.exs`)
-  * `Pleroma.Upload.Filters.Exiftool.ReadDescription` upload filter (related config: `Pleroma.Upload/filters` in `config/config.exs`)
+It is required for the following Pleroma features:
+  * `Pleroma.Upload.Filters.Exiftool` upload filter (related config: `Plaroma.Upload/filters` in `config/config.exs`)
--- a/docs/docs/installation/otp_en.md
+++ b/docs/docs/installation/otp_en.md
@ -5,26 +5,26 @@
 This guide covers a installation using an OTP release. To install Akkoma from source, please check out the corresponding guide for your distro.

 ## Pre-requisites
-* A machine running Linux with GNU (e.g. Debian, Ubuntu) or musl (e.g. Alpine) libc and an `x86_64` or `arm64` CPU you have root access to. If you are not sure if it's compatible see [Detecting flavour section](#detecting-flavour) below
+* A machine running Linux with GNU (e.g. Debian, Ubuntu) or musl (e.g. Alpine) libc and `x86_64`, `aarch64` or `armv7l` CPU, you have root access to. If you are not sure if it's compatible see [Detecting flavour section](#detecting-flavour) below
 * For installing OTP releases on RedHat-based distros like Fedora and Centos Stream, please follow [this guide](./otp_redhat_en.md) instead.
 * A (sub)domain pointed to the machine

-You will be running commands as root. If you aren't root already, please elevate your priviledges by executing `sudo -i`/`su`.
+You will be running commands as root. If you aren't root already, please elevate your priviledges by executing `sudo su`/`su`.

 While in theory OTP releases are possbile to install on any compatible machine, for the sake of simplicity this guide focuses only on Debian/Ubuntu and Alpine.

 ### Detecting flavour

+This is a little more complex than it used to be (thanks ubuntu)
+
 Use the following mapping to figure out your flavour:

-| distribution    | architecture       | flavour             | available branches  |
-| --------------- | ------------------ | ------------------- | ------------------- |
-| debian bookworm | amd64              | amd64               | develop, stable     |
-| debian bookworm | arm64              | arm64               | stable              |
-| ubuntu jammy    | amd64              | amd64               | develop, stable     |
-| ubuntu jammy    | arm64              | arm64               | develop, stable     |
-| alpine          | amd64              | amd64-musl          | stable              |
-| alpine          | arm64              | arm64-musl          | stable              |
+| distribution  | flavour            | available branches  |
+| ------------- | ------------------ | ------------------- |
+| debian stable | amd64              | develop, stable     |
+| ubuntu focal  | amd64              | develop, stable     |
+| ubuntu jammy  | amd64-ubuntu-jammy | develop, stable     |
+| alpine        | amd64-musl         | stable              |

 Other similar distributions will _probably_ work, but if it is not listed above, there is no official
 support.
@ -119,11 +119,7 @@ adduser --system --shell  /bin/false --home /opt/akkoma akkoma

 # Set the flavour environment variable to the string you got in Detecting flavour section.
 # For example if the flavour is `amd64-musl` the command will be
-#     export FLAVOUR="amd64-musl"
-export FLAVOUR="<replace-this-with-the-correct-flavour-string>"
-
-# Make sure the SHELL variable is set
-export SHELL="${SHELL:-/bin/sh}"
+export FLAVOUR="amd64-musl"

 # Clone the release build into a temporary directory and unpack it
 su akkoma -s $SHELL -lc "
@ -176,24 +172,29 @@ su akkoma -s $SHELL -lc "./bin/pleroma stop"

 ### Setting up nginx and getting Let's Encrypt SSL certificaties

+#### Get a Let's Encrypt certificate
+```sh
+certbot certonly --standalone --preferred-challenges http -d yourinstance.tld
+```
+
 #### Copy Akkoma nginx configuration to the nginx folder

 The location of nginx configs is dependent on the distro

 === "Alpine"
    ```
-    cp /opt/akkoma/installation/akkoma.nginx /etc/nginx/conf.d/akkoma.conf
+    cp /opt/akkoma/installation/nginx/akkoma.nginx /etc/nginx/conf.d/akkoma.conf
    ```

 === "Debian/Ubuntu"
    ```
-    cp /opt/akkoma/installation/akkoma.nginx /etc/nginx/sites-available/akkoma.conf
+    cp /opt/akkoma/installation/nginx/akkoma.nginx /etc/nginx/sites-available/akkoma.conf
    ln -s /etc/nginx/sites-available/akkoma.conf /etc/nginx/sites-enabled/akkoma.conf
    ```

 If your distro does not have either of those you can append `include /etc/nginx/akkoma.conf` to the end of the http section in /etc/nginx/nginx.conf and
 ```sh
-cp /opt/akkoma/installation/akkoma.nginx /etc/nginx/akkoma.conf
+cp /opt/akkoma/installation/nginx/akkoma.nginx /etc/nginx/akkoma.conf
 ```

 #### Edit the nginx config
@ -204,14 +205,6 @@ $EDITOR path-to-nginx-config
 # Verify that the config is valid
 nginx -t
 ```
-
-#### Get a Let's Encrypt certificate
-```sh
-certbot --nginx -d yourinstance.tld -d media.yourinstance.tld
-```
-
-If that doesn't work the first time, add `--dry-run` to further attempts to avoid being ratelimited as you identify the issue, and do not remove it until the dry run succeeds. A common source of problems are nginx config syntax errors; this can be checked for by running `nginx -t`.
-
 #### Start nginx

 === "Alpine"
@ -255,19 +248,32 @@ If everything worked, you should see Akkoma-FE when visiting your domain. If tha
 ## Post installation

 ### Setting up auto-renew of the Let's Encrypt certificate
+```sh
+# Create the directory for webroot challenges
+mkdir -p /var/lib/letsencrypt
+
+# Uncomment the webroot method
+$EDITOR path-to-nginx-config
+
+# Verify that the config is valid
+nginx -t
+```

 === "Alpine"
    ```
+    # Restart nginx
+    rc-service nginx restart
+
    # Start the cron daemon and make it start on boot
    rc-service crond start
    rc-update add crond

    # Ensure the webroot menthod and post hook is working
-    certbot renew --cert-name yourinstance.tld --nginx --dry-run
+    certbot renew --cert-name yourinstance.tld --webroot -w /var/lib/letsencrypt/ --dry-run --post-hook 'rc-service nginx reload'

    # Add it to the daily cron
    echo '#!/bin/sh
-    certbot renew --cert-name yourinstance.tld --nginx
+    certbot renew --cert-name yourinstance.tld --webroot -w /var/lib/letsencrypt/ --post-hook "rc-service nginx reload"
    ' > /etc/periodic/daily/renew-akkoma-cert
    chmod +x /etc/periodic/daily/renew-akkoma-cert

@ -276,7 +282,22 @@ If everything worked, you should see Akkoma-FE when visiting your domain. If tha
    ```

 === "Debian/Ubuntu"
-    This should be automatically enabled with the `certbot-renew.timer` systemd unit.
+    ```
+    # Restart nginx
+    systemctl restart nginx
+
+    # Ensure the webroot menthod and post hook is working
+    certbot renew --cert-name yourinstance.tld --webroot -w /var/lib/letsencrypt/ --dry-run --post-hook 'systemctl reload nginx'
+
+    # Add it to the daily cron
+    echo '#!/bin/sh
+    certbot renew --cert-name yourinstance.tld --webroot -w /var/lib/letsencrypt/ --post-hook "systemctl reload nginx"
+    ' > /etc/cron.daily/renew-akkoma-cert
+    chmod +x /etc/cron.daily/renew-akkoma-cert
+
+    # If everything worked the output should contain /etc/cron.daily/renew-akkoma-cert
+    run-parts --test /etc/cron.daily
+    ```

 ## Create your first user and set as admin
 ```sh
--- a/docs/docs/installation/otp_redhat_en.md
+++ b/docs/docs/installation/otp_redhat_en.md
@ -37,7 +37,7 @@ sudo dnf install git gcc g++ erlang elixir erlang-os_mon erlang-eldap erlang-xme

 ```shell
 cd ~
-git clone https://akkoma.dev/AkkomaGang/akkoma.git -b stable
+git clone https://akkoma.dev/AkkomaGang/akkoma.git
 ```

 * Change to the new directory:
@ -82,7 +82,6 @@ Other than things bundled in the OTP release Akkoma depends on:
 * PostgreSQL (also utilizes extensions in postgresql-contrib)
 * nginx (could be swapped with another reverse proxy but this guide covers only it)
 * certbot (for Let's Encrypt certificates, could be swapped with another ACME client, but this guide covers only it)
-    * If you are using certbot, also install the `python3-certbot-nginx` package for the nginx plugin
 * libmagic/file

 First, update your system, if not already done:
@ -170,10 +169,16 @@ sudo -Hu akkoma ./bin/pleroma stop

 ### Setting up nginx and getting Let's Encrypt SSL certificaties

+#### Get a Let's Encrypt certificate
+
+```shell
+certbot certonly --standalone --preferred-challenges http -d yourinstance.tld
+```
+
 #### Copy Akkoma nginx configuration to the nginx folder

 ```shell
-cp /opt/akkoma/installation/akkoma.nginx /etc/nginx/conf.d/akkoma.conf
+cp /opt/akkoma/installation/nginx/akkoma.nginx /etc/nginx/conf.d/akkoma.conf
 ```

 #### Edit the nginx config
@ -190,15 +195,8 @@ sudo nginx -t
 sudo systemctl start nginx
 ```

-#### Get a Let's Encrypt certificate
+At this point if you open your (sub)domain in a browser you should see a 502 error, that's because Akkoma is not started yet.

-```shell
-sudo certbot --email <your@emailaddress> -d <yourdomain> -d <media_domain> --nginx
-```
-
-If that doesn't work the first time, add `--dry-run` to further attempts to avoid being ratelimited as you identify the issue, and do not remove it until the dry run succeeds. A common source of problems are nginx config syntax errors; this can be checked for by running `nginx -t`.
-
-If you're successful with obtaining the certificates, opening your (sub)domain in a browser will result in a 502 error, since Akkoma hasn't been started yet.

 ### Setting up a system service

@ -241,11 +239,19 @@ sudo nginx -t
 # Restart nginx
 sudo systemctl restart nginx

-# Test that renewals work properly
-sudo certbot renew --cert-name yourinstance.tld --nginx --dry-run
+# Ensure the webroot menthod and post hook is working
+sudo certbot renew --cert-name yourinstance.tld --webroot -w /var/lib/letsencrypt/ --dry-run --post-hook 'systemctl reload nginx'
+
+# Add it to the daily cron
+echo '#!/bin/sh
+certbot renew --cert-name yourinstance.tld --webroot -w /var/lib/letsencrypt/ --post-hook "systemctl reload nginx"
+' > /etc/cron.daily/renew-akkoma-cert
+sudo chmod +x /etc/cron.daily/renew-akkoma-cert
+
+# If everything worked the output should contain /etc/cron.daily/renew-akkoma-cert
+sudo run-parts --test /etc/cron.daily
 ```

-Assuming the commands were run successfully, certbot should be able to renew your certificates automatically via the `certbot-renew.timer` systemd unit.

 ## Create your first user and set as admin
 ```shell
--- a/docs/docs/installation/verifying_otp_releases.md
+++ b/docs/docs/installation/verifying_otp_releases.md
@ -12,7 +12,7 @@ Release URLs will always be of the form
 https://akkoma-updates.s3-website.fr-par.scw.cloud/{branch}/akkoma-{flavour}.zip
 ```

-Where branch is usually `stable` and `flavour` is
+Where branch is usually `stable` or `develop`, and `flavour` is
 the one [that you detect on install](../otp_en/#detecting-flavour).

 So, for an AMD64 stable install, your update URL will be
--- a/docs/docs/installation/yunohost_en.md
+++ b/docs/docs/installation/yunohost_en.md
@ -1,9 +0,0 @@
-# Installing on Yunohost
-
-[YunoHost](https://yunohost.org) is a server operating system aimed at self-hosting. The YunoHost community maintains a package of Akkoma which allows you to install Akkoma on YunoHost. You can install it via the normal way through the admin web interface, or through the CLI. More information can be found at [the repo of the package](https://github.com/YunoHost-Apps/akkoma_ynh).
-
-## Questions
-
-Questions and problems related to the YunoHost parts can be done through the [YunoHost channels](https://yunohost.org/en/help).
-
-For questions about Akkoma, check out the [Akkoma community channels](../../#community-channels).
--- a/docs/mkdocs.yml
+++ b/docs/mkdocs.yml
@ -1,30 +1,14 @@
 site_name: Akkoma Documentation
 theme:
-  favicon: 'images/favicon.ico'
+  favicon: 'images/akko_badday.png'
  name: 'material'
  custom_dir: 'theme'
  # Disable google fonts
  font: false
-  logo: 'images/logo.png'
+  logo: 'images/akko_badday.png'
  features:
-    - navigation.tabs
-    - toc.follow
-    - navigation.instant
-    - navigation.sections
+    - tabs
  palette:
-    - media: "(prefers-color-scheme: light)"
-      scheme: default
-      toggle:
-        icon: material/brightness-7
-        name: Switch to dark mode
-      primary: 'deep purple'
-      accent: 'blue grey'
-
-    - media: "(prefers-color-scheme: dark)"
-      scheme: slate
-      toggle:
-        icon: material/brightness-4
-        name: Switch to light mode
    primary: 'deep purple'
    accent: 'blue grey'

@ -47,8 +31,7 @@ markdown_extensions:
  - pymdownx.tasklist:
      custom_checkbox: true
  - pymdownx.superfences
-  - pymdownx.tabbed:
-      alternate_style: true
+  - pymdownx.tabbed
  - pymdownx.details
  - markdown_include.include:
      base_path: docs
--- a/docs/theme/partials/source.html
+++ b/docs/theme/partials/source.html
@ -38,11 +38,11 @@
 {% endif %}

 {% if page and page.url.startswith('backend') %}
-  {% set repo_url = "https://akkoma.dev/AkkomaGang/akkoma" %}
-  {% set repo_name = "AkkomaGang/akkoma" %}
+  {% set repo_url = "https://git.pleroma.social/pleroma/pleroma" %}
+  {% set repo_name = "pleroma/pleroma" %}
 {% elif page and page.url.startswith('frontend') %}
-  {% set repo_url = "https://akkoma.dev/AkkomaGang/akkoma-fe" %}
-  {% set repo_name = "AkkomaGang/akkoma-fe" %}
+  {% set repo_url = "https://git.pleroma.social/pleroma/pleroma-fe" %}
+  {% set repo_name = "pleroma/pleroma-fe" %}
 {% else %}
  {% set repo_url = config.repo_url %}
  {% set repo_name = config.repo_name %}
--- a/elixir_buildpack.config
+++ b/elixir_buildpack.config
@ -0,0 +1,2 @@
+elixir_version=1.9.4
+erlang_version=22.3.4.1
--- a/installation/akkoma.service
+++ b/installation/akkoma.service
@ -4,24 +4,14 @@ After=network.target postgresql.service

 [Service]
 ExecReload=/bin/kill $MAINPID
+KillMode=process
 Restart=on-failure

-; Uncomment this if you're on Arch Linux
-; Environment="PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl"
-; Uncomment if using asdf to manage Elixir and Erlang
-; Environment="PATH=/var/lib/akkoma/.asdf/shims:/var/lib/akkoma/.asdf/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
-
 ; Name of the user that runs the Akkoma service.
 User=akkoma
 ; Declares that Akkoma runs in production mode.
 Environment="MIX_ENV=prod"

-; Don't listen epmd on 0.0.0.0
-Environment="ERL_EPMD_ADDRESS=127.0.0.1"
-
-; Don't busy wait
-Environment="ERL_AFLAGS=+sbwt none +sbwtdcpu none +sbwtdio none"
-
 ; Make sure that all paths fit your installation.
 ; Path to the home directory of the user running the Akkoma service.
 Environment="HOME=/var/lib/akkoma"
@ -29,8 +19,6 @@ Environment="HOME=/var/lib/akkoma"
 WorkingDirectory=/opt/akkoma
 ; Path to the Mix binary.
 ExecStart=/usr/bin/mix phx.server
-; If using asdf comment the above line and uncomment the one below instead
-; ExecStart=/var/lib/akkoma/.asdf/shims/mix phx.server

 ; Some security directives.
 ; Use private /tmp and /var/tmp folders inside a new file system namespace, which are discarded after the process stops.
@ -41,8 +29,6 @@ ProtectHome=true
 ProtectSystem=full
 ; Sets up a new /dev mount for the process and only adds API pseudo devices like /dev/null, /dev/zero or /dev/random but not physical devices. Disabled by default because it may not work on devices like the Raspberry Pi.
 PrivateDevices=false
-; Ensures that the service process and all its children can never gain new privileges through execve(). 
-NoNewPrivileges=true
 ; Drops the sysadmin capability from the daemon.
 CapabilityBoundingSet=~CAP_SYS_ADMIN

--- a/installation/akkoma.supervisord
+++ b/installation/akkoma.supervisord
@ -12,8 +12,7 @@ environment =
  HOME=/home/akkoma,
  USER=akkoma,
  PATH="/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/home/akkoma/bin:%(ENV_PATH)s",
-  PWD=/home/akkoma/akkoma,
-  ERL_EPMD_ADDRESS=127.0.0.1
+  PWD=/home/akkoma/akkoma
 stdout_logfile=/home/akkoma/logs/stdout.log
 stdout_logfile_maxbytes=50MB
 stdout_logfile_backups=10
--- a/installation/akkoma.vcl
+++ b/installation/akkoma.vcl
@ -1,5 +1,4 @@
 # Recommended varnishncsa logging format: '%h %l %u %t "%m %{X-Forwarded-Proto}i://%{Host}i%U%q %H" %s %b "%{Referer}i" "%{User-agent}i"'
-# Please use Varnish 7.0+ for proper Range Requests / Chunked encoding support
 vcl 4.1;
 import std;

@ -23,6 +22,11 @@ sub vcl_recv {
      set req.http.X-Forwarded-Proto = "https";
    }

+    # CHUNKED SUPPORT
+    if (req.http.Range ~ "bytes=") {
+      set req.http.x-range = req.http.Range;
+    }
+
    # Pipe if WebSockets request is coming through
    if (req.http.upgrade ~ "(?i)websocket") {
      return (pipe);
@ -49,6 +53,12 @@ sub vcl_backend_response {
      return (retry);
    }

+    # CHUNKED SUPPORT
+    if (bereq.http.x-range ~ "bytes=" && beresp.status == 206) {
+      set beresp.ttl = 10m;
+      set beresp.http.CR = beresp.http.content-range;
+    }
+
    # Bypass cache for large files
    # 50000000 ~ 50MB
    if (std.integer(beresp.http.content-length, 0) > 50000000) {
@ -96,12 +106,25 @@ sub vcl_pipe {
    }
 }

+sub vcl_hash {
+    # CHUNKED SUPPORT
+    if (req.http.x-range ~ "bytes=") {
+      hash_data(req.http.x-range);
+      unset req.http.Range;
+    }
+}
+
 sub vcl_backend_fetch {
    # Be more lenient for slow servers on the fediverse
    if (bereq.url ~ "^/proxy/") {
      set bereq.first_byte_timeout = 300s;
    }

+    # CHUNKED SUPPORT
+    if (bereq.http.x-range) {
+      set bereq.http.Range = bereq.http.x-range;
+    }
+
    if (bereq.retries == 0) {
        # Clean up the X-Varnish-Backend-503 flag that is used internally
        # to mark broken backend responses that should be retried.
@ -120,6 +143,14 @@ sub vcl_backend_fetch {
    }
 }

+sub vcl_deliver {
+    # CHUNKED SUPPORT
+    if (resp.http.CR) {
+      set resp.http.Content-Range = resp.http.CR;
+      unset resp.http.CR;
+    }
+}
+
 sub vcl_backend_error {
    # Retry broken backend responses.
    set bereq.http.X-Varnish-Backend-503 = "1";
--- a/installation/apache/akkoma-apache.conf
+++ b/installation/apache/akkoma-apache.conf
@ -60,7 +60,7 @@ ServerTokens Prod
    Include /etc/letsencrypt/options-ssl-apache.conf

    # Uncomment the following to enable MediaProxy caching on disk
-    #CacheRoot /var/tmp/akkoma-media-cache/
+    #CacheRoot /tmp/akkoma-media-cache/
    #CacheDirLevels 1
    #CacheDirLength 2
    #CacheEnable disk /proxy
--- a/installation/apache/apache-cache-purge.sh.example
+++ b/installation/apache/apache-cache-purge.sh.example
@ -16,7 +16,7 @@
 SCRIPTNAME=${0##*/}

 # mod_disk_cache directory
-CACHE_DIRECTORY="/var/tmp/akkoma-media-cache"
+CACHE_DIRECTORY="/tmp/akkoma-media-cache"

 ## Removes an item via the htcacheclean utility
 ## $1 - the filename, can be a pattern .
--- a/Show more
+++ b/Show more
				`@ -0,0 +1 @@`
				`https://github.com/hashnuke/heroku-buildpack-elixir`