run credo on PR

2022-12-14 12:49:14 +00:00
567 changed files with 11554 additions and 131962 deletions
--- a/.formatter.exs
+++ b/.formatter.exs
@ -1,14 +1,3 @@
 [
-  import_deps: [:ecto, :ecto_sql, :phoenix],
+  inputs: ["mix.exs", "{config,lib,test}/**/*.{ex,exs}", "priv/repo/migrations/*.exs", "priv/repo/optional_migrations/**/*.exs", "priv/scrubbers/*.ex"]
  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"
  ]
 ]
--- a/.gitattributes
+++ b/.gitattributes
@ -1,4 +1,11 @@
 *.ex diff=elixir
 *.exs diff=elixir
-*.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
 priv/static/instance/static.css diff=css
 priv/static/static-fe/static-fe.css diff=css
--- a/.gitignore
+++ b/.gitignore
@ -73,8 +73,6 @@ pleroma.iml
 # Generated documentation
 docs/site
 docs/venv
 # docker stuff
 docker-db
 *.iml
--- a/.woodpecker.yml
+++ b/.woodpecker.yml
@ -0,0 +1,205 @@
 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: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:1.14
    commands:
    - mix local.hex --force
    - mix local.rebar --force
    - mix format --check-formatted
  build:
    image: akkoma/ci-base:1.14
    <<: *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
  credo:
    <<: *on-pr-open
    image: akkoma/ci-base:1.14
    commands:
    - mix local.hex --force
    - mix local.rebar --force
    - mix credo || true # we don't want to error here
  test:
    image: akkoma/ci-base:1.14
    <<: *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
  ubuntu22:
    image: hexpm/elixir:1.14.2-erlang-25.1.2-ubuntu-jammy-20220428
    <<: *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-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.14.2-erlang-25.1.2-debian-bullseye-20221004
    <<: *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:
    image: akkoma/releaser
    <<: *on-release
    secrets: *scw-secrets
    commands:
      - export SOURCE=akkoma-amd64.zip
      - export DEST=scaleway:akkoma-updates/$${CI_COMMIT_TAG:-"$CI_COMMIT_BRANCH"}/akkoma-amd64.zip
      - /bin/sh /entrypoint.sh
      - 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.14.2-erlang-25.1.2-alpine-3.16.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-amd64-musl.zip -r release
  release-musl:
    image: akkoma/releaser
    <<: *on-stable
    secrets: *scw-secrets
    commands:
      - 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-amd64.yml
+++ b/.woodpecker/build-amd64.yml
@ -1,117 +0,0 @@
 platform: linux/amd64
 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:
        - develop
        - stable
  - &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"
 pipeline:
  # Canonical amd64
  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-amd64.zip -r release
  release-debian-bookworm:
    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
      - /bin/sh /entrypoint.sh
  # Canonical amd64-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-amd64-musl.zip -r release
  release-musl:
    image: akkoma/releaser
    <<: *on-stable
    secrets: *scw-secrets
    commands:
      - 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
--- a/.woodpecker/build-arm64.yml
+++ b/.woodpecker/build-arm64.yml
@ -1,89 +0,0 @@
 platform: linux/arm64
 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"
 pipeline:
  # 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,69 +0,0 @@
 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"
 pipeline:
  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,55 +0,0 @@
 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"
 pipeline:
  lint:
    image: akkoma/ci-base:1.15-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,93 +0,0 @@
 platform: linux/amd64
 depends_on:
  - lint
 matrix:
  ELIXIR_VERSION:
    - 1.14
    - 1.15
  OTP_VERSION:
    - 25
    - 26
  include:
    - ELIXIR_VERSION: 1.14
      OTP_VERSION: 25
    - ELIXIR_VERSION: 1.15
      OTP_VERSION: 25
    - ELIXIR_VERSION: 1.15
      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
 pipeline:
  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 --preload-modules --only mocked
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@ -6,152 +6,15 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 ## Unreleased
 ## Added
 - Full compatibility with Erlang OTP26
 - handling of GET /api/v1/preferences
 ## Changed
 - OTP builds are now built on erlang OTP26
 - The base Phoenix framework is now updated to 1.7
 ## Fixed
 - Documentation issue in which a non-existing nginx file was referenced
 - Issue where a bad inbox URL could break federation
 ## 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
--- a/2
+++ b/2
@ -1,4 +1,4 @@
-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
--- a/7
+++ b/7
@ -0,0 +1,7 @@
 all:	install
 	pipenv run mkdocs build
 install:
 	pipenv install
 clean:
 	rm -rf docs
--- 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/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
@ -65,6 +65,7 @@
  link_name: false,
  proxy_remote: false,
  filename_display_max_length: 30,
  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, []}}
       ]}
    ]
  ],
@ -156,10 +171,6 @@
  "application/ld+json" => ["activity+json"]
 }
 config :mime, :extensions, %{
  "activity+json" => "application/activity+json"
 }
 config :tesla, :adapter, {Tesla.Adapter.Finch, name: MyFinch}
 # Configures http settings, upstream proxy etc.
@ -168,7 +179,6 @@
  receive_timeout: :timer.seconds(15),
  proxy_url: nil,
  user_agent: :default,
  pool_size: 50,
  adapter: []
 config :pleroma, :instance,
@ -249,9 +259,7 @@
  profile_directory: true,
  privileged_staff: false,
  local_bubble: [],
-  max_frontend_settings_json_chars: 100_000,
+  max_frontend_settings_json_chars: 100_000
  export_prometheus_metrics: true,
  federated_timeline_available: true
 config :pleroma, :welcome,
  direct_message: [
@ -344,7 +352,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,
@ -408,8 +416,6 @@
 config :pleroma, :mrf_follow_bot, follower_nickname: nil
 config :pleroma, :mrf_reject_newly_created_account_notes, age: 86_400
 config :pleroma, :rich_media,
  enabled: true,
  ignore_hosts: [],
@ -418,7 +424,7 @@
    Pleroma.Web.RichMedia.Parsers.TwitterCard,
    Pleroma.Web.RichMedia.Parsers.OEmbed
  ],
-  failure_backoff: :timer.minutes(20),
+  failure_backoff: 60_000,
  ttl_setters: [Pleroma.Web.RichMedia.Parser.TTL.AwsSignedUrl]
 config :pleroma, :media_proxy,
@ -433,8 +439,7 @@
    # Note: max_read_duration defaults to Pleroma.ReverseProxy.max_read_duration_default/1
    max_read_duration: 30_000
  ],
-  whitelist: [],
+  whitelist: []
  blocklist: []
 config :pleroma, Pleroma.Web.MediaProxy.Invalidation.Http,
  method: :purge,
@ -738,9 +743,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",
@ -779,6 +781,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",
@ -806,7 +816,7 @@
 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?}
@ -878,11 +888,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
@ -790,7 +790,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,
@ -964,17 +964,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."
      }
    ]
  },
@ -1081,7 +1070,7 @@
        key: :level,
        type: {:dropdown, :atom},
        description: "Log level",
-        suggestions: [:debug, :info, :warning, :error]
+        suggestions: [:debug, :info, :warn, :error]
      },
      %{
        key: :ident,
@ -1114,7 +1103,7 @@
        key: :level,
        type: {:dropdown, :atom},
        description: "Log level",
-        suggestions: [:debug, :info, :warning, :error]
+        suggestions: [:debug, :info, :warn, :error]
      },
      %{
        key: :format,
@ -1558,21 +1547,7 @@
      %{
        key: :whitelist,
        type: {:list, :string},
-        description: """
+        description: "List of hosts with scheme to bypass the MediaProxy",
        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.
        """,
        suggestions: ["http://example.com"]
      }
    ]
@ -1858,7 +1833,7 @@
        key: :log,
        type: {:dropdown, :atom},
        description: "Logs verbose mode",
-        suggestions: [false, :error, :warning, :info, :debug]
+        suggestions: [false, :error, :warn, :info, :debug]
      },
      %{
        key: :queues,
@ -2681,12 +2656,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. Default 50.",
        suggestions: [50]
      },
      %{
        key: :adapter,
        type: :keyword,
@ -3013,11 +2982,6 @@
            key: :federated,
            type: :boolean,
            description: "Disallow viewing the whole known network timeline."
          },
          %{
            key: :bubble,
            type: :boolean,
            description: "Disallow viewing the bubble timeline."
          }
        ]
      },
@ -3173,12 +3137,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."
      }
    ]
  },
@ -3473,32 +3431,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/test.exs
+++ b/config/test.exs
@ -16,14 +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,
  filters: [],
-  link_name: false
+  link_name: false,
  default_description: :filename
 config :pleroma, Pleroma.Uploaders.Local, uploads: "test/uploads"
@ -81,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,
--- 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) 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) db
--- 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/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
+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.
 # 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
-# Optionally use a virtual environment
+### Example using a Debian based distro
 python3 -m venv venv
 source venv/bin/activate
-# Install dependencies
+#### 1. Install pipenv and dependencies
 pip install -r requirements.txt
-# Run an http server who rebuilds when files change
+```shell
-# Accessable on http://127.0.0.1:8000
+pip install pipenv
-mkdocs serve
+pipenv sync
 # 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
 ```
 #### 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.
+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.
 !!! 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).
 !!! 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,11 +45,7 @@ This will prune remote posts older than 90 days (configurable with [`config :ple
    ```
 ### Options
-
+- `--vacuum` - run `VACUUM FULL` after the objects are pruned
 - `--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.
 - `--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.
 ## Create a conversation for all existing DMs
@ -99,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.**
@ -187,4 +178,4 @@ to the current day.
    ```sh
    mix pleroma.database prune_task
-    ```
+    ```
--- 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/robots_txt.md
+++ b/docs/docs/administration/CLI_tasks/robots_txt.md
@ -11,11 +11,11 @@ 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"
    ```sh
-    mix pleroma.robotstxt disallow_all
+    mix pleroma.robots_txt disallow_all
    ```
--- a/docs/docs/administration/backup.md
+++ b/docs/docs/administration/backup.md
@ -21,15 +21,33 @@
 6. Restore the database schema and akkoma role using either of the following options
    * You can use the original `setup_db.psql` if you have it[²]: `sudo -Hu postgres psql -f config/setup_db.psql`.
    * Or recreate the database and user yourself (replace the password with the one you find in the config file) `sudo -Hu postgres psql -c "CREATE USER akkoma WITH ENCRYPTED PASSWORD '<database-password-wich-you-can-find-in-your-config-file>'; 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>`
+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 `MIX_ENV=prod mix ecto.migrate`[³]. This task performs database migrations, if there were any.
+8. If you installed a newer Akkoma version, you should run `MIX_ENV=prod mix ecto.migrate`[⁴]. 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/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 config files.  
 [²]: You can recreate the `config/setup_db.psql` by running 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 backed up config file. This will also create a new `config/generated_config.exs` file which you may delete as it is not needed.  
-[³]: Prefix with `MIX_ENV=prod` to run it using the production config file.  
+[³]: `pg_restore` will add data before adding indexes. The indexes are added in alphabetical order. There's one index, `activities_visibility_index` which may take a long time because it can't make use of an index that's only added later. You can significantly speed up restoration by skipping this index and add it afterwards. For that, you can do the following (we assume the akkoma.pgdump is in the directory you're running the commands):  
 ```sh
 pg_restore -l akkoma.pgdump > db.list
 # Comment out the step for creating activities_visibility_index by adding a semi colon at the start of the line
 sed -i -E 's/(.*activities_visibility_index.*)/;\1/' db.list
 # We restore the database using the db.list list-file
 sudo -Hu postgres pg_restore -L db.list -d akkoma -v -1 akkoma.pgdump
 # You can see the sql statement with which to create the index using
 grep -Eao 'CREATE INDEX activities_visibility_index.*' akkoma.pgdump
 # Then create the index manually
 # Make sure that the command to create is correct! You never know it has changed since writing this guide
 sudo -Hu postgres psql -d pleroma_ynh -c "CREATE INDEX activities_visibility_index ON public.activities USING btree (public.activity_visibility(actor, recipients, data), id DESC NULLS LAST) WHERE ((data ->> 'type'::text) = 'Create'::text);"
 ```
 [⁴]: Prefix with `MIX_ENV=prod` to run it using the production config file.  
 ## Remove
--- a/docs/docs/administration/monitoring.md
+++ b/docs/docs/administration/monitoring.md
@ -1,33 +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 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
 ```
--- a/docs/docs/administration/updating.md
+++ b/docs/docs/administration/updating.md
@ -1,6 +1,6 @@
 # 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
@ -26,11 +26,11 @@ su -s "$SHELL" 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
 # Start akkoma
 ./bin/pleroma daemon # or using the system service manager (e.g. systemctl start akkoma)
 ```
 If you selected an alternate flavour on installation, 
@ -41,10 +41,8 @@ you _may_ need to specify `--flavour`, in the same way as
 Run as the `akkoma` user:
 ```sh
-# fetch changes
+# Pull in new changes
-git fetch
+git pull
 # check out the latest tag
 git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1)
 # Run with production configuration
 export MIX_ENV=prod
@ -59,9 +57,9 @@ sudo systemctl stop akkoma
 # Run database migrations
 mix ecto.migrate
 # Update frontend(s). See Frontend Configration doc for more information.
 mix pleroma.frontend install pleroma-fe --ref stable
 # 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
 ```
--- a/docs/docs/clients.md
+++ b/docs/docs/clients.md
@ -2,14 +2,6 @@
 Note: Additional clients may work, but these are known to work with Akkoma.
 Apps listed here might not support all of Akkoma's features.
 ## Multiplatform
 ### Kaiteki
 - Homepage: <https://kaiteki.app/>
 - Source Code: <https://github.com/Kaiteki-Fedi/Kaiteki>
 - Contact: [@kaiteki@fedi.software](https://fedi.software/@Kaiteki)
 - Platforms: Web, Windows, Linux, Android
 - Features: MastoAPI, Supports multiple backends
 ## Desktop
 ### Whalebird
 - Homepage: <https://whalebird.social/>
@ -33,7 +25,7 @@ Apps listed here might not support all of Akkoma's features.
 - 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
@ -53,10 +45,10 @@ Apps listed here might not support all of Akkoma's features.
 ## Alternative Web Interfaces
 ### Pinafore
 - Note: Pinafore is unmaintained (See [the author's original article](https://nolanlawson.com/2023/01/09/retiring-pinafore/) for details)
 - 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
@ -62,7 +62,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.
 ## :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).
@ -246,11 +245,11 @@ Notes:
 ### :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,
@ -562,6 +561,7 @@ the source code is here: [kocaptcha](https://github.com/koto-bank/kocaptcha). Th
 * `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`.
@ -615,12 +615,6 @@ This filter only strips the GPS and location metadata with Exiftool leaving colo
 No specific configuration.
 #### Pleroma.Upload.Filter.OnlyMedia
 This filter rejects uploads that are not identified with Content-Type matching audio/\*, image/\*, or video/\*
 No specific configuration.
 #### Pleroma.Upload.Filter.Mogrify
 * `args`: List of actions for the `mogrify` command like `"strip"` or `["strip", "auto-orient", {"implode", "1"}]`.
@ -1124,7 +1118,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`)
@ -1133,7 +1127,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`
@ -1145,9 +1139,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
--- 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
@ -70,4 +70,4 @@ config :pleroma, :frontend_configurations,
  }
 ```
-If you added it in the back-end configuration file, you'll need to restart your instance for the changes to take effect. If you don't see the changes, it's probably because the browser has cached the previous theme. In that case you'll want to clear browser caches. Alternatively you can use a private/incognito window just to see the changes.
+If you added it in the back-end configuration file, you'll need to restart your instance for the changes to take effect. If you don't see the changes, it's probably because the browser has cached the previous theme. In that case you'll want to clear browser caches. Alternatively you can use a private/incognito window just to see the changes.
--- a/docs/docs/configuration/postgresql.md
+++ b/docs/docs/configuration/postgresql.md
@ -6,31 +6,6 @@ Akkoma performance is largely dependent on performance of the underlying databas
 [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.
 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. In the end, PGTune only provides recomended settings, you can always try to finetune further.
 ### 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
 ```
 ## Disable generic query plans
 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.
@ -48,3 +23,26 @@ config :pleroma, Pleroma.Repo,
 ```
 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/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](../../../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;
 ```
    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_http_version 1.1;
-        proxy_cache_lock   on;
+        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
+Add to your `prod.secret.exs`:
 If you're using static file configuration, add the `MediaProxyWarmingPolicy` to your MRF policies. For example:
 ```
 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`
--- a/docs/docs/development/API/differences_in_mastoapi_responses.md
+++ b/docs/docs/development/API/differences_in_mastoapi_responses.md
@ -25,7 +25,6 @@ Home, public, hashtag & list timelines accept these parameters:
 ## 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:
@ -37,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"]}`.
+- `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.
  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.
 - `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.
@ -217,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,
+config :prometheus, Pleroma.Web.Endpoint.MetricsExporter,
-  export_prometheus_metrics: true
+  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/index.md
+++ b/docs/docs/development/index.md
@ -1,48 +1 @@
-# Contributing to Akkoma
+This section contains notes and guidelines for developers.
 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`.
--- a/docs/docs/development/setting_up_akkoma_dev.md
+++ b/docs/docs/development/setting_up_akkoma_dev.md
@ -5,37 +5,22 @@ 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.
+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 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"}
 ```
 Example config to change the scheme to http. Change the port if you want to run on another port.
 ```elixir
-config :pleroma, Pleroma.Web.Endpoint,
+  config :pleroma, Pleroma.Web.Endpoint,
-  url: [host: "localhost", scheme: "http", port: 4000],
+   url: [host: "localhost", scheme: "http", port: 4000],
 ```
 Example config to disable captcha. This makes it a bit easier to create test-users.
@ -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/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
+### Pleroma-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/).
+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}
--- 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}
--- 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}
--- 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
@ -65,9 +65,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 +84,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,8 +125,8 @@ cp docker-resources/Caddyfile.example docker-resources/Caddyfile
 Then edit the TLD in your caddyfile to the domain you're serving on.
-Uncomment the `caddy` section in the docker compose file,
+Uncomment the `caddy` section in the docker-compose file,
-then run `docker compose up -d` again.
+then run `docker-compose up -d` again.
 #### Running a reverse proxy on the host
@ -152,7 +152,7 @@ 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
 ```
 #### Further reading
--- 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}
--- a/docs/docs/installation/generic_dependencies.include
+++ b/docs/docs/installation/generic_dependencies.include
@ -1,8 +1,8 @@
 ## Required dependencies
 * PostgreSQL 9.6+
-* Elixir 1.14+
+* Elixir 1.12+ (1.13+ recommended)
-* Erlang OTP 24+
+* Erlang OTP 22.2+
 * git
 * file / libmagic
 * gcc (clang might also work)
--- a/docs/docs/installation/migrating_to_akkoma.md
+++ b/docs/docs/installation/migrating_to_akkoma.md
@ -117,16 +117,4 @@ To fix this, run:
    mix pleroma.config delete pleroma frontends
    ```
-which will remove the config from the database. Things should work now.
+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.
--- 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 --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 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,10 +12,11 @@ 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 elixir gmake git postgresql-server postgresql-contrib cmake ffmpeg ImageMagick erlang-wx-25
 pkg_add erlang-wx # Choose the latest version as package version when promted
 ```
 (Note that the erlang version may change, it was 25 at the time of writing)
 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.
 #### Optional software
@ -28,35 +29,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
+Start a shell as the \_postgresql user (as root run `su _postgresql -` then run the `initdb` command to initialize postgresql:
-directory for user `_postgresql` run `usermod -d  /var/postgresql/data _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 +70,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 +93,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 +108,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 +129,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 +140,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 +198,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 +222,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,19 +1,19 @@
 # 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:
+For specific Pleroma functionality (which is disabled by default) some or all of the below packages are required:
-  * `ImageMagick`
+  * `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:
+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`)
@ -21,12 +21,12 @@ It is required for the following Akkoma features:
 `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:
+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,7 +5,7 @@
 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
@ -15,16 +15,16 @@ While in theory OTP releases are possbile to install on any compatible machine,
 ### 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  |
+| distribution  | flavour            | available branches  |
-| --------------- | ------------------ | ------------------- | ------------------- |
+| ------------- | ------------------ | ------------------- |
-| debian bookworm | amd64              | amd64               | develop, stable     |
+| debian stable | amd64              | develop, stable     |
-| debian bookworm | arm64              | arm64               | stable              |
+| ubuntu focal  | amd64              | develop, stable     |
-| ubuntu jammy    | amd64              | amd64               | develop, stable     |
+| ubuntu jammy  | amd64-ubuntu-jammy | develop, stable     |
-| ubuntu jammy    | arm64              | arm64               | develop, stable     |
+| alpine        | amd64-musl         | stable              |
 | alpine          | amd64              | amd64-musl          | stable              |
 | alpine          | arm64              | arm64-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="amd64-musl"
 export FLAVOUR="<replace-this-with-the-correct-flavour-string>"
 # Make sure the SHELL variable is set
 export SHELL="${SHELL:-/bin/sh}"
 # Clone the release build into a temporary directory and unpack it
 su akkoma -s $SHELL -lc "
@ -187,18 +183,18 @@ 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
--- 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:
@ -178,7 +178,7 @@ 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
--- 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/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_url = "https://git.pleroma.social/pleroma/pleroma" %}
-  {% set repo_name = "AkkomaGang/akkoma" %}
+  {% set repo_name = "pleroma/pleroma" %}
 {% elif page and page.url.startswith('frontend') %}
-  {% set repo_url = "https://akkoma.dev/AkkomaGang/akkoma-fe" %}
+  {% set repo_url = "https://git.pleroma.social/pleroma/pleroma-fe" %}
-  {% set repo_name = "AkkomaGang/akkoma-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
@ -1,2 +1,2 @@
-elixir_version=1.14.3
+elixir_version=1.9.4
-erlang_version=25.3
+erlang_version=22.3.4.1
--- a/installation/akkoma.service
+++ b/installation/akkoma.service
@ -7,9 +7,7 @@ ExecReload=/bin/kill $MAINPID
 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"
+; Evironment="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
@ -26,8 +24,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.
@ -38,8 +34,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/caddy/Caddyfile
+++ b/installation/caddy/Caddyfile
@ -4,9 +4,6 @@
 # 1. Replace 'example.tld' with your instance's domain wherever it appears.
 # 2. Copy this section into your Caddyfile and restart Caddy.
 # If you are able to, it's highly recommended to have your media served via a separate subdomain for improved security.
 # Uncomment the relevant sectons here and modify the base_url setting for Pleroma.Upload and :media_proxy accordingly.
 example.tld  {
  log {
    output file /var/log/caddy/akkoma.log
@ -17,21 +14,4 @@ example.tld  {
  # this is explicitly IPv4 since Pleroma.Web.Endpoint binds on IPv4 only
  # and `localhost.` resolves to [::0] on some systems: see issue #930
  reverse_proxy 127.0.0.1:4000
  # Uncomment if using a separate media subdomain
  #@mediaproxy path /media/* /proxy/*
  #handle @mediaproxy {
  #  redir https://media.example.tld{uri} permanent
  #}
 }
 # Uncomment if using a separate media subdomain
 #media.example.tld {
 #  @mediaproxy path /media/* /proxy/*
 #  reverse_proxy @mediaproxy 127.0.0.1:4000 {
 #    transport http {
 #      response_header_timeout 10s
 #      read_timeout 15s
 #    }
 #  }
 #}
--- a/installation/init.d/akkoma
+++ b/installation/init.d/akkoma
@ -8,7 +8,6 @@ pidfile="/var/run/akkoma.pid"
 directory=/opt/akkoma
 healthcheck_delay=60
 healthcheck_timer=30
 no_new_privs="yes"
 : ${akkoma_port:-4000}
--- a/installation/nginx/akkoma.nginx
+++ b/installation/nginx/akkoma.nginx
@ -54,6 +54,8 @@ server {
    ssl_protocols TLSv1.2 TLSv1.3;
    ssl_ciphers "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4";
    ssl_prefer_server_ciphers off;
    # In case of an old server with an OpenSSL version of 1.0.2 or below,
    # leave only prime256v1 or comment out the following line.
    ssl_ecdh_curve X25519:prime256v1:secp384r1:secp521r1;
    ssl_stapling on;
    ssl_stapling_verify on;
--- a/lib/mix/tasks/pleroma/config.ex
+++ b/lib/mix/tasks/pleroma/config.ex
@ -79,45 +79,6 @@ def run(["dump", group]) do
    end)
  end
  def run(["dump_to_file", group, key, fname]) do
    check_configdb(fn ->
      start_pleroma()
      group = maybe_atomize(group)
      key = maybe_atomize(key)
      config = ConfigDB.get_by_group_and_key(group, key)
      json =
        %{
          group: ConfigDB.to_json_types(config.group),
          key: ConfigDB.to_json_types(config.key),
          value: ConfigDB.to_json_types(config.value)
        }
        |> Jason.encode!()
        |> Jason.Formatter.pretty_print()
      File.write(fname, json)
      shell_info("Wrote #{group}_#{key}.json")
    end)
  end
  def run(["load_from_file", fname]) do
    check_configdb(fn ->
      start_pleroma()
      json = File.read!(fname)
      config = Jason.decode!(json)
      group = ConfigDB.to_elixir_types(config["group"])
      key = ConfigDB.to_elixir_types(config["key"])
      value = ConfigDB.to_elixir_types(config["value"])
      params = %{group: group, key: key, value: value}
      ConfigDB.update_or_create(params)
      shell_info("Loaded #{config["group"]}, #{config["key"]}")
    end)
  end
  def run(["groups"]) do
    check_configdb(fn ->
      start_pleroma()
--- a/lib/mix/tasks/pleroma/database.ex
+++ b/lib/mix/tasks/pleroma/database.ex
@ -67,168 +67,43 @@ def run(["prune_objects" | args]) do
      OptionParser.parse(
        args,
        strict: [
-          vacuum: :boolean,
+          vacuum: :boolean
          keep_threads: :boolean,
          keep_non_public: :boolean,
          prune_orphaned_activities: :boolean
        ]
      )
    start_pleroma()
    deadline = Pleroma.Config.get([:instance, :remote_post_retention_days])
    time_deadline = NaiveDateTime.utc_now() |> NaiveDateTime.add(-(deadline * 86_400))
-    log_message = "Pruning objects older than #{deadline} days"
+    Logger.info("Pruning objects older than #{deadline} days")
-    log_message =
+    time_deadline =
-      if Keyword.get(options, :keep_non_public) do
+      NaiveDateTime.utc_now()
-        log_message <> ", keeping non public posts"
+      |> NaiveDateTime.add(-(deadline * 86_400))
      else
        log_message
      end
-    log_message =
+    from(o in Object,
-      if Keyword.get(options, :keep_threads) do
+      where:
-        log_message <> ", keeping threads intact"
+        fragment(
-      else
+          "?->'to' \\? ? OR ?->'cc' \\? ?",
-        log_message
+          o.data,
-      end
+          ^Pleroma.Constants.as_public(),
-
+          o.data,
-    log_message =
+          ^Pleroma.Constants.as_public()
-      if Keyword.get(options, :prune_orphaned_activities) do
+        ),
-        log_message <> ", pruning orphaned activities"
+      where: o.inserted_at < ^time_deadline,
-      else
+      where:
        log_message
      end
    log_message =
      if Keyword.get(options, :vacuum) do
        log_message <>
          ", doing a full vacuum (you shouldn't do this as a recurring maintanance task)"
      else
        log_message
      end
    Logger.info(log_message)
    if Keyword.get(options, :keep_threads) do
      # We want to delete objects from threads where
      # 1. the newest post is still old
      # 2. none of the activities is local
      # 3. none of the activities is bookmarked
      # 4. optionally none of the posts is non-public
      deletable_context =
        if Keyword.get(options, :keep_non_public) do
          Pleroma.Activity
          |> join(:left, [a], b in Pleroma.Bookmark, on: a.id == b.activity_id)
          |> group_by([a], fragment("? ->> 'context'::text", a.data))
          |> having(
            [a],
            not fragment(
              # Posts (checked on Create Activity) is non-public
              "bool_or((not(?->'to' \\? ? OR ?->'cc' \\? ?)) and ? ->> 'type' = 'Create')",
              a.data,
              ^Pleroma.Constants.as_public(),
              a.data,
              ^Pleroma.Constants.as_public(),
              a.data
            )
          )
        else
          Pleroma.Activity
          |> join(:left, [a], b in Pleroma.Bookmark, on: a.id == b.activity_id)
          |> group_by([a], fragment("? ->> 'context'::text", a.data))
        end
        |> having([a], max(a.updated_at) < ^time_deadline)
        |> having([a], not fragment("bool_or(?)", a.local))
        |> having([_, b], fragment("max(?::text) is null", b.id))
        |> select([a], fragment("? ->> 'context'::text", a.data))
      Pleroma.Object
      |> where([o], fragment("? ->> 'context'::text", o.data) in subquery(deletable_context))
    else
      if Keyword.get(options, :keep_non_public) do
        Pleroma.Object
        |> where(
          [o],
          fragment(
            "?->'to' \\? ? OR ?->'cc' \\? ?",
            o.data,
            ^Pleroma.Constants.as_public(),
            o.data,
            ^Pleroma.Constants.as_public()
          )
        )
      else
        Pleroma.Object
      end
      |> where([o], o.updated_at < ^time_deadline)
      |> where(
        [o],
        fragment("split_part(?->>'actor', '/', 3) != ?", o.data, ^Pleroma.Web.Endpoint.host())
-      )
+    )
    end
    |> Repo.delete_all(timeout: :infinity)
-    if !Keyword.get(options, :keep_threads) do
+    prune_hashtags_query = """
      # Without the --keep-threads option, it's possible that bookmarked
      # objects have been deleted. We remove the corresponding bookmarks.
      """
      delete from public.bookmarks
      where id in (
        select b.id from public.bookmarks b
        left join public.activities a on b.activity_id = a.id
        left join public.objects o on a."data" ->> 'object' = o.data ->> 'id'
        where o.id is null
      )
      """
      |> Repo.query([], timeout: :infinity)
    end
    if Keyword.get(options, :prune_orphaned_activities) do
      # Prune activities who link to a single object
      """
      delete from public.activities
      where id in (
        select a.id from public.activities a
        left join public.objects o on a.data ->> 'object' = o.data ->> 'id'
        left join public.activities a2 on a.data ->> 'object' = a2.data ->> 'id'
        left join public.users u  on a.data ->> 'object' = u.ap_id
        where not a.local
        and jsonb_typeof(a."data" -> 'object') = 'string'
        and o.id is null
        and a2.id is null
        and u.id is null
      )
      """
      |> Repo.query([], timeout: :infinity)
      # Prune activities who link to an array of objects
      """
      delete from public.activities
      where id in (
        select a.id from public.activities a
        join json_array_elements_text((a."data" -> 'object')::json) as j on jsonb_typeof(a."data" -> 'object') = 'array'
        left join public.objects o on j.value = o.data ->> 'id'
        left join public.activities a2 on j.value = a2.data ->> 'id'
        left join public.users u  on j.value = u.ap_id
        group by a.id
        having max(o.data ->> 'id') is null
        and max(a2.data ->> 'id') is null
        and max(u.ap_id) is null
      )
      """
      |> Repo.query([], timeout: :infinity)
    end
    """
    DELETE FROM hashtags AS ht
    WHERE NOT EXISTS (
      SELECT 1 FROM hashtags_objects hto
      WHERE ht.id = hto.hashtag_id)
    """
-    |> Repo.query()
+
    Repo.query(prune_hashtags_query)
    if Keyword.get(options, :vacuum) do
      Maintenance.vacuum("full")
@ -359,7 +234,7 @@ def run(["set_text_search_config", tsconfig]) do
        )
      end
-      shell_info(~c"Done.")
+      shell_info('Done.')
    end
  end
--- a/lib/mix/tasks/pleroma/diagnostics.ex
+++ b/lib/mix/tasks/pleroma/diagnostics.ex
@ -82,46 +82,4 @@ def run(["user_timeline", nickname, reading_nickname]) do
    Ecto.Adapters.SQL.explain(Repo, :all, query, analyze: true, timeout: :infinity)
    |> IO.puts()
  end
  def run(["notifications", nickname]) do
    start_pleroma()
    user = Repo.get_by!(User, nickname: nickname)
    account_ap_id = user.ap_id
    options = %{account_ap_id: user.ap_id}
    query =
      user
      |> Pleroma.Notification.for_user_query(options)
      |> where([n, a], a.actor == ^account_ap_id)
      |> limit(20)
    Ecto.Adapters.SQL.explain(Repo, :all, query, analyze: true, timeout: :infinity)
    |> IO.puts()
  end
  def run(["known_network", nickname]) do
    start_pleroma()
    user = Repo.get_by!(User, nickname: nickname)
    params =
      %{}
      |> Map.put(:type, ["Create"])
      |> Map.put(:local_only, false)
      |> Map.put(:blocking_user, user)
      |> Map.put(:muting_user, user)
      |> Map.put(:reply_filtering_user, user)
      # Restricts unfederated content to authenticated users
      |> Map.put(:includes_local_public, not is_nil(user))
      |> Map.put(:restrict_unlisted, true)
    query =
      Pleroma.Web.ActivityPub.ActivityPub.fetch_activities_query(
        [Pleroma.Constants.as_public()],
        params
      )
      |> limit(20)
    Ecto.Adapters.SQL.explain(Repo, :all, query, analyze: true, timeout: :infinity)
    |> IO.puts()
  end
 end
--- a/lib/mix/tasks/pleroma/emoji.ex
+++ b/lib/mix/tasks/pleroma/emoji.ex
@ -130,7 +130,6 @@ def run(["get-packs" | args]) do
        }
        File.write!(Path.join(pack_path, "pack.json"), Jason.encode!(pack_json, pretty: true))
        Pleroma.Emoji.reload()
      else
        IO.puts(IO.ANSI.format([:bright, :red, "No pack named \"#{pack_name}\" found"]))
      end
@ -236,8 +235,6 @@ def run(["gen-pack" | args]) do
      IO.puts("#{pack_file} has been created with the #{name} pack")
    end
    Pleroma.Emoji.reload()
  end
  def run(["reload"]) do
--- a/lib/mix/tasks/pleroma/instance.ex
+++ b/lib/mix/tasks/pleroma/instance.ex
@ -247,22 +247,16 @@ def run(["gen" | rest]) do
      config_dir = Path.dirname(config_path)
      psql_dir = Path.dirname(psql_path)
      # Note: Distros requiring group read (0o750) on those directories should
      # pre-create the directories.
      to_create =
        [config_dir, psql_dir, static_dir, uploads_dir]
        |> Enum.reject(&File.exists?/1)
      for dir <- to_create do
        File.mkdir_p!(dir)
        File.chmod!(dir, 0o700)
      end
      shell_info("Writing config to #{config_path}.")
      # Sadly no fchmod(2) equivalent in Elixir…
      File.touch!(config_path)
      File.chmod!(config_path, 0o640)
      File.write(config_path, result_config)
      shell_info("Writing the postgres script to #{psql_path}.")
      File.write(psql_path, result_psql)
@ -281,7 +275,8 @@ def run(["gen" | rest]) do
    else
      shell_error(
        "The task would have overwritten the following files:\n" <>
-          Enum.map_join(will_overwrite, &"- #{&1}\n") <> "Rerun with `--force` to overwrite them."
+          (Enum.map(will_overwrite, &"- #{&1}\n") |> Enum.join("")) <>
          "Rerun with `--force` to overwrite them."
      )
    end
  end
--- a/lib/mix/tasks/pleroma/search/meilisearch.ex
+++ b/lib/mix/tasks/pleroma/search/meilisearch.ex
@ -30,12 +30,12 @@ def run(["index"]) do
      meili_put(
        "/indexes/objects/settings/ranking-rules",
        [
          "published:desc",
          "words",
          "exactness",
          "proximity",
          "typo",
          "exactness",
          "attribute",
          "published:desc",
          "sort"
        ]
      )
--- a/lib/mix/tasks/pleroma/user.ex
+++ b/lib/mix/tasks/pleroma/user.ex
@ -11,7 +11,6 @@ defmodule Mix.Tasks.Pleroma.User do
  alias Pleroma.UserInviteToken
  alias Pleroma.Web.ActivityPub.Builder
  alias Pleroma.Web.ActivityPub.Pipeline
  use Pleroma.Web, :verified_routes
  @shortdoc "Manages Pleroma users"
  @moduledoc File.read!("docs/docs/administration/CLI_tasks/user.md")
@ -114,7 +113,11 @@ def run(["reset_password", nickname]) do
         {:ok, token} <- Pleroma.PasswordResetToken.create_token(user) do
      shell_info("Generated password reset token for #{user.nickname}")
-      IO.puts("URL: #{~p[/api/v1/pleroma/password_reset/#{token.token}]}")
+      IO.puts(
        "URL: #{Pleroma.Web.Router.Helpers.reset_password_url(Pleroma.Web.Endpoint,
        :reset,
        token.token)}"
      )
    else
      _ ->
        shell_error("No local user #{nickname}")
@ -300,7 +303,13 @@ def run(["invite" | rest]) do
         {:ok, invite} <- UserInviteToken.create_invite(options) do
      shell_info("Generated user invite token " <> String.replace(invite.invite_type, "_", " "))
-      url = url(~p[/registration/#{invite.token}])
+      url =
        Pleroma.Web.Router.Helpers.redirect_url(
          Pleroma.Web.Endpoint,
          :registration_page,
          invite.token
        )
      IO.puts(url)
    else
      error ->
--- a/lib/phoenix/transports/web_socket/raw.ex
+++ b/lib/phoenix/transports/web_socket/raw.ex
@ -26,6 +26,7 @@ def init(%Plug.Conn{method: "GET"} = conn, {endpoint, handler, transport}) do
      conn
      |> fetch_query_params
      |> Transport.transport_log(opts[:transport_log])
      |> Transport.force_ssl(handler, endpoint, opts)
      |> Transport.check_origin(handler, endpoint, opts)
    case conn do
--- a/lib/pleroma/activity.ex
+++ b/lib/pleroma/activity.ex
@ -277,13 +277,6 @@ def get_create_by_object_ap_id_with_object(ap_id) when is_binary(ap_id) do
  def get_create_by_object_ap_id_with_object(_), do: nil
  def get_local_create_by_object_ap_id(ap_id) when is_binary(ap_id) do
    ap_id
    |> create_by_object_ap_id()
    |> where(local: true)
    |> Repo.one()
  end
  @spec create_by_id_with_object(String.t()) :: t() | nil
  def create_by_id_with_object(id) do
    get_by_id_with_opts(id, preload: [:object], filter: [type: "Create"])
@ -390,8 +383,7 @@ def restrict_deactivated_users(query) do
      active in fragment(
        "SELECT is_active from users WHERE ap_id = ? AND is_active = TRUE",
        activity.actor
-      ),
+      )
      on: true
    )
  end
--- a/lib/pleroma/activity/ir/topics.ex
+++ b/lib/pleroma/activity/ir/topics.ex
@ -21,7 +21,7 @@ defp generate_topics(object, activity) do
    ["user", "list"] ++ visibility_tags(object, activity)
  end
-  defp visibility_tags(object, %{data: %{"type" => type}} = activity) when type != "Announce" do
+  defp visibility_tags(object, activity) do
    case Visibility.get_visibility(activity) do
      "public" ->
        if activity.local do
@ -31,10 +31,6 @@ defp visibility_tags(object, %{data: %{"type" => type}} = activity) when type !=
        end
        |> item_creation_tags(object, activity)
      "local" ->
        ["public:local"]
        |> item_creation_tags(object, activity)
      "direct" ->
        ["direct"]
@ -43,10 +39,6 @@ defp visibility_tags(object, %{data: %{"type" => type}} = activity) when type !=
    end
  end
  defp visibility_tags(_object, _activity) do
    []
  end
  defp item_creation_tags(tags, object, %{data: %{"type" => "Create"}} = activity) do
    tags ++
      remote_topics(activity) ++ hashtags_to_topics(object) ++ attachment_topics(object, activity)
@ -71,18 +63,7 @@ defp remote_topics(_), do: []
  defp attachment_topics(%{data: %{"attachment" => []}}, _act), do: []
-  defp attachment_topics(_object, %{local: true} = activity) do
+  defp attachment_topics(_object, %{local: true}), do: ["public:media", "public:local:media"]
    case Visibility.get_visibility(activity) do
      "public" ->
        ["public:media", "public:local:media"]
      "local" ->
        ["public:local:media"]
      _ ->
        []
    end
  end
  defp attachment_topics(_object, %{actor: actor}) when is_binary(actor),
    do: ["public:media", "public:remote:media:" <> URI.parse(actor).host]
--- a/lib/pleroma/akkoma/translators/argos_translate.ex
+++ b/lib/pleroma/akkoma/translators/argos_translate.ex
@ -1,109 +0,0 @@
 defmodule Pleroma.Akkoma.Translators.ArgosTranslate do
  @behaviour Pleroma.Akkoma.Translator
  alias Pleroma.Config
  defp argos_translate do
    Config.get([:argos_translate, :command_argos_translate])
  end
  defp argospm do
    Config.get([:argos_translate, :command_argospm])
  end
  defp strip_html? do
    Config.get([:argos_translate, :strip_html])
  end
  defp safe_languages() do
    try do
      System.cmd(argospm(), ["list"], stderr_to_stdout: true, parallelism: true)
    rescue
      _ -> {"Command #{argospm()} not found", 1}
    end
  end
  @impl Pleroma.Akkoma.Translator
  def languages do
    with {response, 0} <- safe_languages() do
      langs =
        response
        |> String.split("\n", trim: true)
        |> Enum.map(fn
          "translate-" <> l -> String.split(l, "_")
        end)
      source_langs =
        langs
        |> Enum.map(fn [l, _] -> %{code: l, name: l} end)
        |> Enum.uniq()
      dest_langs =
        langs
        |> Enum.map(fn [_, l] -> %{code: l, name: l} end)
        |> Enum.uniq()
      {:ok, source_langs, dest_langs}
    else
      {response, _} -> {:error, "ArgosTranslate failed to fetch languages (#{response})"}
    end
  end
  defp safe_translate(string, from_language, to_language) do
    try do
      System.cmd(
        argos_translate(),
        ["--from-lang", from_language, "--to-lang", to_language, string],
        stderr_to_stdout: true,
        parallelism: true
      )
    rescue
      _ -> {"Command #{argos_translate()} not found", 1}
    end
  end
  defp clean_string(string, true) do
    string
    |> String.replace("<p>", "\n")
    |> String.replace("</p>", "\n")
    |> String.replace("<br>", "\n")
    |> String.replace("<br/>", "\n")
    |> String.replace("<li>", "\n")
    |> Pleroma.HTML.strip_tags()
    |> HtmlEntities.decode()
  end
  defp clean_string(string, _), do: string
  defp htmlify_response(string, true) do
    string
    |> HtmlEntities.encode()
    |> String.replace("\n", "<br/>")
  end
  defp htmlify_response(string, _), do: string
  @impl Pleroma.Akkoma.Translator
  def translate(string, nil, to_language) do
    # Akkoma's Pleroma-fe expects us to detect the source language automatically.
    # Argos-translate doesn't have that option (yet?)
    #     see <https://github.com/argosopentech/argos-translate/issues/9>
    # For now we return the text unchanged, supposedly translated from the target language.
    # Afterwards people get the option to overwrite the source language from a dropdown.
    {:ok, to_language, string}
  end
  def translate(string, from_language, to_language) do
    # Argos Translate doesn't properly translate HTML (yet?)
    # For now we give admins the option to strip the html before translating
    # Note that we have to add some html back to the response afterwards
    string = clean_string(string, strip_html?())
    with {translated, 0} <-
           safe_translate(string, from_language, to_language) do
      {:ok, from_language, translated |> htmlify_response(strip_html?())}
    else
      {response, _} -> {:error, "ArgosTranslate failed to translate (#{response})"}
    end
  end
 end
--- a/lib/pleroma/akkoma/translators/libre_translate.ex
+++ b/lib/pleroma/akkoma/translators/libre_translate.ex
@ -40,7 +40,7 @@ def translate(string, from_language, to_language) do
        if Map.has_key?(body, "detectedLanguage") do
          get_in(body, ["detectedLanguage", "language"])
        else
-          from_language || ""
+          from_language
        end
      {:ok, detected, translated}
--- a/lib/pleroma/application.ex
+++ b/lib/pleroma/application.ex
@ -53,7 +53,6 @@ def start(_type, _args) do
    Config.DeprecationWarnings.warn()
    Pleroma.Web.Plugs.HTTPSecurityPlug.warn_if_disabled()
    Pleroma.ApplicationRequirements.verify!()
    load_all_pleroma_modules()
    load_custom_modules()
    Pleroma.Docs.JSON.compile()
    limiters_setup()
@ -74,8 +73,7 @@ def start(_type, _args) do
          Pleroma.JobQueueMonitor,
          {Majic.Pool, [name: Pleroma.MajicPool, pool_size: Config.get([:majic_pool, :size], 2)]},
          {Oban, Config.get(Oban)},
-          Pleroma.Web.Endpoint,
+          Pleroma.Web.Endpoint
          Pleroma.Web.Telemetry
        ] ++
        elasticsearch_children() ++
        task_children(@mix_env) ++
@ -88,7 +86,7 @@ def start(_type, _args) do
    # Go for the default 3 unless we're in test
    max_restarts =
      if @mix_env == :test do
-        1000
+        100
      else
        3
      end
@ -113,7 +111,7 @@ defp set_postgres_server_version do
        num
      else
        e ->
-          Logger.warning(
+          Logger.warn(
            "Could not get the postgres version: #{inspect(e)}.\nSetting the default value of 9.6"
          )
@ -145,24 +143,6 @@ def load_custom_modules do
    end
  end
  def load_all_pleroma_modules do
    :code.all_available()
    |> Enum.filter(fn {mod, _, _} ->
      mod
      |> to_string()
      |> String.starts_with?("Elixir.Pleroma.")
    end)
    |> Enum.map(fn {mod, _, _} ->
      mod
      |> to_string()
      |> String.to_existing_atom()
      |> Code.ensure_loaded!()
    end)
    # Use this when 1.15 is standard
    # |> Code.ensure_all_loaded!()
  end
  defp cachex_children do
    [
      build_cachex("used_captcha", ttl_interval: seconds_valid_interval()),
@ -178,8 +158,7 @@ defp cachex_children do
      build_cachex("banned_urls", default_ttl: :timer.hours(24 * 30), limit: 5_000),
      build_cachex("translations", default_ttl: :timer.hours(24 * 30), limit: 2500),
      build_cachex("instances", default_ttl: :timer.hours(24), ttl_interval: 1000, limit: 2500),
-      build_cachex("request_signatures", default_ttl: :timer.hours(24 * 30), limit: 3000),
+      build_cachex("request_signatures", default_ttl: :timer.hours(24 * 30), limit: 3000)
      build_cachex("rel_me", default_ttl: :timer.hours(24 * 30), limit: 300)
    ]
  end
@ -279,14 +258,10 @@ def limiters_setup do
  defp http_children do
    proxy_url = Config.get([:http, :proxy_url])
    proxy = Pleroma.HTTP.AdapterHelper.format_proxy(proxy_url)
    pool_size = Config.get([:http, :pool_size])
    :public_key.cacerts_load()
    config =
      [:http, :adapter]
      |> Config.get([])
      |> Pleroma.HTTP.AdapterHelper.add_pool_size(pool_size)
      |> Pleroma.HTTP.AdapterHelper.maybe_add_proxy_pool(proxy)
      |> Keyword.put(:name, MyFinch)
--- a/lib/pleroma/application_requirements.ex
+++ b/lib/pleroma/application_requirements.ex
@ -34,7 +34,7 @@ defp handle_result({:error, message}), do: raise(VerifyError, message: message)
  defp check_welcome_message_config!(:ok) do
    if Pleroma.Config.get([:welcome, :email, :enabled], false) and
         not Pleroma.Emails.Mailer.enabled?() do
-      Logger.warning("""
+      Logger.warn("""
      To send welcome emails, you need to enable the mailer.
      Welcome emails will NOT be sent with the current config.
@ -53,7 +53,7 @@ defp check_welcome_message_config!(result), do: result
  def check_confirmation_accounts!(:ok) do
    if Pleroma.Config.get([:instance, :account_activation_required]) &&
         not Pleroma.Emails.Mailer.enabled?() do
-      Logger.warning("""
+      Logger.warn("""
      Account activation is required, but the mailer is disabled.
      Users will NOT be able to confirm their accounts with this config.
      Either disable account activation or enable the mailer.
--- a/lib/pleroma/config/deprecation_warnings.ex
+++ b/lib/pleroma/config/deprecation_warnings.ex
@ -28,7 +28,7 @@ def check_simple_policy_tuples do
      |> Enum.any?(fn {_, v} -> is_list(v) and Enum.any?(v, &is_binary/1) end)
    if has_strings do
-      Logger.warning("""
+      Logger.warn("""
      !!!DEPRECATION WARNING!!!
      Your config is using strings in the SimplePolicy configuration instead of tuples. They should work for now, but you are advised to change to the new configuration to prevent possible issues later:
@ -87,7 +87,7 @@ def check_quarantined_instances_tuples do
    has_strings = Config.get([:instance, :quarantined_instances], []) |> Enum.any?(&is_binary/1)
    if has_strings do
-      Logger.warning("""
+      Logger.warn("""
      !!!DEPRECATION WARNING!!!
      Your config is using strings in the quarantined_instances configuration instead of tuples. They should work for now, but you are advised to change to the new configuration to prevent possible issues later:
@ -124,7 +124,7 @@ def check_transparency_exclusions_tuples do
    has_strings = Config.get([:mrf, :transparency_exclusions]) |> Enum.any?(&is_binary/1)
    if has_strings do
-      Logger.warning("""
+      Logger.warn("""
      !!!DEPRECATION WARNING!!!
      Your config is using strings in the transparency_exclusions configuration instead of tuples. They should work for now, but you are advised to change to the new configuration to prevent possible issues later:
@ -159,7 +159,7 @@ def check_transparency_exclusions_tuples do
  def check_hellthread_threshold do
    if Config.get([:mrf_hellthread, :threshold]) do
-      Logger.warning("""
+      Logger.warn("""
      !!!DEPRECATION WARNING!!!
      You are using the old configuration mechanism for the hellthread filter. Please check config.md.
      """)
@ -264,7 +264,7 @@ def move_namespace_and_warn(config_map, warning_preface) do
    if warning == "" do
      :ok
    else
-      Logger.warning(warning_preface <> warning)
+      Logger.warn(warning_preface <> warning)
      :error
    end
  end
@ -274,7 +274,7 @@ def check_media_proxy_whitelist_config do
    whitelist = Config.get([:media_proxy, :whitelist])
    if Enum.any?(whitelist, &(not String.starts_with?(&1, "http"))) do
-      Logger.warning("""
+      Logger.warn("""
      !!!DEPRECATION WARNING!!!
      Your config is using old format (only domain) for MediaProxy whitelist option. Setting should work for now, but you are advised to change format to scheme with port to prevent possible issues later.
      """)
--- a/lib/pleroma/config/oban.ex
+++ b/lib/pleroma/config/oban.ex
@ -23,7 +23,7 @@ def warn do
          You are using old workers in Oban crontab settings, which were removed.
          Please, remove setting from crontab in your config file (prod.secret.exs): #{inspect(setting)}
          """
-          |> Logger.warning()
+          |> Logger.warn()
          List.delete(acc, setting)
        else
--- a/lib/pleroma/config/release_runtime_provider.ex
+++ b/lib/pleroma/config/release_runtime_provider.ex
@ -22,20 +22,6 @@ def load(config, opts) do
    with_runtime_config =
      if File.exists?(config_path) do
        # <https://git.pleroma.social/pleroma/pleroma/-/issues/3135>
        %File.Stat{mode: mode} = File.lstat!(config_path)
        if Bitwise.band(mode, 0o007) > 0 do
          raise "Configuration at #{config_path} has world-permissions, execute the following: chmod o= #{config_path}"
        end
        if Bitwise.band(mode, 0o020) > 0 do
          raise "Configuration at #{config_path} has group-wise write permissions, execute the following: chmod g-w #{config_path}"
        end
        # Note: Elixir doesn't provides a getuid(2)
        # so cannot forbid group-read only when config is owned by us
        runtime_config = Config.Reader.read!(config_path)
        with_defaults
--- a/lib/pleroma/config/transfer_task.ex
+++ b/lib/pleroma/config/transfer_task.ex
@ -25,9 +25,7 @@ defp reboot_time_subkeys,
    do: [
      {:pleroma, Pleroma.Captcha, [:seconds_valid]},
      {:pleroma, Pleroma.Upload, [:proxy_remote]},
-      {:pleroma, :instance, [:upload_limit]},
+      {:pleroma, :instance, [:upload_limit]}
      {:pleroma, :http, [:pool_size]},
      {:pleroma, :http, [:proxy_url]}
    ]
  def start_link(restart_pleroma? \\ true) do
@ -42,7 +40,6 @@ def load_and_update_env(deleted_settings \\ [], restart_pleroma? \\ true) do
      # We need to restart applications for loaded settings take effect
      {logger, other} =
        (Repo.all(ConfigDB) ++ deleted_settings)
        |> Enum.reject(&invalid_key_or_group/1)
        |> Enum.map(&merge_with_default/1)
        |> Enum.split_with(fn {group, _, _, _} -> group == :logger end)
@ -86,10 +83,6 @@ defp maybe_set_pleroma_last(apps) do
    end
  end
  defp invalid_key_or_group(%ConfigDB{key: :invalid_atom}), do: true
  defp invalid_key_or_group(%ConfigDB{group: :invalid_atom}), do: true
  defp invalid_key_or_group(_), do: false
  defp merge_with_default(%{group: group, key: key, value: value} = setting) do
    default =
      if group == :pleroma do
@ -110,7 +103,7 @@ defp merge_with_default(%{group: group, key: key, value: value} = setting) do
  defp configure({_, :backends, _, merged}) do
    # removing current backends
-    Enum.each(Application.get_env(:logger, :backends, []), &Logger.remove_backend/1)
+    Enum.each(Application.get_env(:logger, :backends), &Logger.remove_backend/1)
    Enum.each(merged, &Logger.add_backend/1)
@ -149,7 +142,7 @@ defp update({group, key, value, merged}) do
        error_msg =
          "updating env causes error, group: #{inspect(group)}, key: #{inspect(key)}, value: #{inspect(value)} error: #{inspect(error)}"
-        Logger.warning(error_msg)
+        Logger.warn(error_msg)
        nil
    end
@ -183,12 +176,12 @@ defp restart(started_applications, app, _) do
      :ok = Application.start(app)
    else
      nil ->
-        Logger.warning("#{app} is not started.")
+        Logger.warn("#{app} is not started.")
      error ->
        error
        |> inspect()
-        |> Logger.warning()
+        |> Logger.warn()
    end
  end
--- a/lib/pleroma/config_db.ex
+++ b/lib/pleroma/config_db.ex
@ -342,11 +342,7 @@ def string_to_elixir_types(":" <> atom), do: String.to_atom(atom)
  def string_to_elixir_types(value) do
    if module_name?(value) do
-      try do
+      String.to_existing_atom("Elixir." <> value)
        String.to_existing_atom("Elixir." <> value)
      rescue
        ArgumentError -> :invalid_atom
      end
    else
      value
    end
--- a/lib/pleroma/constants.ex
+++ b/lib/pleroma/constants.ex
@ -25,7 +25,7 @@ defmodule Pleroma.Constants do
  const(static_only_files,
    do:
-      ~w(index.html robots.txt static static-fe finmoji emoji packs sounds images instance embed sw.js sw-pleroma.js favicon.png schemas doc)
+      ~w(index.html robots.txt static static-fe finmoji emoji packs sounds images instance sw.js sw-pleroma.js favicon.png schemas doc embed.js embed.css)
  )
  const(status_updatable_fields,
@ -38,8 +38,7 @@ defmodule Pleroma.Constants do
      "summary",
      "sensitive",
      "attachment",
-      "generator",
+      "generator"
      "contentMap"
    ]
  )
--- a/lib/pleroma/emails/admin_email.ex
+++ b/lib/pleroma/emails/admin_email.ex
@ -6,13 +6,10 @@ defmodule Pleroma.Emails.AdminEmail do
  @moduledoc "Admin emails"
  import Swoosh.Email
-  use Pleroma.Web, :mailer
+
  alias Pleroma.Config
  alias Pleroma.HTML
-
+  alias Pleroma.Web.Router.Helpers
  use Phoenix.VerifiedRoutes,
    endpoint: Pleroma.Web.Endpoint,
    router: Pleroma.Web.Router
  defp instance_config, do: Config.get(:instance)
  defp instance_name, do: instance_config()[:name]
@ -48,7 +45,7 @@ def report(to, reporter, account, statuses, comment) do
          statuses
          |> Enum.map(fn
            %{id: id} ->
-              status_url = url(~p[/notice/#{id}])
+              status_url = Helpers.o_status_url(Pleroma.Web.Endpoint, :notice, id)
              "<li><a href=\"#{status_url}\">#{status_url}</li>"
            %{"id" => id} when is_binary(id) ->
--- a/lib/pleroma/emails/user_email.ex
+++ b/lib/pleroma/emails/user_email.ex
@ -6,11 +6,12 @@ defmodule Pleroma.Emails.UserEmail do
  @moduledoc "User emails"
  require Pleroma.Web.Gettext
  use Pleroma.Web, :mailer
  alias Pleroma.Config
  alias Pleroma.User
  alias Pleroma.Web.Endpoint
  alias Pleroma.Web.Gettext
  alias Pleroma.Web.Router
  import Swoosh.Email
  import Phoenix.Swoosh, except: [render_body: 3]
@ -74,7 +75,7 @@ def welcome(user, opts \\ %{}) do
  def password_reset_email(user, token) when is_binary(token) do
    Gettext.with_locale_or_default user.language do
-      password_reset_url = ~p[/api/v1/pleroma/password_reset/#{token}]
+      password_reset_url = Router.Helpers.reset_password_url(Endpoint, :reset, token)
      html_body =
        Gettext.dpgettext(
@ -107,7 +108,12 @@ def user_invitation_email(
        to_name \\ nil
      ) do
    Gettext.with_locale_or_default user.language do
-      registration_url = ~p[/registration/#{user_invite_token.token}]
+      registration_url =
        Router.Helpers.redirect_url(
          Endpoint,
          :registration_page,
          user_invite_token.token
        )
      html_body =
        Gettext.dpgettext(
@ -115,7 +121,7 @@ def user_invitation_email(
          "user invitation email body",
          """
          <h3>You are invited to %{instance_name}</h3>
-          <p>%{inviter_name} invites you to join %{instance_name}, an instance of Akkoma federated social networking platform.</p>
+          <p>%{inviter_name} invites you to join %{instance_name}, an instance of Pleroma federated social networking platform.</p>
          <p>Click the following link to register: <a href="%{registration_url}">accept invitation</a>.</p>
          """,
          instance_name: instance_name(),
@ -140,7 +146,13 @@ def user_invitation_email(
  def account_confirmation_email(user) do
    Gettext.with_locale_or_default user.language do
-      confirmation_url = ~p[/api/account/confirm_email/#{user.id}/#{user.confirmation_token}]
+      confirmation_url =
        Router.Helpers.confirm_email_url(
          Endpoint,
          :confirm_email,
          user.id,
          to_string(user.confirmation_token)
        )
      html_body =
        Gettext.dpgettext(
@ -330,7 +342,7 @@ def unsubscribe_url(user, notifications_type) do
      |> Pleroma.JWT.generate_and_sign!()
      |> Base.encode64()
-    ~p[/mailer/unsubscribe/#{token}]
+    Router.Helpers.subscription_url(Endpoint, :unsubscribe, token)
  end
  def backup_is_ready_email(backup, admin_user_id \\ nil) do
@ -345,7 +357,7 @@ def backup_is_ready_email(backup, admin_user_id \\ nil) do
            "static_pages",
            "account archive email body - self-requested",
            """
-            <p>You requested a full backup of your Akkoma account. It's ready for download:</p>
+            <p>You requested a full backup of your Pleroma account. It's ready for download:</p>
            <p><a href="%{download_url}">%{download_url}</a></p>
            """,
            download_url: download_url
@ -357,7 +369,7 @@ def backup_is_ready_email(backup, admin_user_id \\ nil) do
            "static_pages",
            "account archive email body - admin requested",
            """
-            <p>Admin @%{admin_nickname} requested a full backup of your Akkoma account. It's ready for download:</p>
+            <p>Admin @%{admin_nickname} requested a full backup of your Pleroma account. It's ready for download:</p>
            <p><a href="%{download_url}">%{download_url}</a></p>
            """,
            admin_nickname: admin.nickname,
--- a/lib/pleroma/emoji.ex
+++ b/lib/pleroma/emoji.ex
@ -21,7 +21,6 @@ defmodule Pleroma.Emoji do
    :named_table,
    {:read_concurrency, true}
  ]
  @emoji_regex ~r/:[A-Za-z0-9_-]+(@.+)?:/
  defstruct [:code, :file, :tags, :safe_code, :safe_file]
@ -206,7 +205,4 @@ def fully_qualify_emoji(unquote(unqualified)), do: unquote(qualified)
  end
  def fully_qualify_emoji(emoji), do: emoji
  def matches_shortcode?(nil), do: false
  def matches_shortcode?(s), do: Regex.match?(@emoji_regex, s)
 end
--- a/lib/pleroma/emoji/loader.ex
+++ b/lib/pleroma/emoji/loader.ex
@ -59,7 +59,7 @@ def load do
          Logger.info("Found emoji packs: #{Enum.join(packs, ", ")}")
          if not Enum.empty?(files) do
-            Logger.warning(
+            Logger.warn(
              "Found files in the emoji folder. These will be ignored, please move them to a subdirectory\nFound files: #{Enum.join(files, ", ")}"
            )
          end
--- a/lib/pleroma/emoji/pack.ex
+++ b/lib/pleroma/emoji/pack.ex
@ -252,7 +252,7 @@ def download(name, url, as) do
    with :ok <- validate_shareable_packs_available(uri),
         {:ok, remote_pack} <-
-           uri |> URI.merge("/api/v1/pleroma/emoji/pack?name=#{URI.encode(name)}") |> http_get(),
+           uri |> URI.merge("/api/v1/pleroma/emoji/pack?name=#{name}") |> http_get(),
         {:ok, %{sha: sha, url: url} = pack_info} <- fetch_pack_info(remote_pack, uri, name),
         {:ok, archive} <- download_archive(url, sha),
         pack <- copy_as(remote_pack, as || name),
@ -287,7 +287,6 @@ def update_metadata(name, data) do
  @spec load_pack(String.t()) :: {:ok, t()} | {:error, :file.posix()}
  def load_pack(name) do
    name = Path.basename(name)
    pack_file = Path.join([emoji_path(), name, "pack.json"])
    with {:ok, _} <- File.stat(pack_file),
@ -412,10 +411,10 @@ defp downloadable?(pack) do
  end
  defp create_archive_and_cache(pack, hash) do
-    files = [~c"pack.json" | Enum.map(pack.files, fn {_, file} -> to_charlist(file) end)]
+    files = ['pack.json' | Enum.map(pack.files, fn {_, file} -> to_charlist(file) end)]
    {:ok, {_, result}} =
-      :zip.zip(~c"#{pack.name}.zip", files, [:memory, cwd: to_charlist(pack.path)])
+      :zip.zip('#{pack.name}.zip', files, [:memory, cwd: to_charlist(pack.path)])
    ttl_per_file = Pleroma.Config.get!([:emoji, :shared_pack_cache_seconds_per_file])
    overall_ttl = :timer.seconds(ttl_per_file * Enum.count(files))
@ -582,7 +581,7 @@ defp unzip(archive, pack_info, remote_pack, local_pack) do
    with :ok <- File.mkdir_p!(local_pack.path) do
      files = Enum.map(remote_pack["files"], fn {_, path} -> to_charlist(path) end)
      # Fallback cannot contain a pack.json file
-      files = if pack_info[:fallback], do: files, else: [~c"pack.json" | files]
+      files = if pack_info[:fallback], do: files, else: ['pack.json' | files]
      :zip.unzip(archive, cwd: to_charlist(local_pack.path), file_list: files)
    end
@ -594,9 +593,7 @@ defp fetch_pack_info(remote_pack, uri, name) do
        {:ok,
         %{
           sha: sha,
-           url:
+           url: URI.merge(uri, "/api/v1/pleroma/emoji/packs/archive?name=#{name}") |> to_string()
             URI.merge(uri, "/api/v1/pleroma/emoji/packs/archive?name=#{URI.encode(name)}")
             |> to_string()
         }}
      %{"fallback-src" => src, "fallback-src-sha256" => sha} when is_binary(src) ->
--- a/lib/pleroma/following_relationship.ex
+++ b/lib/pleroma/following_relationship.ex
@ -155,13 +155,14 @@ def following_count(%User{} = user) do
    |> Repo.aggregate(:count, :id)
  end
-  def get_follow_requests_query(%User{id: id}) do
+  def get_follow_requests(%User{id: id}) do
    __MODULE__
-    |> join(:inner, [r], f in assoc(r, :follower), as: :follower)
+    |> join(:inner, [r], f in assoc(r, :follower))
    |> where([r], r.state == ^:follow_pending)
    |> where([r], r.following_id == ^id)
-    |> where([r, follower: f], f.is_active == true)
+    |> where([r, f], f.is_active == true)
-    |> select([r, follower: f], f)
+    |> select([r, f], f)
    |> Repo.all()
  end
  def following?(%User{id: follower_id}, %User{id: followed_id}) do
--- a/lib/pleroma/formatter.ex
+++ b/lib/pleroma/formatter.ex
@ -124,8 +124,8 @@ def mentions_escape(text, options \\ []) do
    end
  end
-  def markdown_to_html(text, opts \\ %{}) do
+  def markdown_to_html(text) do
-    Earmark.as_html!(text, %Earmark.Options{compact_output: true} |> Map.merge(opts))
+    Earmark.as_html!(text, %Earmark.Options{compact_output: true})
  end
  def html_escape({text, mentions, hashtags}, type) do
--- a/lib/pleroma/http.ex
+++ b/lib/pleroma/http.ex
@ -27,10 +27,10 @@ defmodule Pleroma.HTTP do
          nil | {:ok, Env.t()} | {:error, any()}
  def get(url, headers \\ [], options \\ [])
  def get(nil, _, _), do: nil
-  def get(url, headers, options), do: request(:get, url, nil, headers, options)
+  def get(url, headers, options), do: request(:get, url, "", headers, options)
  @spec head(Request.url(), Request.headers(), keyword()) :: {:ok, Env.t()} | {:error, any()}
-  def head(url, headers \\ [], options \\ []), do: request(:head, url, nil, headers, options)
+  def head(url, headers \\ [], options \\ []), do: request(:head, url, "", headers, options)
  @doc """
  Performs POST request.
@ -62,17 +62,10 @@ def request(method, url, body, headers, options) when is_binary(url) do
    uri = URI.parse(url)
    adapter_opts = AdapterHelper.options(uri, options || [])
    adapter_opts =
      if uri.scheme == :https do
        AdapterHelper.maybe_add_cacerts(adapter_opts, :public_key.cacerts_get())
      else
        adapter_opts
      end
    options = put_in(options[:adapter], adapter_opts)
    params = options[:params] || []
    request = build_request(method, headers, options, url, body, params)
-    client = Tesla.client([Tesla.Middleware.FollowRedirects, Tesla.Middleware.Telemetry])
+    client = Tesla.client([Tesla.Middleware.FollowRedirects])
    request(client, request)
  end
--- a/lib/pleroma/http/adapter_helper.ex
+++ b/lib/pleroma/http/adapter_helper.ex
@ -47,24 +47,6 @@ def maybe_add_proxy_pool(opts, proxy) do
    |> put_in([:pools, :default, :conn_opts, :proxy], proxy)
  end
  def maybe_add_cacerts(opts, nil), do: opts
  def maybe_add_cacerts(opts, cacerts) do
    opts
    |> maybe_add_pools()
    |> maybe_add_default_pool()
    |> maybe_add_conn_opts()
    |> maybe_add_transport_opts()
    |> put_in([:pools, :default, :conn_opts, :transport_opts, :cacerts], cacerts)
  end
  def add_pool_size(opts, pool_size) do
    opts
    |> maybe_add_pools()
    |> maybe_add_default_pool()
    |> put_in([:pools, :default, :size], pool_size)
  end
  defp maybe_add_pools(opts) do
    if Keyword.has_key?(opts, :pools) do
      opts
@ -93,16 +75,6 @@ defp maybe_add_conn_opts(opts) do
    end
  end
  defp maybe_add_transport_opts(opts) do
    transport_opts = get_in(opts, [:pools, :default, :conn_opts, :transport_opts])
    unless is_nil(transport_opts) do
      opts
    else
      put_in(opts, [:pools, :default, :conn_opts, :transport_opts], [])
    end
  end
  @doc """
  Merge default connection & adapter options with received ones.
  """
@ -131,7 +103,7 @@ def parse_proxy(proxy) when is_binary(proxy) do
      {:ok, type, uri.host, uri.port}
    else
      e ->
-        Logger.warning("Parsing proxy failed #{inspect(proxy)}, #{inspect(e)}")
+        Logger.warn("Parsing proxy failed #{inspect(proxy)}, #{inspect(e)}")
        {:error, :invalid_proxy}
    end
  end
@ -141,7 +113,7 @@ def parse_proxy(proxy) when is_tuple(proxy) do
      {:ok, type, host, port}
    else
      _ ->
-        Logger.warning("Parsing proxy failed #{inspect(proxy)}")
+        Logger.warn("Parsing proxy failed #{inspect(proxy)}")
        {:error, :invalid_proxy}
    end
  end
--- a/lib/pleroma/instances/instance.ex
+++ b/lib/pleroma/instances/instance.ex
@ -162,7 +162,7 @@ def local do
    %Instance{
      host: Pleroma.Web.Endpoint.host(),
      favicon: Pleroma.Web.Endpoint.url() <> "/favicon.png",
-      nodeinfo: Pleroma.Web.Nodeinfo.Nodeinfo.get_nodeinfo("2.1")
+      nodeinfo: Pleroma.Web.Nodeinfo.NodeinfoController.raw_nodeinfo()
    }
  end
--- a/lib/pleroma/iso639.ex
+++ b/lib/pleroma/iso639.ex
@ -1,11 +0,0 @@
 defmodule Pleroma.ISO639 do
  @file "priv/language-codes.json"
  @data File.read!(@file)
        |> Jason.decode!()
  for %{"alpha2" => alpha2} <- @data do
    def valid_alpha2?(unquote(alpha2)), do: true
  end
  def valid_alpha2?(_alpha2), do: false
 end
--- a/lib/pleroma/maintenance.ex
+++ b/lib/pleroma/maintenance.ex
@ -20,7 +20,7 @@ def vacuum(args) do
      "full" ->
        Logger.info("Running VACUUM FULL.")
-        Logger.warning(
+        Logger.warn(
          "Re-packing your entire database may take a while and will consume extra disk space during the process."
        )
--- a/lib/pleroma/migrators/support/base_migrator.ex
+++ b/lib/pleroma/migrators/support/base_migrator.ex
@ -73,7 +73,7 @@ def handle_continue(:init_state, _state) do
          data_migration.state == :manual or data_migration.name in manual_migrations ->
            message = "Data migration is in manual execution or manual fix mode."
            update_status(:manual, message)
-            Logger.warning("#{__MODULE__}: #{message}")
+            Logger.warn("#{__MODULE__}: #{message}")
          data_migration.state == :complete ->
            on_complete(data_migration)
@ -109,7 +109,7 @@ def handle_info(:perform, state) do
            Putting data migration to manual fix mode. Try running `#{__MODULE__}.retry_failed/0`.
            """
-            Logger.warning("#{__MODULE__}: #{message}")
+            Logger.warn("#{__MODULE__}: #{message}")
            update_status(:manual, message)
            on_complete(data_migration())
@ -125,7 +125,7 @@ def handle_info(:perform, state) do
      defp on_complete(data_migration) do
        if data_migration.feature_lock || feature_state() == :disabled do
-          Logger.warning(
+          Logger.warn(
            "#{__MODULE__}: migration complete but feature is locked; consider enabling."
          )
--- a/lib/pleroma/notification.ex
+++ b/lib/pleroma/notification.ex
@ -195,7 +195,6 @@ defp exclude_filtered(query, user) do
        from([_n, a, o] in query,
          where:
            fragment("not(?->>'content' ~* ?)", o.data, ^regex) or
              fragment("?->>'content' is null", o.data) or
              fragment("?->>'actor' = ?", o.data, ^user.ap_id)
        )
    end
@ -696,7 +695,7 @@ def skip?(
    cond do
      opts[:type] == "poll" -> false
      user.ap_id == actor -> false
-      !User.following?(user, follower) -> true
+      !User.following?(follower, user) -> true
      true -> false
    end
  end
--- a/lib/pleroma/object/fetcher.ex
+++ b/lib/pleroma/object/fetcher.ex
@ -117,8 +117,6 @@ def refetch_object(%Object{data: %{"id" => id}} = object) do
  # Note: will create a Create activity, which we need internally at the moment.
  def fetch_object_from_id(id, options \\ []) do
    with %URI{} = uri <- URI.parse(id),
         # let's check the URI is even vaguely valid first
         {:scheme, true} <- {:scheme, uri.scheme == "http" or uri.scheme == "https"},
         # If we have instance restrictions, apply them here to prevent fetching from unwanted instances
         {:ok, nil} <- Pleroma.Web.ActivityPub.MRF.SimplePolicy.check_reject(uri),
         {:ok, _} <- Pleroma.Web.ActivityPub.MRF.SimplePolicy.check_accept(uri),
@ -137,9 +135,6 @@ def fetch_object_from_id(id, options \\ []) do
      {:allowed_depth, false} ->
        {:error, "Max thread distance exceeded."}
      {:scheme, false} ->
        {:error, "URI Scheme Invalid"}
      {:containment, _} ->
        {:error, "Object containment failed."}
--- a/lib/pleroma/object/updater.ex
+++ b/lib/pleroma/object/updater.ex
@ -129,10 +129,7 @@ def make_update_object_data(original_data, new_data, date) do
    else
      %{updated_object: updated_data} =
        updated_data
-        |> maybe_update_history(original_data,
+        |> maybe_update_history(original_data, updated: updated, use_history_in_new_object?: false)
          updated: updated,
          use_history_in_new_object?: false
        )
      updated_data
      |> Map.put("updated", date)
--- a/lib/pleroma/pagination.ex
+++ b/lib/pleroma/pagination.ex
@ -88,9 +88,9 @@ def paginate(query, options, :offset, table_binding) do
  defp cast_params(params) do
    param_types = %{
-      min_id: params[:id_type] || :string,
+      min_id: :string,
-      since_id: params[:id_type] || :string,
+      since_id: :string,
-      max_id: params[:id_type] || :string,
+      max_id: :string,
      offset: :integer,
      limit: :integer,
      skip_extra_order: :boolean,
--- a/lib/pleroma/password.ex
+++ b/lib/pleroma/password.ex
@ -1,55 +0,0 @@
 defmodule Pleroma.Password do
  @moduledoc """
  This module handles password hashing and verification.
  It will delegate to the appropriate module based on the password hash.
  It also handles upgrading of password hashes.
  """
  alias Pleroma.User
  alias Pleroma.Password.Pbkdf2
  require Logger
  @hashing_module Argon2
  @spec hash_pwd_salt(String.t()) :: String.t()
  defdelegate hash_pwd_salt(pass), to: @hashing_module
  @spec checkpw(String.t(), String.t()) :: boolean()
  def checkpw(password, "$2" <> _ = password_hash) do
    # Handle bcrypt passwords for Mastodon migration
    Bcrypt.verify_pass(password, password_hash)
  end
  def checkpw(password, "$pbkdf2" <> _ = password_hash) do
    Pbkdf2.verify_pass(password, password_hash)
  end
  def checkpw(password, "$argon2" <> _ = password_hash) do
    Argon2.verify_pass(password, password_hash)
  end
  def checkpw(_password, _password_hash) do
    Logger.error("Password hash not recognized")
    false
  end
  @spec maybe_update_password(User.t(), String.t()) ::
          {:ok, User.t()} | {:error, Ecto.Changeset.t()}
  def maybe_update_password(%User{password_hash: "$2" <> _} = user, password) do
    do_update_password(user, password)
  end
  def maybe_update_password(%User{password_hash: "$6" <> _} = user, password) do
    do_update_password(user, password)
  end
  def maybe_update_password(%User{password_hash: "$pbkdf2" <> _} = user, password) do
    do_update_password(user, password)
  end
  def maybe_update_password(user, _), do: {:ok, user}
  defp do_update_password(user, password) do
    User.reset_password(user, %{password: password, password_confirmation: password})
  end
 end
--- a/lib/pleroma/prometheus_exporter.ex
+++ b/lib/pleroma/prometheus_exporter.ex
@ -1,49 +0,0 @@
 defmodule Pleroma.PrometheusExporter do
  @moduledoc """
  Exports metrics in Prometheus format.
  Mostly exists because of https://github.com/beam-telemetry/telemetry_metrics_prometheus_core/issues/52
  Basically we need to fetch metrics every so often, or the lib will let them pile up and eventually crash the VM.
  It also sorta acts as a cache so there is that too.
  """
  use GenServer
  require Logger
  def start_link(_opts) do
    GenServer.start_link(__MODULE__, :ok, name: __MODULE__)
  end
  def init(_opts) do
    schedule_next()
    {:ok, ""}
  end
  defp schedule_next do
    Process.send_after(self(), :gather, 60_000)
  end
  # Scheduled function, gather metrics and schedule next run
  def handle_info(:gather, _state) do
    schedule_next()
    state = TelemetryMetricsPrometheus.Core.scrape()
    {:noreply, state}
  end
  # Trigger the call dynamically, mostly for testing
  def handle_call(:gather, _from, _state) do
    state = TelemetryMetricsPrometheus.Core.scrape()
    {:reply, state, state}
  end
  def handle_call(:show, _from, state) do
    {:reply, state, state}
  end
  def show do
    GenServer.call(__MODULE__, :show)
  end
  def gather do
    GenServer.call(__MODULE__, :gather)
  end
 end
--- a/Show more
+++ b/Show more
		`@ -1,2 +0,0 @@`
			`hehe, /emoji/hehe.png, Akkoma`
			`nothehe, /emoji/nothehe.png, Akkoma`
`@ -1,3 +1,3 @@`
	`#!/bin/sh`	`#!/bin/sh`

	`docker compose run --rm akkoma $@`	`docker-compose run --rm akkoma $@`
`@ -1,2 +1,2 @@`
	`elixir_version=1.14.3`	`elixir_version=1.9.4`
	`erlang_version=25.3`	`erlang_version=22.3.4.1`