.credo.exs

@@ -25,7 +25,7 @@
       #
       # If you create your own checks, you must specify the source files for
       # them here, so they can be loaded by Credo before running the analysis.
-      requires: ["./test/credo/check/consistency/file_location.ex"],
+      requires: [],
       #
       # Credo automatically checks for updates, like e.g. Hex does.
       # You can disable this behaviour below:
@@ -71,6 +71,7 @@
         # set this value to 0 (zero).
         {Credo.Check.Design.TagTODO, exit_status: 0},
         {Credo.Check.Design.TagFIXME, exit_status: 0},
+
         {Credo.Check.Readability.FunctionNames},
         {Credo.Check.Readability.LargeNumbers},
         {Credo.Check.Readability.MaxLineLength, priority: :low, max_length: 100},
@@ -83,7 +84,6 @@
         # lanodan: I think PreferImplicitTry should be consistency, and the behaviour seems
         # inconsistent, see: https://github.com/rrrene/credo/issues/224
         {Credo.Check.Readability.PreferImplicitTry, false},
-        {Credo.Check.Readability.PipeIntoAnonymousFunctions, exit_status: 0},
         {Credo.Check.Readability.RedundantBlankLines},
         {Credo.Check.Readability.StringSigils},
         {Credo.Check.Readability.TrailingBlankLine},
@@ -91,7 +91,7 @@
         {Credo.Check.Readability.VariableNames},
         {Credo.Check.Readability.Semicolons},
         {Credo.Check.Readability.SpaceAfterCommas},
-        {Credo.Check.Readability.WithSingleClause, exit_status: 0},
+
         {Credo.Check.Refactor.DoubleBooleanNegation},
         {Credo.Check.Refactor.CondStatements},
         {Credo.Check.Refactor.CyclomaticComplexity},
@@ -102,6 +102,7 @@
         {Credo.Check.Refactor.Nesting},
         {Credo.Check.Refactor.PipeChainStart},
         {Credo.Check.Refactor.UnlessWithElse},
+
         {Credo.Check.Warning.BoolOperationOnSameValues},
         {Credo.Check.Warning.IExPry},
         {Credo.Check.Warning.IoInspect},
@@ -130,7 +131,6 @@
 
         # Custom checks can be created using `mix credo.gen.check`.
         #
-        {Credo.Check.Consistency.FileLocation}
       ]
     }
   ]

.dialyzer_ignore.exs

@@ -1,9 +0,0 @@
-[
-{"lib/cachex.ex", "Unknown type: Spec.cache/0."},
-{"lib/pleroma/web/plugs/rate_limiter.ex", "The pattern can never match the type {:commit, _} | {:ignore, _}."},
-{"lib/pleroma/web/plugs/rate_limiter.ex", "Function get_scale/2 will never be called."},
-{"lib/pleroma/web/plugs/rate_limiter.ex", "Function initialize_buckets!/1 will never be called."},
-{"lib/pleroma/workers/receiver_worker.ex", :call},
-{"lib/pleroma/workers/receiver_worker.ex", :pattern_match},
-{"lib/pleroma/workers/receiver_worker.ex", :pattern_match_cov},
-]

.formatter.exs

@@ -1,3 +1,3 @@
 [
-  inputs: ["mix.exs", "{config,lib,test}/**/*.{ex,exs}", "priv/repo/migrations/*.exs", "priv/repo/optional_migrations/**/*.exs", "priv/scrubbers/*.ex"]
+  inputs: ["mix.exs", "{config,lib,test}/**/*.{ex,exs}", "priv/repo/migrations/*.exs", "priv/scrubbers/*.ex"]
 ]

.gitattributes

@@ -1,10 +1,2 @@
 *.ex diff=elixir
 *.exs diff=elixir
-
-priv/static/instance/static.css diff=css
-
-# Most of js/css files included in the repo are minified bundles,
-#   and we don't want to search/diff those as text files.
-*.js binary
-*.js.map binary
-*.css binary

.gitignore

@@ -3,10 +3,9 @@
 /db
 /deps
 /*.ez
-/test/instance
 /test/uploads
 /.elixir_ls
-/test/fixtures/DSCN0010_tmp*
+/test/fixtures/DSCN0010_tmp.jpg
 /test/fixtures/test_tmp.txt
 /test/fixtures/image_tmp.jpg
 /test/tmp/
@@ -28,12 +27,9 @@ erl_crash.dump
 # variables.
 /config/*.secret.exs
 /config/generated_config.exs
-/config/runtime.exs
-/config/*.env
-
 
 # Database setup file, some may forget to delete it
-/config/setup_db*.psql
+/config/setup_db.psql
 
 .DS_Store
 .env
@@ -48,21 +44,9 @@ docs/generated_config.md
 # Code test coverage
 /cover
 /Elixir.*.coverdata
-/coverage.xml
 
 .idea
 pleroma.iml
 
 # asdf
 .tool-versions
-
-# Editor temp files
-*~
-*#
-*.swp
-
-archive-*
-.gitlab-ci-local
-
-# Test files should be named *.exs
-test/pleroma/**/*.ex

.gitlab-ci.yml

@@ -1,203 +1,118 @@
-image: git.pleroma.social:5050/pleroma/pleroma/ci-base:elixir-1.14.5-otp-25
+image: elixir:1.9.4
 
 variables: &global_variables
-  # Only used for the release
-  ELIXIR_VER: 1.17.3
   POSTGRES_DB: pleroma_test
   POSTGRES_USER: postgres
   POSTGRES_PASSWORD: postgres
   DB_HOST: postgres
-  DB_PORT: "5432"
   MIX_ENV: test
-  GIT_STRATEGY: fetch
-
-workflow:
-  rules:
-    - if: $CI_PIPELINE_SOURCE == "merge_request_event"
-    - if: $CI_COMMIT_BRANCH && $CI_OPEN_MERGE_REQUESTS
-      when: never
-    - if: $CI_COMMIT_BRANCH
 
 cache: &global_cache_policy
-  key: $CI_JOB_IMAGE-$CI_COMMIT_SHORT_SHA
+  key: ${CI_COMMIT_REF_SLUG}
   paths:
     - deps
     - _build
 
 stages:
   - build
-  - lint
   - test
-  - check-changelog
   - benchmark
   - deploy
   - release
   - docker
-  - docker-combine
 
 before_script:
-  - echo $MIX_ENV
-  - rm -rf _build/*/lib/pleroma
+  - apt-get update && apt-get install -y cmake
+  - mix local.hex --force
+  - mix local.rebar --force
+
+build:
+  stage: build
+  script:
   - mix deps.get
-
-after_script:
-  - rm -rf _build/*/lib/pleroma
-
-check-changelog:
-  stage: check-changelog
-  image: alpine
-  rules:
-    - if: $CI_MERGE_REQUEST_SOURCE_PROJECT_PATH == 'pleroma/pleroma' && $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME == 'weblate-extract'
-      when: never
-    - if: $CI_MERGE_REQUEST_SOURCE_PROJECT_PATH == 'pleroma/pleroma' && $CI_MERGE_REQUEST_SOURCE_BRANCH_NAME == 'weblate'
-      when: never
-    - if: $CI_MERGE_REQUEST_TARGET_BRANCH_NAME == "develop"
-  before_script: ''
-  after_script: ''
-  cache: {}
-  script:
-    - apk add git
-    - sh ./tools/check-changelog
-
-.build_changes_policy:
-  rules:
-    - changes:
-        - ".gitlab-ci.yml"
-        - "**/*.ex"
-        - "**/*.exs"
-        - "mix.lock"
-
-.using-ci-base:
-  tags:
-    - amd64
-
-build-1.14.5-otp-25:
-  extends:
-  - .build_changes_policy
-  - .using-ci-base
-  stage: build
-  script:
   - mix compile --force
 
-build-1.17.1-otp-26:
-  extends:
-  - .build_changes_policy
-  - .using-ci-base
-  stage: build
-  image: git.pleroma.social:5050/pleroma/pleroma/ci-base:elixir-1.17.1-otp-26
-  script:
-  - mix compile --force
-
-spec-build:
-  extends:
-  - .using-ci-base
-  stage: build
-  rules:
-    - changes:
-        - ".gitlab-ci.yml"
-        - "lib/pleroma/web/api_spec/**/*.ex"
-        - "lib/pleroma/web/api_spec.ex"
-  artifacts:
-    paths:
-    - spec.json
-  script:
-  - mix pleroma.openapi_spec spec.json
-
 benchmark:
-  extends:
-  - .using-ci-base
   stage: benchmark
   when: manual
   variables:
     MIX_ENV: benchmark
   services:
-  - name: postgres:11.22-alpine
+  - name: postgres:9.6
     alias: postgres
     command: ["postgres", "-c", "fsync=off", "-c", "synchronous_commit=off", "-c", "full_page_writes=off"]
   script:
+    - mix deps.get
     - mix ecto.create
     - mix ecto.migrate
     - mix pleroma.load_testing
 
-unit-testing-1.14.5-otp-25:
-  extends:
-  - .build_changes_policy
-  - .using-ci-base
+unit-testing:
   stage: test
+  retry: 2
   cache: &testing_cache_policy
     <<: *global_cache_policy
     policy: pull
-  services: &testing_services
-  - name: postgres:13-alpine
+
+  services:
+  - name: postgres:9.6
     alias: postgres
     command: ["postgres", "-c", "fsync=off", "-c", "synchronous_commit=off", "-c", "full_page_writes=off"]
-  script: &testing_script
+  script:
+    - apt-get update && apt-get install -y libimage-exiftool-perl
+    - mix deps.get
     - mix ecto.create
     - mix ecto.migrate
-    - mix pleroma.test_runner --cover --preload-modules
-  coverage: '/^Line total: ([^ ]*%)$/'
-  artifacts:
-    reports:
-      coverage_report:
-        coverage_format: cobertura
-        path: coverage.xml
+    - mix coveralls --preload-modules
 
-unit-testing-1.17.1-otp-26:
-  extends:
-  - .build_changes_policy
-  - .using-ci-base
+# Removed to fix CI issue. In this early state it wasn't adding much value anyway.
+# TODO Fix and reinstate federated testing
+# federated-testing:
+#   stage: test
+#   cache: *testing_cache_policy
+#   services:
+#   - name: minibikini/postgres-with-rum:12
+#     alias: postgres
+#     command: ["postgres", "-c", "fsync=off", "-c", "synchronous_commit=off", "-c", "full_page_writes=off"]
+#   script:
+#     - mix deps.get
+#     - mix ecto.create
+#     - mix ecto.migrate
+#     - epmd -daemon
+#     - mix test --trace --only federated
+
+unit-testing-rum:
   stage: test
-  image: git.pleroma.social:5050/pleroma/pleroma/ci-base:elixir-1.17.1-otp-26
+  retry: 2
   cache: *testing_cache_policy
-  services: *testing_services
-  script: *testing_script
-
-formatting-1.15:
-  extends: .build_changes_policy
-  image: &formatting_elixir elixir:1.15-alpine
-  stage: lint
-  cache: *testing_cache_policy
-  before_script: &current_bfr_script
-    - apk update
-    - apk add build-base cmake file-dev git openssl
-    - mix local.hex --force
-    - mix local.rebar --force
+  services:
+  - name: minibikini/postgres-with-rum:12
+    alias: postgres
+    command: ["postgres", "-c", "fsync=off", "-c", "synchronous_commit=off", "-c", "full_page_writes=off"]
+  variables:
+    <<: *global_variables
+    RUM_ENABLED: "true"
+  script:
+    - apt-get update && apt-get install -y libimage-exiftool-perl
     - mix deps.get
+    - mix ecto.create
+    - mix ecto.migrate
+    - "mix ecto.migrate --migrations-path priv/repo/optional_migrations/rum_indexing/"
+    - mix test --preload-modules
+
+lint:
+  stage: test
+  cache: *testing_cache_policy
   script:
     - mix format --check-formatted
 
-cycles-1.15:
-  extends: .build_changes_policy
-  image: *formatting_elixir
-  stage: lint
-  cache: {}
-  before_script: *current_bfr_script
-  script:
-    - mix compile
-    - mix xref graph --format cycles --label compile | awk '{print $0} END{exit ($0 != "No cycles found")}'
-
 analysis:
-  extends:
-  - .build_changes_policy
-  - .using-ci-base
-  stage: lint
+  stage: test
   cache: *testing_cache_policy
   script:
+    - mix deps.get
     - mix credo --strict --only=warnings,todo,fixme,consistency,readability
 
-dialyzer:
-  extends:
-  - .build_changes_policy
-  - .using-ci-base
-  stage: lint
-  allow_failure: true
-  when: manual 
-  cache: *testing_cache_policy
-  tags:
-    - feld
-  script:
-    - mix dialyzer
-
 docs-deploy:
   stage: deploy
   cache: *testing_cache_policy
@@ -208,7 +123,7 @@ docs-deploy:
   before_script:
   - apk add curl
   script:
-  - curl --fail-with-body -X POST -F"token=$CI_JOB_TOKEN" -F'ref=master' -F"variables[BRANCH]=$CI_COMMIT_REF_NAME" https://git.pleroma.social/api/v4/projects/673/trigger/pipeline
+  - curl -X POST -F"token=$DOCS_PIPELINE_TRIGGER" -F'ref=master' -F"variables[BRANCH]=$CI_COMMIT_REF_NAME" https://git.pleroma.social/api/v4/projects/673/trigger/pipeline
 review_app:
   image: alpine:3.9
   stage: deploy
@@ -238,20 +153,6 @@ review_app:
     - (ssh -t dokku@pleroma.online -- certs:add "$CI_ENVIRONMENT_SLUG" /home/dokku/server.crt /home/dokku/server.key) || true
     - git push -f dokku@pleroma.online:$CI_ENVIRONMENT_SLUG $CI_COMMIT_SHA:refs/heads/master
 
-spec-deploy:
-  stage: deploy
-  artifacts:
-    paths:
-    - spec.json
-  only:
-    - develop@pleroma/pleroma
-  image: alpine:latest
-  before_script:
-    - apk add curl
-  script:
-    - curl --fail-with-body -X POST -F"token=$CI_JOB_TOKEN" -F'ref=master' -F"variables[BRANCH]=$CI_COMMIT_REF_NAME" -F"variables[JOB_REF]=$CI_JOB_ID" https://git.pleroma.social/api/v4/projects/1130/trigger/pipeline
-
-
 stop_review_app:
   image: alpine:3.9
   stage: deploy
@@ -272,15 +173,12 @@ stop_review_app:
 
 amd64:
   stage: release
-  image: 
-    name: hexpm/elixir-amd64:1.17.3-erlang-26.2.5.6-ubuntu-focal-20241011
+  image: elixir:1.10.3
   only: &release-only
   - stable@pleroma/pleroma
   - develop@pleroma/pleroma
   - /^maint/.*$/@pleroma/pleroma
   - /^release/.*$/@pleroma/pleroma
-  tags:
-    - amd64
   artifacts: &release-artifacts
     name: "pleroma-$CI_COMMIT_REF_NAME-$CI_COMMIT_SHORT_SHA-$CI_JOB_NAME"
     paths:
@@ -297,11 +195,9 @@ amd64:
           - deps
   variables: &release-variables
     MIX_ENV: prod
-    VIX_COMPILATION_MODE: PLATFORM_PROVIDED_LIBVIPS
-    DEBIAN_FRONTEND: noninteractive
   before_script: &before-release
-  - apt-get update && apt-get install -y cmake libmagic-dev libvips-dev erlang-dev git
-  - echo "import Config" > config/prod.secret.exs
+  - apt-get update && apt-get install -y cmake
+  - echo "import Mix.Config" > config/prod.secret.exs
   - mix local.hex --force
   - mix local.rebar --force
   script: &release
@@ -315,27 +211,23 @@ amd64-musl:
   stage: release
   artifacts: *release-artifacts
   only: *release-only
-  image: 
-    name: hexpm/elixir-amd64:1.17.3-erlang-26.2.5.6-alpine-3.17.9
-  tags:
-    - amd64
+  image: elixir:1.10.3-alpine 
   cache: *release-cache
   variables: *release-variables
   before_script: &before-release-musl
-  - apk add git build-base cmake file-dev openssl vips-dev
-  - echo "import Config" > config/prod.secret.exs
+  - apk add git gcc g++ musl-dev make cmake
+  - echo "import Mix.Config" > config/prod.secret.exs
   - mix local.hex --force
   - mix local.rebar --force
   script: *release
 
 arm:
   stage: release
-  allow_failure: true
   artifacts: *release-artifacts
   only: *release-only
   tags:
-    - arm32-specified
-  image: arm32v7/elixir:$ELIXIR_VER
+    - arm32
+  image: elixir:1.10.3
   cache: *release-cache
   variables: *release-variables
   before_script: *before-release
@@ -346,8 +238,8 @@ arm-musl:
   artifacts: *release-artifacts
   only: *release-only
   tags:
-    - arm32-specified
-  image: arm32v7/elixir:$ELIXIR_VER-alpine
+    - arm32
+  image: elixir:1.10.3-alpine
   cache: *release-cache
   variables: *release-variables
   before_script: *before-release-musl
@@ -359,8 +251,7 @@ arm64:
   only: *release-only
   tags:
     - arm
-  image: 
-    name: hexpm/elixir-arm64:1.17.3-erlang-26.2.5.6-ubuntu-focal-20241011
+  image: elixir:1.10.3
   cache: *release-cache
   variables: *release-variables
   before_script: *before-release
@@ -372,174 +263,88 @@ arm64-musl:
   only: *release-only
   tags:
     - arm
-  image: 
-    name: hexpm/elixir-arm64:1.17.3-erlang-26.2.5.6-alpine-3.17.9
+  # TODO: Replace with upstream image when 1.9.0 comes out
+  image: elixir:1.10.3-alpine
   cache: *release-cache
   variables: *release-variables
   before_script: *before-release-musl
   script: *release
 
-.kaniko:
+docker:
   stage: docker
-  image:
-    name: gcr.io/kaniko-project/executor:debug
-    entrypoint: [""]
+  image: docker:latest
   cache: {}
   dependencies: []
-  before_script: &before-kaniko
+  variables: &docker-variables
+    DOCKER_DRIVER: overlay2
+    DOCKER_HOST: unix:///var/run/docker.sock
+    IMAGE_TAG: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHORT_SHA
+    IMAGE_TAG_SLUG: $CI_REGISTRY_IMAGE:$CI_COMMIT_REF_SLUG
+    IMAGE_TAG_LATEST: $CI_REGISTRY_IMAGE:latest
+    IMAGE_TAG_LATEST_STABLE: $CI_REGISTRY_IMAGE:latest-stable
+    DOCKER_BUILDX_URL: https://github.com/docker/buildx/releases/download/v0.4.1/buildx-v0.4.1.linux-amd64
+    DOCKER_BUILDX_HASH: 71a7d01439aa8c165a25b59c44d3f016fddbd98b
+  before_script: &before-docker
+    - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY
+    - docker pull $IMAGE_TAG_SLUG || true
     - export CI_JOB_TIMESTAMP=$(date --utc -Iseconds)
     - export CI_VCS_REF=$CI_COMMIT_SHORT_SHA
-    - export IMAGE_TAG=$CI_REGISTRY_IMAGE/$BUILD_ARCH_IMG_SUFFIX:$CI_COMMIT_SHORT_SHA
-    - export IMAGE_TAG_SLUG=$CI_REGISTRY_IMAGE/$BUILD_ARCH_IMG_SUFFIX:$CI_COMMIT_REF_SLUG
-    - export IMAGE_TAG_LATEST=$CI_REGISTRY_IMAGE/$BUILD_ARCH_IMG_SUFFIX:latest
-    - export IMAGE_TAG_LATEST_STABLE=$CI_REGISTRY_IMAGE/$BUILD_ARCH_IMG_SUFFIX:latest-stable
-    - mkdir -p /kaniko/.docker
-    - echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > /kaniko/.docker/config.json
-
-.kaniko-latest:
-  extends: .kaniko
+  allow_failure: true
+  script:
+    - mkdir -p /root/.docker/cli-plugins
+    - wget "${DOCKER_BUILDX_URL}" -O ~/.docker/cli-plugins/docker-buildx
+    - echo "${DOCKER_BUILDX_HASH}  /root/.docker/cli-plugins/docker-buildx" | sha1sum -c
+    - chmod +x ~/.docker/cli-plugins/docker-buildx
+    - docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
+    - docker buildx create --name mbuilder --driver docker-container --use
+    - docker buildx inspect --bootstrap
+    - docker buildx build --platform linux/amd64,linux/arm/v7,linux/arm64/v8 --push --cache-from $IMAGE_TAG_SLUG --build-arg VCS_REF=$CI_VCS_REF --build-arg BUILD_DATE=$CI_JOB_TIMESTAMP -t $IMAGE_TAG -t $IMAGE_TAG_SLUG -t $IMAGE_TAG_LATEST .
+  tags:
+    - dind
   only:
     - develop@pleroma/pleroma
-  script:
-    - /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/Dockerfile --custom-platform=$BUILD_ARCH --build-arg VCS_REF=$CI_VCS_REF --build-arg BUILD_DATE=$CI_JOB_TIMESTAMP --build-arg ELIXIR_IMG=$ELIXIR_IMG --destination $IMAGE_TAG --destination $IMAGE_TAG_SLUG --destination $IMAGE_TAG_LATEST
 
-.kaniko-stable:
-  extends: .kaniko
-  only:
-    - stable@pleroma/pleroma
-  script:
-    - /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/Dockerfile --custom-platform=$BUILD_ARCH --build-arg VCS_REF=$CI_VCS_REF --build-arg BUILD_DATE=$CI_JOB_TIMESTAMP --build-arg ELIXIR_IMG=$ELIXIR_IMG --destination $IMAGE_TAG --destination $IMAGE_TAG_SLUG --destination $IMAGE_TAG_LATEST_STABLE
-
-.kaniko-release:
-  extends: .kaniko
-  only:
-    - /^release/.*$/@pleroma/pleroma
-  script:
-    - /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/Dockerfile --custom-platform=$BUILD_ARCH --build-arg VCS_REF=$CI_VCS_REF --build-arg BUILD_DATE=$CI_JOB_TIMESTAMP --build-arg ELIXIR_IMG=$ELIXIR_IMG --destination $IMAGE_TAG --destination $IMAGE_TAG_SLUG
-
-.kaniko-adhoc:
-  extends: .kaniko
-  only:
-    - /^build-docker/.*$/@pleroma/pleroma
-  script:
-    - /kaniko/executor --context $CI_PROJECT_DIR --dockerfile $CI_PROJECT_DIR/Dockerfile --custom-platform=$BUILD_ARCH --build-arg VCS_REF=$CI_VCS_REF --build-arg BUILD_DATE=$CI_JOB_TIMESTAMP --build-arg ELIXIR_IMG=$ELIXIR_IMG --destination $IMAGE_TAG --destination $IMAGE_TAG_SLUG
-
-.kaniko:linux/amd64:
-  variables:
-    BUILD_ARCH: linux/amd64
-    BUILD_ARCH_IMG_SUFFIX: linux-amd64
-    ELIXIR_IMG: hexpm/elixir
-  tags:
-    - amd64
-
-.kaniko:linux/arm64:
-  variables:
-    BUILD_ARCH: linux/arm64/v8
-    BUILD_ARCH_IMG_SUFFIX: linux-arm64-v8
-    ELIXIR_IMG: hexpm/elixir
-  tags:
-    - arm
-
-.kaniko:linux/arm:
-  variables:
-    BUILD_ARCH: linux/arm/v7
-    BUILD_ARCH_IMG_SUFFIX: linux-arm-v7
-    ELIXIR_IMG: git.pleroma.social:5050/pleroma/ci-image/elixir-linux-arm-v7
-  tags:
-    - arm32-specified
-
-kaniko-latest:linux/amd64:
-  extends:
-    - .kaniko-latest
-    - .kaniko:linux/amd64
-
-kaniko-latest:linux/arm64:
-  extends:
-    - .kaniko-latest
-    - .kaniko:linux/arm64
-
-kaniko-latest:linux/arm:
-  extends:
-    - .kaniko-latest
-    - .kaniko:linux/arm
-
-kaniko-stable:linux/amd64:
-  extends:
-    - .kaniko-stable
-    - .kaniko:linux/amd64
-
-kaniko-stable:linux/arm64:
-  extends:
-    - .kaniko-stable
-    - .kaniko:linux/arm64
-
-kaniko-stable:linux/arm:
-  extends:
-    - .kaniko-stable
-    - .kaniko:linux/arm
-
-kaniko-release:linux/amd64:
-  extends:
-    - .kaniko-release
-    - .kaniko:linux/amd64
-
-kaniko-release:linux/arm64:
-  extends:
-    - .kaniko-release
-    - .kaniko:linux/arm64
-
-kaniko-release:linux/arm:
-  extends:
-    - .kaniko-release
-    - .kaniko:linux/arm
-
-.docker-combine:
-  stage: docker-combine
-  image: docker:cli
+docker-stable:
+  stage: docker
+  image: docker:latest
   cache: {}
-  before_script:
-    - 'BUILD_ARCHES="linux-amd64 linux-arm64-v8 linux-arm-v7"'
-    - export IMAGE_TAG=$CI_REGISTRY_IMAGE:$CI_COMMIT_SHORT_SHA
-    - export IMAGE_TAG_SLUG=$CI_REGISTRY_IMAGE:$CI_COMMIT_REF_SLUG
-    - export IMAGE_TAG_LATEST=$CI_REGISTRY_IMAGE:latest
-    - export IMAGE_TAG_LATEST_STABLE=$CI_REGISTRY_IMAGE:latest-stable
-    - 'IMAGES=; for arch in $BUILD_ARCHES; do IMAGES="$IMAGES $CI_REGISTRY_IMAGE/$arch:$CI_COMMIT_SHORT_SHA"; done'
-    - 'IMAGES_SLUG=; for arch in $BUILD_ARCHES; do IMAGES_SLUG="$IMAGES_SLUG $CI_REGISTRY_IMAGE/$arch:$CI_COMMIT_REF_SLUG"; done'
-    - 'IMAGES_LATEST=; for arch in $BUILD_ARCHES; do IMAGES_LATEST="$IMAGES_LATEST $CI_REGISTRY_IMAGE/$arch:latest"; done'
-    - 'IMAGES_LATEST_STABLE=; for arch in $BUILD_ARCHES; do IMAGES_LATEST_STABLE="$IMAGES_LATEST_STABLE $CI_REGISTRY_IMAGE/$arch:latest"; done'
-    - mkdir -p ~/.docker
-    - echo "{\"auths\":{\"$CI_REGISTRY\":{\"username\":\"$CI_REGISTRY_USER\",\"password\":\"$CI_REGISTRY_PASSWORD\"}}}" > ~/.docker/config.json
-
-docker-combine:latest:
-  extends: .docker-combine
-  only:
-    - develop@pleroma/pleroma
+  dependencies: []
+  variables: *docker-variables
+  before_script: *before-docker
+  allow_failure: true
   script:
-    - 'docker manifest create $IMAGE_TAG $IMAGES'
-    - 'docker manifest push $IMAGE_TAG'
-    - 'docker manifest create $IMAGE_TAG_SLUG $IMAGES_SLUG'
-    - 'docker manifest push $IMAGE_TAG_SLUG'
-    - 'docker manifest create $IMAGE_TAG_LATEST $IMAGES_LATEST'
-    - 'docker manifest push $IMAGE_TAG_LATEST'
-
-docker-combine:stable:
-  extends: .docker-combine
+    - mkdir -p /root/.docker/cli-plugins
+    - wget "${DOCKER_BUILDX_URL}" -O ~/.docker/cli-plugins/docker-buildx
+    - echo "${DOCKER_BUILDX_HASH}  /root/.docker/cli-plugins/docker-buildx" | sha1sum -c
+    - chmod +x ~/.docker/cli-plugins/docker-buildx
+    - docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
+    - docker buildx create --name mbuilder --driver docker-container --use
+    - docker buildx inspect --bootstrap
+    - docker buildx build --platform linux/amd64,linux/arm/v7,linux/arm64/v8 --push --cache-from $IMAGE_TAG_SLUG --build-arg VCS_REF=$CI_VCS_REF --build-arg BUILD_DATE=$CI_JOB_TIMESTAMP -t $IMAGE_TAG -t $IMAGE_TAG_SLUG -t $IMAGE_TAG_LATEST_STABLE .
+  tags:
+    - dind
   only:
     - stable@pleroma/pleroma
-  script:
-    - 'docker manifest create $IMAGE_TAG $IMAGES'
-    - 'docker manifest push $IMAGE_TAG'
-    - 'docker manifest create $IMAGE_TAG_SLUG $IMAGES_SLUG'
-    - 'docker manifest push $IMAGE_TAG_SLUG'
-    - 'docker manifest create $IMAGE_TAG_LATEST_STABLE $IMAGES_LATEST_STABLE'
-    - 'docker manifest push $IMAGE_TAG_LATEST_STABLE'
 
-docker-combine:release:
-  extends: .docker-combine
+docker-release:
+  stage: docker
+  image: docker:latest
+  cache: {}
+  dependencies: []
+  variables: *docker-variables
+  before_script: *before-docker
+  allow_failure: true
+  script:
+  script:
+    - mkdir -p /root/.docker/cli-plugins
+    - wget "${DOCKER_BUILDX_URL}" -O ~/.docker/cli-plugins/docker-buildx
+    - echo "${DOCKER_BUILDX_HASH}  /root/.docker/cli-plugins/docker-buildx" | sha1sum -c
+    - chmod +x ~/.docker/cli-plugins/docker-buildx
+    - docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
+    - docker buildx create --name mbuilder --driver docker-container --use
+    - docker buildx inspect --bootstrap
+    - docker buildx build --platform linux/amd64,linux/arm/v7,linux/arm64/v8 --push --cache-from $IMAGE_TAG_SLUG --build-arg VCS_REF=$CI_VCS_REF --build-arg BUILD_DATE=$CI_JOB_TIMESTAMP -t $IMAGE_TAG -t $IMAGE_TAG_SLUG .
+  tags:
+    - dind
   only:
     - /^release/.*$/@pleroma/pleroma
-  script:
-    - 'docker manifest create $IMAGE_TAG $IMAGES'
-    - 'docker manifest push $IMAGE_TAG'
-    - 'docker manifest create $IMAGE_TAG_SLUG $IMAGES_SLUG'
-    - 'docker manifest push $IMAGE_TAG_SLUG'

.gitlab/merge_request_templates/Default.md

@@ -1,10 +0,0 @@
-### Checklist
-- [ ] Adding a changelog: In the `changelog.d` directory, create a file named `<code>.<type>`.
-
-  `<code>` can be anything, but we recommend using a more or less unique identifier to avoid collisions, such as the branch name.
-
-  `<type>` can be `add`, `change`, `remove`, `fix`, `security` or `skip`. `skip` is only used if there is no user-visible change in the MR (for example, only editing comments in the code). Otherwise, choose a type that corresponds to your change.
-
-  In the file, write the changelog entry. For example, if an MR adds group functionality, we can create a file named `group.add` and write `Add group functionality` in it.
-
-  If one changelog entry is not enough, you may add more. But that might mean you can split it into two MRs. Only use more than one changelog entry if you really need to (for example, when one change in the code fix two different bugs, or when refactoring).

.gitlab/merge_request_templates/Release.md

@@ -1,8 +1,6 @@
 ### Release checklist
-* [ ] Bump version in `mix.exs`
-* [ ] Compile a changelog with the `tools/collect-changelog` script
-* [ ] Create an MR with an announcement to pleroma.social
-#### post-merge
-* [ ] Tag the release on the merge commit
-* [ ] Make the tag into a Gitlab Release™
+* [ ]  Bump version in `mix.exs`
+* [ ]  Compile a changelog
+* [ ]  Create an MR with an announcement to pleroma.social
+* [ ]  Tag the release
 * [ ] Merge `stable` into `develop` (in case the fixes are already in develop, use `git merge -s ours --no-commit` and manually merge the changelogs)

.mailmap

@@ -1,3 +1,2 @@
 Ariadne Conill <ariadne@dereferenced.org> <nenolod@dereferenced.org>
 Ariadne Conill <ariadne@dereferenced.org> <nenolod@gmail.com>
-rinpatch <rin@patch.cx> <rinpatch@sdf.org>

.rgignore

@@ -1 +0,0 @@
-priv/static

CC-BY-4.0

@@ -1,395 +0,0 @@
-Attribution 4.0 International
-
-=======================================================================
-
-Creative Commons Corporation ("Creative Commons") is not a law firm and
-does not provide legal services or legal advice. Distribution of
-Creative Commons public licenses does not create a lawyer-client or
-other relationship. Creative Commons makes its licenses and related
-information available on an "as-is" basis. Creative Commons gives no
-warranties regarding its licenses, any material licensed under their
-terms and conditions, or any related information. Creative Commons
-disclaims all liability for damages resulting from their use to the
-fullest extent possible.
-
-Using Creative Commons Public Licenses
-
-Creative Commons public licenses provide a standard set of terms and
-conditions that creators and other rights holders may use to share
-original works of authorship and other material subject to copyright
-and certain other rights specified in the public license below. The
-following considerations are for informational purposes only, are not
-exhaustive, and do not form part of our licenses.
-
-     Considerations for licensors: Our public licenses are
-     intended for use by those authorized to give the public
-     permission to use material in ways otherwise restricted by
-     copyright and certain other rights. Our licenses are
-     irrevocable. Licensors should read and understand the terms
-     and conditions of the license they choose before applying it.
-     Licensors should also secure all rights necessary before
-     applying our licenses so that the public can reuse the
-     material as expected. Licensors should clearly mark any
-     material not subject to the license. This includes other CC-
-     licensed material, or material used under an exception or
-     limitation to copyright. More considerations for licensors:
-    wiki.creativecommons.org/Considerations_for_licensors
-
-     Considerations for the public: By using one of our public
-     licenses, a licensor grants the public permission to use the
-     licensed material under specified terms and conditions. If
-     the licensor's permission is not necessary for any reason--for
-     example, because of any applicable exception or limitation to
-     copyright--then that use is not regulated by the license. Our
-     licenses grant only permissions under copyright and certain
-     other rights that a licensor has authority to grant. Use of
-     the licensed material may still be restricted for other
-     reasons, including because others have copyright or other
-     rights in the material. A licensor may make special requests,
-     such as asking that all changes be marked or described.
-     Although not required by our licenses, you are encouraged to
-     respect those requests where reasonable. More considerations
-     for the public:
-    wiki.creativecommons.org/Considerations_for_licensees
-
-=======================================================================
-
-Creative Commons Attribution 4.0 International Public License
-
-By exercising the Licensed Rights (defined below), You accept and agree
-to be bound by the terms and conditions of this Creative Commons
-Attribution 4.0 International Public License ("Public License"). To the
-extent this Public License may be interpreted as a contract, You are
-granted the Licensed Rights in consideration of Your acceptance of
-these terms and conditions, and the Licensor grants You such rights in
-consideration of benefits the Licensor receives from making the
-Licensed Material available under these terms and conditions.
-
-
-Section 1 -- Definitions.
-
-  a. Adapted Material means material subject to Copyright and Similar
-     Rights that is derived from or based upon the Licensed Material
-     and in which the Licensed Material is translated, altered,
-     arranged, transformed, or otherwise modified in a manner requiring
-     permission under the Copyright and Similar Rights held by the
-     Licensor. For purposes of this Public License, where the Licensed
-     Material is a musical work, performance, or sound recording,
-     Adapted Material is always produced where the Licensed Material is
-     synched in timed relation with a moving image.
-
-  b. Adapter's License means the license You apply to Your Copyright
-     and Similar Rights in Your contributions to Adapted Material in
-     accordance with the terms and conditions of this Public License.
-
-  c. Copyright and Similar Rights means copyright and/or similar rights
-     closely related to copyright including, without limitation,
-     performance, broadcast, sound recording, and Sui Generis Database
-     Rights, without regard to how the rights are labeled or
-     categorized. For purposes of this Public License, the rights
-     specified in Section 2(b)(1)-(2) are not Copyright and Similar
-     Rights.
-
-  d. Effective Technological Measures means those measures that, in the
-     absence of proper authority, may not be circumvented under laws
-     fulfilling obligations under Article 11 of the WIPO Copyright
-     Treaty adopted on December 20, 1996, and/or similar international
-     agreements.
-
-  e. Exceptions and Limitations means fair use, fair dealing, and/or
-     any other exception or limitation to Copyright and Similar Rights
-     that applies to Your use of the Licensed Material.
-
-  f. Licensed Material means the artistic or literary work, database,
-     or other material to which the Licensor applied this Public
-     License.
-
-  g. Licensed Rights means the rights granted to You subject to the
-     terms and conditions of this Public License, which are limited to
-     all Copyright and Similar Rights that apply to Your use of the
-     Licensed Material and that the Licensor has authority to license.
-
-  h. Licensor means the individual(s) or entity(ies) granting rights
-     under this Public License.
-
-  i. Share means to provide material to the public by any means or
-     process that requires permission under the Licensed Rights, such
-     as reproduction, public display, public performance, distribution,
-     dissemination, communication, or importation, and to make material
-     available to the public including in ways that members of the
-     public may access the material from a place and at a time
-     individually chosen by them.
-
-  j. Sui Generis Database Rights means rights other than copyright
-     resulting from Directive 96/9/EC of the European Parliament and of
-     the Council of 11 March 1996 on the legal protection of databases,
-     as amended and/or succeeded, as well as other essentially
-     equivalent rights anywhere in the world.
-
-  k. You means the individual or entity exercising the Licensed Rights
-     under this Public License. Your has a corresponding meaning.
-
-
-Section 2 -- Scope.
-
-  a. License grant.
-
-       1. Subject to the terms and conditions of this Public License,
-          the Licensor hereby grants You a worldwide, royalty-free,
-          non-sublicensable, non-exclusive, irrevocable license to
-          exercise the Licensed Rights in the Licensed Material to:
-
-            a. reproduce and Share the Licensed Material, in whole or
-               in part; and
-
-            b. produce, reproduce, and Share Adapted Material.
-
-       2. Exceptions and Limitations. For the avoidance of doubt, where
-          Exceptions and Limitations apply to Your use, this Public
-          License does not apply, and You do not need to comply with
-          its terms and conditions.
-
-       3. Term. The term of this Public License is specified in Section
-          6(a).
-
-       4. Media and formats; technical modifications allowed. The
-          Licensor authorizes You to exercise the Licensed Rights in
-          all media and formats whether now known or hereafter created,
-          and to make technical modifications necessary to do so. The
-          Licensor waives and/or agrees not to assert any right or
-          authority to forbid You from making technical modifications
-          necessary to exercise the Licensed Rights, including
-          technical modifications necessary to circumvent Effective
-          Technological Measures. For purposes of this Public License,
-          simply making modifications authorized by this Section 2(a)
-          (4) never produces Adapted Material.
-
-       5. Downstream recipients.
-
-            a. Offer from the Licensor -- Licensed Material. Every
-               recipient of the Licensed Material automatically
-               receives an offer from the Licensor to exercise the
-               Licensed Rights under the terms and conditions of this
-               Public License.
-
-            b. No downstream restrictions. You may not offer or impose
-               any additional or different terms or conditions on, or
-               apply any Effective Technological Measures to, the
-               Licensed Material if doing so restricts exercise of the
-               Licensed Rights by any recipient of the Licensed
-               Material.
-
-       6. No endorsement. Nothing in this Public License constitutes or
-          may be construed as permission to assert or imply that You
-          are, or that Your use of the Licensed Material is, connected
-          with, or sponsored, endorsed, or granted official status by,
-          the Licensor or others designated to receive attribution as
-          provided in Section 3(a)(1)(A)(i).
-
-  b. Other rights.
-
-       1. Moral rights, such as the right of integrity, are not
-          licensed under this Public License, nor are publicity,
-          privacy, and/or other similar personality rights; however, to
-          the extent possible, the Licensor waives and/or agrees not to
-          assert any such rights held by the Licensor to the limited
-          extent necessary to allow You to exercise the Licensed
-          Rights, but not otherwise.
-
-       2. Patent and trademark rights are not licensed under this
-          Public License.
-
-       3. To the extent possible, the Licensor waives any right to
-          collect royalties from You for the exercise of the Licensed
-          Rights, whether directly or through a collecting society
-          under any voluntary or waivable statutory or compulsory
-          licensing scheme. In all other cases the Licensor expressly
-          reserves any right to collect such royalties.
-
-
-Section 3 -- License Conditions.
-
-Your exercise of the Licensed Rights is expressly made subject to the
-following conditions.
-
-  a. Attribution.
-
-       1. If You Share the Licensed Material (including in modified
-          form), You must:
-
-            a. retain the following if it is supplied by the Licensor
-               with the Licensed Material:
-
-                 i. identification of the creator(s) of the Licensed
-                    Material and any others designated to receive
-                    attribution, in any reasonable manner requested by
-                    the Licensor (including by pseudonym if
-                    designated);
-
-                ii. a copyright notice;
-
-               iii. a notice that refers to this Public License;
-
-                iv. a notice that refers to the disclaimer of
-                    warranties;
-
-                 v. a URI or hyperlink to the Licensed Material to the
-                    extent reasonably practicable;
-
-            b. indicate if You modified the Licensed Material and
-               retain an indication of any previous modifications; and
-
-            c. indicate the Licensed Material is licensed under this
-               Public License, and include the text of, or the URI or
-               hyperlink to, this Public License.
-
-       2. You may satisfy the conditions in Section 3(a)(1) in any
-          reasonable manner based on the medium, means, and context in
-          which You Share the Licensed Material. For example, it may be
-          reasonable to satisfy the conditions by providing a URI or
-          hyperlink to a resource that includes the required
-          information.
-
-       3. If requested by the Licensor, You must remove any of the
-          information required by Section 3(a)(1)(A) to the extent
-          reasonably practicable.
-
-       4. If You Share Adapted Material You produce, the Adapter's
-          License You apply must not prevent recipients of the Adapted
-          Material from complying with this Public License.
-
-
-Section 4 -- Sui Generis Database Rights.
-
-Where the Licensed Rights include Sui Generis Database Rights that
-apply to Your use of the Licensed Material:
-
-  a. for the avoidance of doubt, Section 2(a)(1) grants You the right
-     to extract, reuse, reproduce, and Share all or a substantial
-     portion of the contents of the database;
-
-  b. if You include all or a substantial portion of the database
-     contents in a database in which You have Sui Generis Database
-     Rights, then the database in which You have Sui Generis Database
-     Rights (but not its individual contents) is Adapted Material; and
-
-  c. You must comply with the conditions in Section 3(a) if You Share
-     all or a substantial portion of the contents of the database.
-
-For the avoidance of doubt, this Section 4 supplements and does not
-replace Your obligations under this Public License where the Licensed
-Rights include other Copyright and Similar Rights.
-
-
-Section 5 -- Disclaimer of Warranties and Limitation of Liability.
-
-  a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
-     EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
-     AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
-     ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
-     IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
-     WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
-     PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
-     ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
-     KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
-     ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
-
-  b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
-     TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
-     NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
-     INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
-     COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
-     USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
-     ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
-     DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
-     IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
-
-  c. The disclaimer of warranties and limitation of liability provided
-     above shall be interpreted in a manner that, to the extent
-     possible, most closely approximates an absolute disclaimer and
-     waiver of all liability.
-
-
-Section 6 -- Term and Termination.
-
-  a. This Public License applies for the term of the Copyright and
-     Similar Rights licensed here. However, if You fail to comply with
-     this Public License, then Your rights under this Public License
-     terminate automatically.
-
-  b. Where Your right to use the Licensed Material has terminated under
-     Section 6(a), it reinstates:
-
-       1. automatically as of the date the violation is cured, provided
-          it is cured within 30 days of Your discovery of the
-          violation; or
-
-       2. upon express reinstatement by the Licensor.
-
-     For the avoidance of doubt, this Section 6(b) does not affect any
-     right the Licensor may have to seek remedies for Your violations
-     of this Public License.
-
-  c. For the avoidance of doubt, the Licensor may also offer the
-     Licensed Material under separate terms or conditions or stop
-     distributing the Licensed Material at any time; however, doing so
-     will not terminate this Public License.
-
-  d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
-     License.
-
-
-Section 7 -- Other Terms and Conditions.
-
-  a. The Licensor shall not be bound by any additional or different
-     terms or conditions communicated by You unless expressly agreed.
-
-  b. Any arrangements, understandings, or agreements regarding the
-     Licensed Material not stated herein are separate from and
-     independent of the terms and conditions of this Public License.
-
-
-Section 8 -- Interpretation.
-
-  a. For the avoidance of doubt, this Public License does not, and
-     shall not be interpreted to, reduce, limit, restrict, or impose
-     conditions on any use of the Licensed Material that could lawfully
-     be made without permission under this Public License.
-
-  b. To the extent possible, if any provision of this Public License is
-     deemed unenforceable, it shall be automatically reformed to the
-     minimum extent necessary to make it enforceable. If the provision
-     cannot be reformed, it shall be severed from this Public License
-     without affecting the enforceability of the remaining terms and
-     conditions.
-
-  c. No term or condition of this Public License will be waived and no
-     failure to comply consented to unless expressly agreed to by the
-     Licensor.
-
-  d. Nothing in this Public License constitutes or may be interpreted
-     as a limitation upon, or waiver of, any privileges and immunities
-     that apply to the Licensor or You, including from the legal
-     processes of any jurisdiction or authority.
-
-
-=======================================================================
-
-Creative Commons is not a party to its public
-licenses. Notwithstanding, Creative Commons may elect to apply one of
-its public licenses to material it publishes and in those instances
-will be considered the “Licensor.” The text of the Creative Commons
-public licenses is dedicated to the public domain under the CC0 Public
-Domain Dedication. Except for the limited purpose of indicating that
-material is shared under a Creative Commons public license or as
-otherwise permitted by the Creative Commons policies published at
-creativecommons.org/policies, Creative Commons does not authorize the
-use of the trademark "Creative Commons" or any other trademark or logo
-of Creative Commons without its prior written consent including,
-without limitation, in connection with any unauthorized modifications
-to any of its public licenses or any other arrangements,
-understandings, or agreements concerning use of licensed material. For
-the avoidance of doubt, this paragraph does not form part of the
-public licenses.
-
-Creative Commons may be contacted at creativecommons.org.

CHANGELOG.md

@@ -1,786 +1,8 @@
 # Changelog
-
 All notable changes to this project will be documented in this file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
 
-## 2.9.1
-
-### Security
-- Fix authorization checks for C2S Update activities to prevent unauthorized modifications of other users' content.
-- Fix content-type spoofing vulnerability that could allow users to upload ActivityPub objects as attachments
-- Reject cross-domain redirects when fetching ActivityPub objects to prevent bypassing domain-based security controls.
-- Limit emoji shortcodes to alphanumeric, dash, or underscore characters to prevent potential abuse.
-- Block attempts to fetch activities from the local instance to prevent spoofing.
-- Sanitize Content-Type headers in media proxy to prevent serving malicious ActivityPub content through proxied media.
-- Validate Content-Type headers when fetching remote ActivityPub objects to prevent spoofing attacks.
-
-### Changed
-- Include `pl-fe` in available frontends
-
-### Fixed
-- Remove trailing ` from end of line 75 which caused issues copy-pasting
-
-## 2.9.0
-
-### Security
-- Require HTTP signatures (if enabled) for routes used by both C2S and S2S AP API
-- Fix several spoofing vectors
-
-### Changed
-- Performance: Use 301 (permanent) redirect instead of 302 (temporary) when redirecting small images in media proxy. This allows browsers to cache the redirect response. 
-
-### Added
-- Include "published" in actor view
-- Link to exported outbox/followers/following collections in backup actor.json
-- Hashtag following
-- Allow to specify post language
-
-### Fixed
-- Verify a local Update sent through AP C2S so users can only update their own objects
-- Fix Mastodon incoming edits with inlined "likes"
-- Allow incoming "Listen" activities
-- Fix missing check for domain presence in rich media ignore_host configuration
-- Fix Rich Media parsing of TwitterCards/OpenGraph to adhere to the spec and always choose the first image if multiple are provided.
-- Fix OpenGraph/TwitterCard meta tag ordering for posts with multiple attachments
-- Fix blurhash generation crashes
-
-### Removed
-- Retire MRFs DNSRBL, FODirectReply, and QuietReply
-
-## 2.8.0
-
-### Changed
-- Metadata: Do not include .atom feed links for remote accounts
-- Bumped `fast_html` to v2.3.0, which notably allows to use system-installed lexbor with passing `WITH_SYSTEM_LEXBOR=1` environment variable at build-time
-- Dedupe upload filter now uses a three-level sharding directory structure
-- Deprecate `/api/v1/pleroma/accounts/:id/subscribe`/`unsubscribe`
-- Restrict incoming activities from unknown actors to a subset that does not imply a previous relationship and early rejection of unrecognized activity types.
-- Elixir 1.14 and Erlang/OTP 23 is now the minimum supported release
-- Support `id` param in `GET /api/v1/statuses`
-- LDAP authentication has been refactored to operate as a GenServer process which will maintain an active connection to the LDAP server.
-- Fix 'Setting a marker should mark notifications as read'
-- Adjust more Oban workers to enforce unique job constraints.
-- Oban updated to 2.18.3
-- Publisher behavior improvement when snoozing Oban jobs due to Gun connection pool contention.
-- Poll results refreshing is handled asynchronously and will not attempt to keep fetching updates to a closed poll.
-- Tuning for release builds to lower CPU usage.
-- Rich Media preview fetching will skip making an HTTP HEAD request to check a URL for allowed content type and length if the Tesla adapter is Gun or Finch
-- Fix nonexisting user will not generate metadata for search engine opt-out
-- Update Oban to 2.18
-- Worker configuration is no longer available. This only affects custom max_retries values for a couple Oban queues.
-
-### Added
-- Add metadata provider for ActivityPub alternate links
-- Added support for argon2 passwords and their conversion for migration from Akkoma fork to upstream.
-- Respect :restrict_unauthenticated for hashtag rss/atom feeds
-- LDAP configuration now permits overriding the CA root certificate file for TLS validation.
-- LDAP now supports users changing their passwords
-- Include list id in StatusView
-- Added MRF.FODirectReply which changes replies to followers-only posts to be direct.
-- Add `id_filter` to MRF to filter URLs and their domain prior to fetching
-- Added MRF.QuietReply which prevents replies to public posts from being published to the timelines
-- Add `group_key` to notifications
-- Allow providing avatar/header descriptions
-- Added RemoteReportPolicy from Rebased for handling bogus federated reports
-- scrubbers/default: Allow "mention hashtag" classes used by Mastodon
-- Added dependencies for Swoosh's Mua mail adapter
-- Include session scopes in TokenView
-
-### Fixed
-- Verify a local Update sent through AP C2S so users can only update their own objects
-- Fixed malformed follow requests that cause them to appear stuck pending due to the recipient being unable to process them.
-- Fix incoming Block activities being rejected
-- STARTTLS certificate and hostname verification for LDAP authentication
-- LDAPS connections (implicit TLS) are now supported.
-- Fix /api/v2/media returning the wrong status code (202) for media processed synchronously
-- Miscellaneous fixes for Meilisearch support
-- Fix pleroma_ctl mix task calls sometimes not being found
-- Add a rate limiter to the OAuth App creation endpoint and ensure registered apps are assigned to users.
-- ReceiverWorker will cancel processing jobs instead of retrying if the user cannot be fetched due to 403, 404, or 410 errors or if the account is disabled locally.
-- Address case where instance reachability status couldn't be updated
-- Remote Fetcher Worker recognizes more permanent failure errors
-- StreamerView: Do not leak follows count if hidden
-- Imports of blocks, mutes, and follows would retry repeatedly due to incorrect error handling and all work executed in a single job
-- Make vapid_config return empty array, fixing preloading for instances without push notifications configured
-
-### Removed
-- Remove stub for /api/v1/accounts/:id/identity_proofs (deprecated by Mastodon 3.5.0)
-
-## 2.7.1
-
-### Changed
-- Accept `application/activity+json` for requests to `/.well-known/nodeinfo`
-
-### Fixed
-- Truncate remote user fields, avoids them getting rejected
-- Improve the `FollowValidator` to successfully incoming activities with an errant `cc` field.
-- Resolved edge case where the API can report you are following a user but the relationship is not fully established.
-- The Swoosh email adapter for Mailgun was missing a new dependency on `:multipart`
-- Fix Mastodon WebSocket authentication
-
-## 2.7.0
-
-### Security
-- HTTP Security: By default, don't allow unsafe-eval. The setting needs to be changed to allow Flash emulation.
-- Fix webfinger spoofing.
-- Use proper workers for fetching pins instead of an ad-hoc task, fixing a potential fetch loop
-
-### Changed
-- Update to Phoenix 1.7
-- Elixir Logger configuration is now longer permitted through AdminFE and ConfigDB
-- Refactor the user backups code and improve test coverage
-- Invalid activities delivered to the inbox will be rejected with a 400 Bad Request
-- Support Bandit as an alternative to Cowboy for the HTTP server. 
-- Update Bandit to 1.5.2
-- Replace eblurhash with rinpatch_blurhash. This also removes a dependency on ImageMagick.
-- Elixir 1.13 is the minimum required version.
-- Document maximum supported version of Erlang & Elixir
-- Update and extend NetBSD installation docs
-- Make `/api/v1/pleroma/federation_status` publicly available
-- Increase outgoing federation parallelism
-- Change Hackney connection pool timeouts to align with the values Gun uses
-- Transmogrifier: handle non-validate errors on incoming Delete activities
-- Remote object fetch failures will prevent the object fetch job from retrying if the object request returns 401, 403, 404, 410, or exceeds the maximum thread depth.
-- - Change AccountView `last_status_at` from a datetime to a date (as done in Mastodon 3.1.0)
-- Improve error logging when LDAP authentication fails.
-- Publisher jobs will not retry if the error received is a 400
-- PollWorker jobs will not retry if the activity no longer exists.
-- Improved detecting unrecoverable errors for incoming federation jobs
-- Changed some jobs to return :cancel on unrecoverable errors that should not be retried
-- Discard Remote Fetcher jobs which errored due to an MRF rejection.
-- Oban queues have refactored to simplify the queue design
-- Ensure all Oban jobs have timeouts defined
-- Optimistic Inbox reduces the processing overhead of incoming activities without instantly verifiable signatures.
-- HTTP connection pool adjustments
-- Disable jit by default for PostgreSQL
-- Update the documentation for configuring Prometheus metrics.
-- Change the prometheus library to PromEx.
-- Publisher jobs now store the the activity id instead of inserting duplicate JSON data in the Oban queue for each delivery.
-- Activity publishing failures will prevent the job from retrying if the publishing request returns a 403 or 410
-- Publisher errors will now emit logs indicating the inbox that was not available for delivery.
-- Reduce the reachability timestamp update to a single upsert query
-- A 422 error is returned when attempting to reply to a deleted status
-- Rich Media backfilling is now an Oban job
-- Refactored Rich Media to cache the content in the database. Fetching operations that could block status rendering have been eliminated.
-- Set default values on validators for transient objects (attachment, poll options)
-- User profile refreshes are now asynchronous
-- Change mediaproxy previews to use vips to generate thumbnails instead of ImageMagick
-- Render nice web push notifications for polls
-- Refactor the Mastodon /api/v1/streaming websocket handler to use Phoenix.Socket.Transport
-
-### Added
-- Uploader: Add support for uploading attachments using IPFS
-- Add NSFW-detecting MRF
-- Add DNSRBL MRF
-- Add options to the mix prune_objects task
-- Add Anti-mention Spam MRF backported from Rebased
-- HTTPSignaturePlug: Add :authorized_fetch_mode_exceptions configuration
-- Support /authorize-interaction route used by Mastodon
-- Add an option to reject certain domains when authorized fetch is enabled.
-- Include following/followers in backups
-- Allow to group bookmarks in folders
-- Include image description in status media cards
-- Implement `/api/v1/accounts/familiar_followers`
-- Add support for configuring favicon, embed favicon and PWA manifest in server-generated meta
-- Implement FEP-2c59, add "webfinger" to user actor
-- Framegrabs with ffmpeg will execute with a 5 second timeout and cache the URLs of failures with a TTL of 15 minutes to prevent excessive retries.
-- Added a Mix task "pleroma.config fix_mrf_policies" which will remove erroneous MRF policies from ConfigDB.
-- Add ForceMention MRF
-- [docs] add frontends management documentation
-- Implement group actors
-- Add contact account to InstanceView
-- Add instance rules
-- Implement /api/v2/instance route
-- Verify profile link ownership with rel="me"
-- Logger metadata is now attached to some logs to help with troubleshooting and analysis
-- Add new parameters to /api/v2/instance: configuration[accounts][max_pinned_statuses] and configuration[statuses][characters_reserved_per_url]
-- Add meilisearch, make search engines pluggable
-- Add missing indexes on foreign key relationships
-- Startup detection for configured MRF modules that are missing or incorrectly defined
-- Permit passing --chunk and --step values to the Pleroma.Search.Indexer Mix task
-- Deleting, Unfavoriting, Unrepeating, or Unreacting will cancel undelivered publishing jobs for the original activity.
-- Oban jobs can now be viewed in the Live Dashboard
-- Add media proxy to opengraph rich media cards
-- Support for Erlang OTP 26
-- Prioritize mentioned recipients (i.e., those that are not just followers) when federating.
-- PromEx documentation
-- Expose nonAnonymous field from Smithereen polls
-- Add Qdrant/OpenAI embedding search
-- Adds the capability to add a URL to a scrobble (optional field)
-- scrubbers/default: Add more formatting elements from HTML4 / GoToSocial (acronym, bdo, big, cite, dfn, ins, kbd, q, samp, s, tt, var, wbr)
-- Monitoring of search backend health to control the processing of jobs in the search indexing Oban queue
-- Display reposted replies with exclude_replies: true
-- Add "status" notification type
-- Support honk-style attachment summaries as alt-text.
-
-### Fixed
-- Fix Emoji object IDs not always being valid
-- Remove checking ImageMagick's commands for Pleroma.Upload.Filter.AnalyzeMetadata
-- Ensure that StripLocation actually removes everything resembling GPS data from PNGs
-- Fix authentication check on account rendering when bio is defined
-- ap userview: add outbox field.
-- Fix #strip_report_status_data
-- Fix federation with Convergence AP Bridge
-- ChatMessage: Tolerate attachment field set to an empty array
-- Config: Check the permissions of the linked file instead of the symlink
-- MediaProxy was setting the content-length header which is not permitted by RFC9112§6.2 when we are chunking the reply as it conflicts with the existence of the transfer-encoding header.
-- Restore Cowboy's ability to stream MediaProxy responses without Chunked encoding.
-- Fix the processing of email digest jobs.
-- Client application data was always missing from the status
-- Elixir 1.15 compatibility
-- When downloading remote emojis packs, account for pagination
-- Make remote emoji packs API use specifically the V1 URL. Akkoma does not understand it without V1, and it works either way with normal pleroma, so no reason to not do this
-- Following HTTP Redirects when the HTTP Adapter is Finch
-- Video framegrabs were not working correctly after the change to use Exile to execute ffmpeg
-- Deactivated groups would still try to repeat a post.
-- Fix logic error in Gun connection pooling which prevented retries even when the worker was launched with retry = true
-- Connection pool errors when publishing an activity is a soft-error that will be retried shortly.
-- Gun Connection Pool was not retrying to acquire a connection if the pool was full and stale connections were reclaimed
-- TwitterAPI: Return proper error when healthcheck is disabled
-- Handle cases when users.inbox is nil.
-- Fix LDAP support
-- Use correct domain for fqn and InstanceView
-- The query for marking notifications as read has been simplified
-- Mastodon API /api/v1/directory: Fix listing directory contents when not authenticated
-- Ensure MediaProxy HTTP requests obey all the defined connection settings
-- Fix a memory leak caused by Websocket connections that would not enter a state where a full garbage collection run could be triggered.
-- Fix OpenGraph and Twitter metadata providers when parsing objects with no content or summary fields.
-- MRF: Log sensible error for subdomains_regex
-- MRF.StealEmojiPolicy: Properly add fallback extension to filenames missing one
-- Federated timeline removal of hashtags via MRF HashtagPolicy
-- Support objects with a null contentMap (firefish)
-- Fix notifications query which was not using the index properly
-- Notifications: improve performance by filtering on users table instead of activities table
-- Prevent Rich Media backfill jobs from retrying in cases where it is likely they will fail again.
-- Oban Jobs for refreshing users were not respecting the uniqueness setting
-- Fix Optimistic Inbox for failed signatures
-- MediaProxy Preview failures prevented when encountering certain video files
-- pleroma_ctl: Use realpath(1) instead of readlink(1)
-- ReceiverWorker: Make sure non-{:ok, _} is returned as {:error, …}
-- Harden Rich Media parsing against very slow or malicious URLs
-- Rich Media Preview cache eviction when the activity is updated.
-- Parsing of RichMedia TTLs for Amazon URLs when query parameters are nil
-- End of poll notifications were not streamed over websockets or web push
-- Fix eblurhash and elixir-captcha not using system cflags
-- Video thumbnails were not being generated due to a negative cache lookup logic error
-- Fix web push notifications not successfully delivering
-- Web Push notifications are no longer generated for muted/blocked threads and users.
-- Fix validate_webfinger when running a different domain for Webfinger
-
-### Removed
-- Mastodon API: Remove deprecated GET /api/v1/statuses/:id/card endpoint https://github.com/mastodon/mastodon/pull/11213
-- Removed support for multiple federator modules as we only support ActivityPub
-
-## 2.6.2
-
-### Security
-- MRF StealEmojiPolicy: Sanitize shortcodes (thanks to Hazel K for the report
-
-## 2.6.1
-### Changed
-- - Document maximum supported version of Erlang & Elixir
-
-### Added
-- [docs] add frontends management documentation
-
-### Fixed
-- TwitterAPI: Return proper error when healthcheck is disabled
-- Fix eblurhash and elixir-captcha not using system cflags
-
-## 2.6.0
-### Security
-- Preload: Make generated JSON html-safe. It already was html safe because it only consists of config data that is base64 encoded, but this will keep it safe it that ever changes.
-- CommonAPI: Prevent users from accessing media of other users by creating a status with reused attachment ID
-- Disable XML entity resolution completely to fix a dos vulnerability
-
-### Added
-- Support for Image activities, namely from Hubzilla
-- Add OAuth scope descriptions
-- Allow lang attribute in status text
-- OnlyMedia Upload Filter
-- Implement MRF policy to reject or delist according to emojis
-- (hardening) Add no_new_privs=yes to OpenRC service files
-- Implement quotes
-- Add unified streaming endpoint
-
-### Fixed
-- rel="me" was missing its cache
-- MediaProxy responses now return a sandbox CSP header
-- Filter context activities using Visibility.visible_for_user?
-- UploadedMedia: Add missing disposition_type to Content-Disposition
-- fix not being able to fetch flash file from remote instance
-- Fix abnormal behaviour when refetching a poll
-- Allow non-HTTP(s) URIs in "url" fields for compatibility with "FEP-fffd: Proxy Objects"
-- Fix opengraph and twitter card meta tags
-- ForceMentionsInContent: fix double mentions for Mastodon/Misskey posts
-- OEmbed HTML tags are now filtered
-- Restrict attachments to only uploaded files only
-- Fix error 404 when deleting status of a banned user
-- Fix config ownership in dockerfile to pass restriction test
-- Fix user fetch completely broken if featured collection is not in a supported form
-- Correctly handle the situation when a poll has both "anyOf" and "oneOf" but one of them being empty
-- Fix handling report from a deactivated user
-- Prevent using the .json format to bypass authorized fetch mode
-- Fix mentioning punycode domains when using Markdown
-- Show more informative errors when profile exceeds char limits
-
-### Removed
-- BREAKING: Support for passwords generated with `crypt(3)` (Gnu Social migration artifact)
-- remove BBS/SSH feature, replaced by an external bridge.
-- Remove a few unused indexes.
-- Cleanup OStatus-era user upgrades and ap_enabled indicator
-- Deprecate Pleroma's audio scrobbling
-
-## 2.5.4
-
-## Security
-- Fix XML External Entity (XXE) loading vulnerability allowing to fetch arbitrary files from the server's filesystem
-
-## 2.5.3
-
-### Security
-- Emoji pack loader sanitizes pack names
-- Reduced permissions of config files and directories, distros requiring greater permissions like group-read need to pre-create the directories
-
-## 2.5.5
-
-## Security
-- Prevent users from accessing media of other users by creating a status with reused attachment ID
-
-## 2.5.4
-
-## Security
-- Fix XML External Entity (XXE) loading vulnerability allowing to fetch arbitrary files from the server's filesystem
-
-## 2.5.3
-
-### Security
-- Emoji pack loader sanitizes pack names
-- Reduced permissions of config files and directories, distros requiring greater permissions like group-read need to pre-create the directories
-
-## 2.5.2
-
-### Security
-- `/proxy` endpoint now sets a Content-Security-Policy (sandbox)
-- WebSocket endpoint now respects unauthenticated restrictions for streams of public posts
-- OEmbed HTML tags are now filtered
-
-### Changed
-- docs: Be more explicit about the level of compatibility of OTP releases
-- Set default background worker timeout to 15 minutes
-
-### Fixed
-- Atom/RSS formatting (HTML truncation, published, missing summary)
-- Remove `static_fe` pipeline for `/users/:nickname/feed`
-- Stop oban from retrying if validating errors occur when processing incoming data
-- Make sure object refetching as used by already received polls follows MRF rules
-
-### Removed
-- BREAKING: Support for passwords generated with `crypt(3)` (Gnu Social migration artifact)
-
-## 2.5.1
-
-### Added
-- Allow customizing instance languages
-
-### Fixed
-- Security: uploading HTTP endpoint can no longer create directories in the upload dir (internal APIs, like backup, still can do it.)
-- ~ character in urls in Markdown posts are handled properly
-- Exiftool upload filter will now ignore SVG files
-- Fix `block_from_stranger` setting
-- Fix rel="me"
-- Docker images will now run properly
-- Fix improper content being cached in report content
-- Notification filter on object content will not operate on the ones that inherently have no content
-- ZWNJ and double dots in links are parsed properly for Plain-text posts
-- OTP releases will work on systems with a newer libcrypt
-- Errors when running Exiftool.ReadDescription filter will not be filled into the image description
-
-## 2.5.0 - 2022-12-23
-
-### Removed
-
-- MastoFE
-- Quack, the logging backend that pushes to Slack channels
-
-### Changed
-- **Breaking:** Elixir >=1.11 is now required (was >= 1.9)
-- Allow users to remove their emails if instance does not need email to register
-- Uploadfilter `Pleroma.Upload.Filter.Exiftool` has been renamed to `Pleroma.Upload.Filter.Exiftool.StripLocation`
-- **Breaking**: `/api/v1/pleroma/backups` endpoints now requires `read:backups` scope instead of `read:accounts`
-- Updated the recommended pleroma.vcl configuration for Varnish to target Varnish 7.0+
-- Set timeout values for Oban queues. The default is infinity and some operations may not time out on their own.
-- Delete activities are federated at lowest priority
-- CSP now includes wasm-unsafe-eval
-
-### Added
-- `activeMonth` and `activeHalfyear` fields in NodeInfo usage.users object
-- Experimental support for Finch. Put `config :tesla, :adapter, {Tesla.Adapter.Finch, name: MyFinch}` in your secrets file to use it. Reverse Proxy will still use Hackney.
-- `ForceMentionsInPostContent` MRF policy
-- PleromaAPI: Add remote follow API endpoint at `POST /api/v1/pleroma/remote_interaction`
-- MastoAPI: Add `GET /api/v1/accounts/lookup`
-- MastoAPI: Profile Directory support
-- MastoAPI: Support v2 Suggestions (handpicked accounts only)
-- Ability to log slow Ecto queries by configuring `:pleroma, :telemetry, :slow_queries_logging`
-- Added Phoenix LiveDashboard at `/phoenix/live_dashboard`
-- Added `/manifest.json` for progressive web apps.
-- MastoAPI: Support for `birthday` and `show_birthday` field in `/api/v1/accounts/update_credentials`.
-- Configuration: Add `birthday_required` and `birthday_min_age` settings to provide a way to require users to enter their birth date.
-- PleromaAPI: Add `GET /api/v1/pleroma/birthdays` API endpoint
-- Make backend-rendered pages translatable. This includes emails. Pages returned as a HTTP response are translated using the language specified in the `userLanguage` cookie, or the `Accept-Language` header. Emails are translated using the `language` field when registering. This language can be changed by `PATCH /api/v1/accounts/update_credentials` with the `language` field.
-- Add fine grained options to provide privileges to moderators and admins (e.g. delete messages, manage reports...)
-- Uploadfilter `Pleroma.Upload.Filter.Exiftool.ReadDescription` returns description values to the FE so they can pre fill the image description field
-- Added move account API
-- Enable remote users to interact with posts
-- Possibility to discover users like `user@example.org`, while Pleroma is working on `pleroma.example.org`. Additional configuration required.
-
-### Fixed
-- Subscription(Bell) Notifications: Don't create from Pipeline Ingested replies
-- Handle Reject for already-accepted Follows properly
-- Display OpenGraph data on alternative notice routes.
-- Fix replies count for remote replies
-- Fixed hashtags disappearing from the end of lines when Markdown is enabled
-- ChatAPI: Add link headers
-- Limited number of search results to 40 to prevent DoS attacks
-- ActivityPub: fixed federation of attachment dimensions
-- Fixed benchmarks
-- Elixir 1.13 support
-- Fixed crash when pinned_objects is nil
-- Fixed slow timelines when there are a lot of deactivated users
-- Fixed account deletion API
-- Fixed lowercase HTTP HEAD method in the Media Proxy Preview code
-- Removed useless notification call on Delete activities
-- Improved performance for filtering out deactivated and invisible users
-- RSS and Atom feeds for users work again
-- TwitterCard meta tags conformance
-
-## 2.4.5 - 2022-11-27
-
-## Fixed
-- Image `class` attributes not being scrubbed, allowing to exploit frontend special classes [!3792](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3792)
-- Delete report notifs when demoting from superuser [!3642](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3642)
-- Validate `mediaType` only by it's format rather than using a list [!3597](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3597)
-- Pagination: Make mutes and blocks lists behave the same as other lists [!3693](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3693)
-- Compatibility with Elixir 1.14 [!3740](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3740)
-- Frontend installer: FediFE build URL [!3736](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3736)
-- Streaming: Don't stream ChatMessage into the home timeline [!3738](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3738)
-- Streaming: Stream local-only posts in the local timeline [!3738](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3738)
-- Signatures: Fix `keyId` lookup for GoToSocial [!3725](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3725)
-- Validator: Fix `replies` handling for GoToSocial [!3725](https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3725)
-
-## 2.4.4 - 2022-08-19
-
-### Security
-- Streaming API sessions will now properly disconnect if the corresponding token is revoked
-
-## 2.4.3 - 2022-05-06
-
-### Security
-- Private `/objects/` and `/activities/` leaking if cached by authenticated user
-- SweetXML library DTD bomb
-
-## 2.4.2 - 2022-01-10
-
-### Fixed
-- Federation issues caused by HTTP pool checkout timeouts
-- Compatibility with Elixir 1.13
-
-### Upgrade notes
-
-1. Restart Pleroma
-
-## 2.4.1 - 2021-08-29
-
-### Changed
-- Make `mix pleroma.database set_text_search_config` run concurrently and indefinitely
-
-### Added
-- AdminAPI: Missing configuration description for StealEmojiPolicy
-
-### Fixed
-- MastodonAPI: Stream out Create activities
-- MRF ObjectAgePolicy: Fix pattern matching on "published"
-- TwitterAPI: Make `change_password` and `change_email` require params on body instead of query
-- Subscription(Bell) Notifications: Don't create from Pipeline Ingested replies
-- AdminAPI: Fix rendering reports containing a `nil` object
-- Mastodon API: Activity Search fallbacks on status fetching after a DB Timeout/Error
-- Mastodon API: Fix crash in Streamer related to reblogging
-- AdminAPI: List available frontends when `static/frontends` folder is missing
-- Make activity search properly use language-aware GIN indexes
-- AdminAPI: Fix suggestions for MRF Policies
-
-## 2.4.0 - 2021-08-08
-
-### Changed
-
-- **Breaking:** Configuration: `:chat, enabled` moved to `:shout, enabled` and `:instance, chat_limit` moved to `:shout, limit`
-- **Breaking** Entries for simple_policy, transparency_exclusions and quarantined_instances now list both the instance and a reason.
-- Support for Erlang/OTP 24
-- The `application` metadata returned with statuses is no longer hardcoded. Apps that want to display these details will now have valid data for new posts after this change.
-- HTTPSecurityPlug now sends a response header to opt out of Google's FLoC (Federated Learning of Cohorts) targeted advertising.
-- Email address is now returned if requesting user is the owner of the user account so it can be exposed in client and FE user settings UIs.
-- Improved Twittercard and OpenGraph meta tag generation including thumbnails and image dimension metadata when available.
-- AdminAPI: sort users so the newest are at the top.
-- ActivityPub Client-to-Server(C2S): Limitation on the type of Activity/Object are lifted as they are now passed through ObjectValidators
-- MRF (`AntiFollowbotPolicy`): Bot accounts are now also considered followbots. Users can still allow bots to follow them by first following the bot.
-
-### Added
-
-- MRF (`FollowBotPolicy`): New MRF Policy which makes a designated local Bot account attempt to follow all users in public Notes received by your instance. Users who require approving follower requests or have #nobot in their profile are excluded.
-- Return OAuth token `id` (primary key) in POST `/oauth/token`.
-- AdminAPI: return `created_at` date with users.
-- AdminAPI: add DELETE `/api/v1/pleroma/admin/instances/:instance` to delete all content from a remote instance.
-- `AnalyzeMetadata` upload filter for extracting image/video attachment dimensions and generating blurhashes for images. Blurhashes for videos are not generated at this time.
-- Attachment dimensions and blurhashes are federated when available.
-- Mastodon API: support `poll` notification.
-- Pinned posts federation
-
-### Fixed
-- Don't crash so hard when email settings are invalid.
-- Checking activated Upload Filters for required commands.
-- Remote users can no longer reappear after being deleted.
-- Deactivated users may now be deleted.
-- Deleting an activity with a lot of likes/boosts no longer causes a database timeout.
-- Mix task `pleroma.database prune_objects`
-- Fixed rendering of JSON errors on ActivityPub endpoints.
-- Linkify: Parsing crash with URLs ending in unbalanced closed paren, no path separator, and no query parameters
-- Try to save exported ConfigDB settings (migrate_from_db) in the system temp directory if default location is not writable.
-- Uploading custom instance thumbnail via AdminAPI/AdminFE generated invalid URL to the image
-- Applying ConcurrentLimiter settings via AdminAPI
-- User login failures if their `notification_settings` were in a NULL state.
-- Mix task `pleroma.user delete_activities` query transaction timeout is now :infinity
-- MRF (`SimplePolicy`): Embedded objects are now checked. If any embedded object would be rejected, its parent is rejected. This fixes Announces leaking posts from blocked domains.
-- Fixed some Markdown issues, including trailing slash in links.
-
-### Removed
-- **Breaking**: Remove deprecated `/api/qvitter/statuses/notifications/read` (replaced by `/api/v1/pleroma/notifications/read`)
-
-## [2.3.0] - 2021-03-01
-
-### Security
-
-- Fixed client user agent leaking through MediaProxy
-
-### Removed
-
-- `:auth, :enforce_oauth_admin_scope_usage` configuration option.
-
-### Changed
-
-- **Breaking**: Changed `mix pleroma.user toggle_confirmed` to `mix pleroma.user confirm`
-- **Breaking**: Changed `mix pleroma.user toggle_activated` to `mix pleroma.user activate/deactivate`
-- **Breaking:** NSFW hashtag is no longer added on sensitive posts
-- Polls now always return a `voters_count`, even if they are single-choice.
-- Admin Emails: The ap id is used as the user link in emails now.
-- Improved registration workflow for email confirmation and account approval modes.
-- Search: When using Postgres 11+, Pleroma will use the `websearch_to_tsvector` function to parse search queries.
-- Emoji: Support the full Unicode 13.1 set of Emoji for reactions, plus regional indicators.
-- Deprecated `Pleroma.Uploaders.S3, :public_endpoint`. Now `Pleroma.Upload, :base_url` is the standard configuration key for all uploaders.
-- Improved Apache webserver support: updated sample configuration, MediaProxy cache invalidation verified with the included sample script
-- Improve OAuth 2.0 provider support. A missing `fqn` field was added to the response, but does not expose the user's email address.
-- Provide redirect of external posts from `/notice/:id` to their original URL
-- Admins no longer receive notifications for reports if they are the actor making the report.
-- Improved Mailer configuration setting descriptions for AdminFE.
-- Updated default avatar to look nicer.
-
-<details>
-  <summary>API Changes</summary>
-
-- **Breaking:** AdminAPI changed User field `confirmation_pending` to `is_confirmed`
-- **Breaking:** AdminAPI changed User field `approval_pending` to `is_approved`
-- **Breaking**: AdminAPI changed User field `deactivated` to `is_active`
-- **Breaking:** AdminAPI `GET /api/pleroma/admin/users/:nickname_or_id/statuses` changed response format and added the number of total users posts.
-- **Breaking:** AdminAPI `GET /api/pleroma/admin/instances/:instance/statuses` changed response format and added the number of total users posts.
-- Admin API: Reports now ordered by newest
-- Pleroma API: `GET /api/v1/pleroma/chats` is deprecated in favor of `GET /api/v2/pleroma/chats`.
-- Pleroma API: Reroute `/api/pleroma/*` to `/api/v1/pleroma/*`
-
-</details>
-- Improved hashtag timeline performance (requires a background migration).
-
-### Added
-
-- Reports now generate notifications for admins and mods.
-- Support for local-only statuses.
-- Support pagination of blocks and mutes.
-- Account backup.
-- Configuration: Add `:instance, autofollowing_nicknames` setting to provide a way to make accounts automatically follow new users that register on the local Pleroma instance.
-- `[:activitypub, :blockers_visible]` config to control visibility of blockers.
-- Ability to view remote timelines, with ex. `/api/v1/timelines/public?instance=lain.com` and streams `public:remote` and `public:remote:media`.
-- The site title is now injected as a `title` tag like preloads or metadata.
-- Password reset tokens now are not accepted after a certain age.
-- Mix tasks to help with displaying and removing ConfigDB entries. See `mix pleroma.config`.
-- OAuth form improvements: users are remembered by their cookie, the CSS is overridable by the admin, and the style has been improved.
-- OAuth improvements and fixes: more secure session-based authentication (by token that could be revoked anytime), ability to revoke belonging OAuth token from any client etc.
-- Ability to set ActivityPub aliases for follower migration.
-- Configurable background job limits for RichMedia (link previews) and MediaProxyWarmingPolicy
-- Ability to define custom HTTP headers per each frontend
-- MRF (`NoEmptyPolicy`): New MRF Policy which will deny empty statuses or statuses of only mentions from being created by local users
-- New users will receive a simple email confirming their registration if no other emails will be dispatched. (e.g., Welcome, Confirmation, or Approval Required)
-
-<details>
-  <summary>API Changes</summary>
-- Admin API: (`GET /api/pleroma/admin/users`) filter users by `unconfirmed` status and `actor_type`.
-- Admin API: OpenAPI spec for the user-related operations
-- Pleroma API: `GET /api/v2/pleroma/chats` added. It is exactly like `GET /api/v1/pleroma/chats` except supports pagination.
-- Pleroma API: Add `idempotency_key` to the chat message entity that can be used for optimistic message sending.
-- Pleroma API: (`GET /api/v1/pleroma/federation_status`) Add a way to get a list of unreachable instances.
-- Mastodon API: User and conversation mutes can now auto-expire if `expires_in` parameter was given while adding the mute.
-- Admin API: An endpoint to manage frontends.
-- Streaming API: Add follow relationships updates.
-- WebPush: Introduce `pleroma:chat_mention` and `pleroma:emoji_reaction` notification types.
-- Mastodon API: Add monthly active users to `/api/v1/instance` (`pleroma.stats.mau`).
-- Mastodon API: Home, public, hashtag & list timelines accept `only_media`, `remote` & `local` parameters for filtration.
-- Mastodon API: `/api/v1/accounts/:id` & `/api/v1/mutes` endpoints accept `with_relationships` parameter and return filled `pleroma.relationship` field.
-- Mastodon API: Endpoint to remove a conversation (`DELETE /api/v1/conversations/:id`).
-- Mastodon API: `expires_in` in the scheduled post `params` field on `/api/v1/statuses` and `/api/v1/scheduled_statuses/:id` endpoints.
-</details>
-
-### Fixed
-
-- Users with `is_discoverable` field set to false (default value) will appear in in-service search results but be hidden from external services (search bots etc.).
-- Streaming API: Posts and notifications are not dropped, when CLI task is executing.
-- Creating incorrect IPv4 address-style HTTP links when encountering certain numbers.
-- Reblog API Endpoint: Do not set visibility parameter to public by default and let CommonAPI to infer it from status, so a user can reblog their private status without explicitly setting reblog visibility to private.
-- Tag URLs in statuses are now absolute
-- Removed duplicate jobs to purge expired activities
-- File extensions of some attachments were incorrectly changed. This feature has been disabled for now.
-- Mix task pleroma.instance creates missing parent directories if the configuration or SQL output paths are changed.
-
-<details>
-  <summary>API Changes</summary>
-  - Mastodon API: Current user is now included in conversation if it's the only participant.
-  - Mastodon API: Fixed last_status.account being not filled with account data.
-  - Mastodon API: Fix not being able to add or remove multiple users at once in lists.
-  - Mastodon API: Fixed own_votes being not returned with poll data.
-  - Mastodon API: Fixed creation of scheduled posts with polls.
-  - Mastodon API: Support for expires_in/expires_at in the Filters.
-</details>
-
-## [2.2.2] - 2021-01-18
-
-### Fixed
-
-- StealEmojiPolicy creates dir for emojis, if it doesn't exist.
-- Updated `elixir_make` to a non-retired version
-
-### Upgrade notes
-
-1. Restart Pleroma
-
-## [2.2.1] - 2020-12-22
-
-### Changed
-- Updated Pleroma FE
-
-### Fixed
-
-- Config generation: rename `Pleroma.Upload.Filter.ExifTool` to `Pleroma.Upload.Filter.Exiftool`.
-- S3 Uploads with Elixir 1.11.
-- Mix task pleroma.user delete_activities for source installations.
-- Search: RUM index search speed has been fixed.
-- Rich Media Previews sometimes showed the wrong preview due to a bug following redirects.
-- Fixes for the autolinker.
-- Forwarded reports duplication from Pleroma instances.
-- Emoji Reaction activity filtering from blocked and muted accounts.
-
-- <details>
-    <summary>API</summary>
-  - Statuses were not displayed for Mastodon forwarded reports.
-  </details>
-
-### Upgrade notes
-
-1. Restart Pleroma
-
-## [2.2.0] - 2020-11-12
-
-### Security
-
-- Fixed the possibility of using file uploads to spoof posts.
-
-### Changed
-
-- **Breaking** Requires `libmagic` (or `file`) to guess file types.
-- **Breaking:** App metrics endpoint (`/api/pleroma/app_metrics`) is disabled by default, check `docs/API/prometheus.md` on enabling and configuring.
-- **Breaking:** Pleroma Admin API: emoji packs and files routes changed.
-- **Breaking:** Sensitive/NSFW statuses no longer disable link previews.
-- Search: Users are now findable by their urls.
-- Renamed `:await_up_timeout` in `:connections_pool` namespace to `:connect_timeout`, old name is deprecated.
-- Renamed `:timeout` in `pools` namespace to `:recv_timeout`, old name is deprecated.
-- The `discoverable` field in the `User` struct will now add a NOINDEX metatag to profile pages when false.
-- Users with the `is_discoverable` field set to false will not show up in searches ([bug](https://git.pleroma.social/pleroma/pleroma/-/issues/2301)).
-- Minimum lifetime for ephmeral activities changed to 10 minutes and made configurable (`:min_lifetime` option).
-- Introduced optional dependencies on `ffmpeg`, `ImageMagick`, `exiftool` software packages. Please refer to `docs/installation/optional/media_graphics_packages.md`.
-- <details>
-  <summary>API Changes</summary>
-- API: Empty parameter values for integer parameters are now ignored in non-strict validaton mode.
-</details>
-
-### Removed
-
-- **Breaking:** `Pleroma.Workers.Cron.StatsWorker` setting from Oban `:crontab` (moved to a simpler implementation).
-- **Breaking:** `Pleroma.Workers.Cron.ClearOauthTokenWorker` setting from Oban `:crontab` (moved to scheduled jobs).
-- **Breaking:** `Pleroma.Workers.Cron.PurgeExpiredActivitiesWorker` setting from Oban `:crontab` (moved to scheduled jobs).
-- Removed `:managed_config` option. In practice, it was accidentally removed with 2.0.0 release when frontends were
-switched to a new configuration mechanism, however it was not officially removed until now.
-
-### Added
-
-- Media preview proxy (requires `ffmpeg` and `ImageMagick` to be installed and media proxy to be enabled; see `:media_preview_proxy` config for more details).
-- Mix tasks for controlling user account confirmation status in bulk (`mix pleroma.user confirm_all` and `mix pleroma.user unconfirm_all`)
-- Mix task for sending confirmation emails to all unconfirmed users (`mix pleroma.email resend_confirmation_emails`)
-- Mix task option for force-unfollowing relays
-- App metrics: ability to restrict access to specified IP whitelist.
-
-<details>
-  <summary>API Changes</summary>
-
-- Admin API: Importing emoji from a zip file
-- Pleroma API: Importing the mutes users from CSV files.
-- Pleroma API: Pagination for remote/local packs and emoji.
-
-</details>
-
-### Fixed
-
-- Add documented-but-missing chat pagination.
-- Allow sending out emails again.
-- Allow sending chat messages to yourself
-- OStatus / static FE endpoints: fixed inaccessibility for anonymous users on non-federating instances, switched to handling per `:restrict_unauthenticated` setting.
-- Fix remote users with a whitespace name.
-
-### Upgrade notes
-
-1. Install libmagic and development headers (`libmagic-dev` on Ubuntu/Debian, `file-dev` on Alpine Linux)
-2. Run database migrations (inside Pleroma directory):
-  - OTP: `./bin/pleroma_ctl migrate`
-  - From Source: `mix ecto.migrate`
-3. Restart Pleroma
-
-## [2.1.2] - 2020-09-17
-
-### Security
-
-- Fix most MRF rules either crashing or not being applied to objects passed into the Common Pipeline (ChatMessage, Question, Answer, Audio, Event).
-
-### Fixed
-
-- Welcome Chat messages preventing user registration with MRF Simple Policy applied to the local instance.
-- Mastodon API: the public timeline returning an error when the `reply_visibility` parameter is set to `self` for an unauthenticated user.
-- Mastodon Streaming API: Handler crashes on authentication failures, resulting in error logs.
-- Mastodon Streaming API: Error logs on client pings.
-- Rich media: Log spam on failures. Now the error is only logged once per attempt.
-
-### Changed
-
-- Rich Media: A HEAD request is now done to the url, to ensure it has the appropriate content type and size before proceeding with a GET.
-
-### Upgrade notes
-
-1. Restart Pleroma
-
 ## [2.1.1] - 2020-09-08
 
 ### Security
@@ -796,12 +18,6 @@ switched to a new configuration mechanism, however it was not officially removed
 ### Added
 - Rich media failure tracking (along with `:failure_backoff` option).
 
-<details>
-  <summary>Admin API Changes</summary>
-
-- Add `PATCH /api/pleroma/admin/instance_document/:document_name` to modify the Terms of Service and Instance Panel HTML pages via Admin API
-</details>
-
 ### Fixed
 - Default HTTP adapter not respecting pool setting, leading to possible OOM.
 - Fixed uploading webp images when the Exiftool Upload Filter is enabled by skipping them
@@ -1054,10 +270,11 @@ switched to a new configuration mechanism, however it was not officially removed
 - Static-FE: Fix remote posts not being sanitized
 
 ### Fixed
+=======
 - Rate limiter crashes when there is no explicitly specified ip in the config
 - 500 errors when no `Accept` header is present if Static-FE is enabled
 - Instance panel not being updated immediately due to wrong `Cache-Control` headers
-- Statuses posted with BBCode/Markdown having unnecessary newlines in Pleroma-FE
+- Statuses posted with BBCode/Markdown having unncessary newlines in Pleroma-FE
 - OTP: Fix some settings not being migrated to in-database config properly
 - No `Cache-Control` headers on attachment/media proxy requests
 - Character limit enforcement being off by 1
@@ -1377,10 +594,10 @@ curl -Lo ./bin/pleroma_ctl 'https://git.pleroma.social/pleroma/pleroma/raw/devel
 - Reverse Proxy limiting `max_body_length` was incorrectly defined and only checked `Content-Length` headers which may not be sufficient in some circumstances
 
 ### Added
-- Expiring/ephemeral activities. All activities can have expires_at value set, which controls when they should be deleted automatically.
+- Expiring/ephemeral activites. All activities can have expires_at value set, which controls when they should be deleted automatically.
 - Mastodon API: in post_status, the expires_in parameter lets you set the number of seconds until an activity expires. It must be at least one hour.
 - Mastodon API: all status JSON responses contain a `pleroma.expires_at` item which states when an activity will expire. The value is only shown to the user who created the activity. To everyone else it's empty.
-- Configuration: `ActivityExpiration.enabled` controls whether expired activities will get deleted at the appropriate time. Enabled by default.
+- Configuration: `ActivityExpiration.enabled` controls whether expired activites will get deleted at the appropriate time. Enabled by default.
 - Conversations: Add Pleroma-specific conversation endpoints and status posting extensions. Run the `bump_all_conversations` task again to create the necessary data.
 - MRF: Support for priming the mediaproxy cache (`Pleroma.Web.ActivityPub.MRF.MediaProxyWarmingPolicy`)
 - MRF: Support for excluding specific domains from Transparency.

COPYING

@@ -1,17 +1,10 @@
-Unless otherwise stated this repository is copyright © 2017-2022
+Unless otherwise stated this repository is copyright © 2017-2020
 Pleroma Authors <https://pleroma.social/>, and is distributed under
 The GNU Affero General Public License Version 3, you should have received a
 copy of the license file as AGPL-3.
 
 ---
 
-Files inside docs directory are copyright © 2022 Pleroma Authors
-<https://pleroma.social/>, and are distributed under the Creative Commons
-Attribution 4.0 International license, you should have received
-a copy of the license file as CC-BY-4.0.
-
----
-
 The following files are copyright © 2019 shitposter.club, and are distributed
 under the Creative Commons Attribution-ShareAlike 4.0 International license,
 you should have received a copy of the license file as CC-BY-SA-4.0.
@@ -30,7 +23,7 @@ priv/static/images/pleroma-fox-tan-shy.png
 
 ---
 
-The following files are copyright © 2017-2022 Pleroma Authors
+The following files are copyright © 2017-2020 Pleroma Authors
 <https://pleroma.social/>, and are distributed under the Creative Commons
 Attribution-ShareAlike 4.0 International license, you should have received
 a copy of the license file as CC-BY-SA-4.0.

Dockerfile

@@ -1,25 +1,18 @@
-# https://hub.docker.com/r/hexpm/elixir/tags
-ARG ELIXIR_IMG=hexpm/elixir
-ARG ELIXIR_VER=1.14.5
-ARG ERLANG_VER=25.3.2.14
-ARG ALPINE_VER=3.17.9
-
-FROM ${ELIXIR_IMG}:${ELIXIR_VER}-erlang-${ERLANG_VER}-alpine-${ALPINE_VER} as build
+FROM elixir:1.9-alpine as build
 
 COPY . .
 
 ENV MIX_ENV=prod
-ENV VIX_COMPILATION_MODE=PLATFORM_PROVIDED_LIBVIPS
 
-RUN apk add git gcc g++ musl-dev make cmake file-dev vips-dev &&\
-	echo "import Config" > config/prod.secret.exs &&\
+RUN apk add git gcc g++ musl-dev make cmake &&\
+	echo "import Mix.Config" > config/prod.secret.exs &&\
 	mix local.hex --force &&\
 	mix local.rebar --force &&\
 	mix deps.get --only prod &&\
 	mkdir release &&\
 	mix release --path release
 
-FROM alpine:${ALPINE_VER}
+FROM alpine:3.11
 
 ARG BUILD_DATE
 ARG VCS_REF
@@ -38,8 +31,9 @@ LABEL maintainer="ops@pleroma.social" \
 ARG HOME=/opt/pleroma
 ARG DATA=/var/lib/pleroma
 
-RUN apk update &&\
-	apk add exiftool ffmpeg vips libmagic ncurses postgresql-client &&\
+RUN echo "http://nl.alpinelinux.org/alpine/latest-stable/community" >> /etc/apk/repositories &&\
+	apk update &&\
+	apk add exiftool imagemagick ncurses postgresql-client &&\
 	adduser --system --shell /bin/false --home ${HOME} pleroma &&\
 	mkdir -p ${DATA}/uploads &&\
 	mkdir -p ${DATA}/static &&\
@@ -51,7 +45,7 @@ USER pleroma
 
 COPY --from=build --chown=pleroma:0 /release ${HOME}
 
-COPY --chown=pleroma --chmod=640 ./config/docker.exs /etc/pleroma/config.exs
+COPY ./config/docker.exs /etc/pleroma/config.exs
 COPY ./docker-entrypoint.sh ${HOME}
 
 EXPOSE 4000

README.md

@@ -18,27 +18,22 @@ If you are running Linux (glibc or musl) on x86/arm, the recommended way to inst
 ### From Source
 If your platform is not supported, or you just want to be able to edit the source code easily, you may install Pleroma from source.
 
-- [Alpine Linux](https://docs-develop.pleroma.social/backend/installation/alpine_linux_en/)
-- [Arch Linux](https://docs-develop.pleroma.social/backend/installation/arch_linux_en/)
-- [CentOS 7](https://docs-develop.pleroma.social/backend/installation/centos7_en/)
 - [Debian-based](https://docs-develop.pleroma.social/backend/installation/debian_based_en/)
 - [Debian-based (jp)](https://docs-develop.pleroma.social/backend/installation/debian_based_jp/)
-- [FreeBSD](https://docs-develop.pleroma.social/backend/installation/freebsd_en/)
+- [Alpine Linux](https://docs-develop.pleroma.social/backend/installation/alpine_linux_en/)
+- [Arch Linux](https://docs-develop.pleroma.social/backend/installation/arch_linux_en/)
 - [Gentoo Linux](https://docs-develop.pleroma.social/backend/installation/gentoo_en/)
 - [NetBSD](https://docs-develop.pleroma.social/backend/installation/netbsd_en/)
 - [OpenBSD](https://docs-develop.pleroma.social/backend/installation/openbsd_en/)
 - [OpenBSD (fi)](https://docs-develop.pleroma.social/backend/installation/openbsd_fi/)
+- [CentOS 7](https://docs-develop.pleroma.social/backend/installation/centos7_en/)
 
 ### OS/Distro packages
-Currently Pleroma is packaged for [YunoHost](https://yunohost.org), [NixOS](https://nixos.org), [Gentoo through GURU](https://gentoo.org/) and [Archlinux through AUR](https://aur.archlinux.org/packages/pleroma). You may find more at <https://repology.org/project/pleroma/versions>.  
-If you want to package Pleroma for any OS/Distros, we can guide you through the process on our [community channels](#community-channels). If you want to change default options in your Pleroma package, please **discuss it with us first**.
+Currently Pleroma is not packaged by any OS/Distros, but if you want to package it for one, we can guide you through the process on our [community channels](#community-channels). If you want to change default options in your Pleroma package, please **discuss it with us first**.
 
 ### Docker
 While we don’t provide docker files, other people have written very good ones. Take a look at <https://github.com/angristan/docker-pleroma> or <https://glitch.sh/sn0w/pleroma-docker>.
 
-### Raspberry Pi
-Community maintained Raspberry Pi image that you can flash and run Pleroma on your Raspberry Pi. Available here <https://github.com/guysoft/PleromaPi>.
-
 ### Compilation Troubleshooting
 If you ever encounter compilation issues during the updating of Pleroma, you can try these commands and see if they fix things:
 
@@ -54,5 +49,5 @@ If you are not developing Pleroma, it is better to use the OTP release, which co
 - Latest Git revision: <https://docs-develop.pleroma.social>
 
 ## Community Channels
-* IRC: **#pleroma** and **#pleroma-dev** on libera.chat, webchat is available at <https://irc.pleroma.social>
-* Matrix: [#pleroma:libera.chat](https://matrix.to/#/#pleroma:libera.chat) and [#pleroma-dev:libera.chat](https://matrix.to/#/#pleroma-dev:libera.chat)
+* IRC: **#pleroma** and **#pleroma-dev** on freenode, webchat is available at <https://irc.pleroma.social>
+* Matrix: <https://matrix.to/#/#freenode_#pleroma:matrix.org> and <https://matrix.to/#/#freenode_#pleroma-dev:matrix.org>

SECURITY.md

@@ -6,7 +6,7 @@ Currently, Pleroma offers bugfixes and security patches only for the latest mino
 
 | Version | Support 
 |---------| --------
-| 2.2     | Bugfixes and security patches
+| 2.0     | Bugfixes and security patches
 
 ## Reporting a vulnerability
 

benchmarks/load_testing/activities.ex

@@ -299,7 +299,7 @@ defmodule Pleroma.LoadTesting.Activities do
       "url" => [
         %{
           "href" =>
-            "#{Pleroma.Web.Endpoint.url()}/media/b1b873552422a07bf53af01f3c231c841db4dfc42c35efde681abaf0f2a4eab7.jpg",
+            "#{Pleroma.Web.base_url()}/media/b1b873552422a07bf53af01f3c231c841db4dfc42c35efde681abaf0f2a4eab7.jpg",
           "mediaType" => "image/jpeg",
           "type" => "Link"
         }
@@ -394,7 +394,7 @@ defmodule Pleroma.LoadTesting.Activities do
 
   defp other_data(actor, content) do
     %{host: host} = URI.parse(actor.ap_id)
-    datetime = DateTime.utc_now() |> to_string()
+    datetime = DateTime.utc_now()
     context_id = "https://#{host}/contexts/#{UUID.generate()}"
     activity_id = "https://#{host}/activities/#{UUID.generate()}"
     object_id = "https://#{host}/objects/#{UUID.generate()}"

benchmarks/load_testing/fetcher.ex

@@ -33,11 +33,10 @@ defmodule Pleroma.LoadTesting.Fetcher do
   end
 
   defp create_filter(user) do
-    Pleroma.Filter.create(%{
+    Pleroma.Filter.create(%Pleroma.Filter{
       user_id: user.id,
       phrase: "must be filtered",
-      hide: true,
-      context: ["home"]
+      hide: true
     })
   end
 

benchmarks/load_testing/users.ex

@@ -55,7 +55,7 @@ defmodule Pleroma.LoadTesting.Users do
       name: "Test テスト User #{i}",
       email: "user#{i}@example.com",
       nickname: "nick#{i}",
-      password_hash: Pleroma.Password.Pbkdf2.hash_pwd_salt("test"),
+      password_hash: Pbkdf2.hash_pwd_salt("test"),
       bio: "Tester Number #{i}",
       local: !remote
     }
@@ -109,8 +109,8 @@ defmodule Pleroma.LoadTesting.Users do
   end
 
   def make_friends(%User{} = main_user, %User{} = user) do
-    {:ok, _, _} = User.follow(main_user, user)
-    {:ok, _, _} = User.follow(user, main_user)
+    {:ok, _} = User.follow(main_user, user)
+    {:ok, _} = User.follow(user, main_user)
   end
 
   @spec get_users(User.t(), keyword()) :: [User.t()]

benchmarks/mix/tasks/pleroma/benchmarks/tags.ex

@@ -99,16 +99,15 @@ defmodule Mix.Tasks.Pleroma.Benchmarks.Tags do
       |> Enum.map(&String.downcase(&1))
 
     _activities =
-      %{
-        type: "Create",
-        local_only: local_only,
-        blocking_user: user,
-        muting_user: user,
-        user: user,
-        tag: tags,
-        tag_all: tag_all,
-        tag_reject: tag_reject,
-      }
+      params
+      |> Map.put(:type, "Create")
+      |> Map.put(:local_only, local_only)
+      |> Map.put(:blocking_user, user)
+      |> Map.put(:muting_user, user)
+      |> Map.put(:user, user)
+      |> Map.put(:tag, tags)
+      |> Map.put(:tag_all, tag_all)
+      |> Map.put(:tag_reject, tag_reject)
       |> Pleroma.Web.ActivityPub.ActivityPub.fetch_public_activities()
   end
 end

benchmarks/mix/tasks/pleroma/benchmarks/timelines.ex

@@ -17,14 +17,14 @@ defmodule Mix.Tasks.Pleroma.Benchmarks.Timelines do
     # Let the user make 100 posts
 
     1..100
-    |> Enum.each(fn i -> CommonAPI.post(user, %{status: to_string(i)}) end)
+    |> Enum.each(fn i -> CommonAPI.post(user, %{"status" => to_string(i)}) end)
 
     # Let 10 random users post
     posts =
       users
       |> Enum.take_random(10)
       |> Enum.map(fn {:ok, random_user} ->
-        {:ok, activity} = CommonAPI.post(random_user, %{status: "."})
+        {:ok, activity} = CommonAPI.post(random_user, %{"status" => "."})
         activity
       end)
 
@@ -42,7 +42,7 @@ defmodule Mix.Tasks.Pleroma.Benchmarks.Timelines do
             |> Conn.assign(:user, reading_user)
             |> Conn.assign(:skip_link_headers, true)
 
-          Pleroma.Web.MastodonAPI.AccountController.statuses(conn, %{id: user.id})
+          Pleroma.Web.MastodonAPI.AccountController.statuses(conn, %{"id" => user.id})
         end
       },
       inputs: %{"user" => user, "no user" => nil},
@@ -60,7 +60,7 @@ defmodule Mix.Tasks.Pleroma.Benchmarks.Timelines do
             |> Conn.assign(:user, reading_user)
             |> Conn.assign(:skip_link_headers, true)
 
-          Pleroma.Web.MastodonAPI.AccountController.statuses(conn, %{id: user.id})
+          Pleroma.Web.MastodonAPI.AccountController.statuses(conn, %{"id" => user.id})
         end
       },
       inputs: %{"user" => user, "no user" => nil},

changelog.d/activity_type_index.change

@@ -1 +0,0 @@
-Add new activity actor/type index. Greatly speeds up retrieval of rare types (like "Listen")

changelog.d/emoji_likes.add

@@ -1 +0,0 @@
-Support Mitra-style emoji likes.

changelog.d/freebsd-rc.fix

@@ -1 +0,0 @@
-Set PATH in the FreeBSD rc script to avoid failures starting the service

changelog.d/gin-search.fix

@@ -1 +0,0 @@
-Improved performance of status search queries using the default GIN index

changelog.d/language-detection.add

@@ -1 +0,0 @@
-Implement language detection with fastText

changelog.d/releases.fix

@@ -1 +0,0 @@
-Fix release builds

changelog.d/siteinfo-baseurls.add

@@ -1 +0,0 @@
-Add `base_urls` to the /api/v1/instance pleroma metadata which provides information about the base URLs for media_proxy and uploads when configured

changelog.d/translate-posts.add

@@ -1 +0,0 @@
-Support translation providers (DeepL, LibreTranslate)

changelog.d/truncate-rich-media.change

@@ -1 +0,0 @@
-Truncate the length of Rich Media title and description fields

ci/README

@@ -1,12 +0,0 @@
-## Dependencies
-
-Assuming an AMD64 Alpine system, you're going to need the following packages
-- `qemu qemu-openrc qemu-arm qemu-aarch64` for binfmt
-- `docker-cli-buildx` for building the images
-
-## Setting up
-
-```
-docker login git.pleroma.social:5050
-doas rc-service qemu-binfmt start
-```

ci/elixir-1.14.5-otp-25/Dockerfile

@@ -1,8 +0,0 @@
-FROM elixir:1.14.5-otp-25
-
-# Single RUN statement, otherwise intermediate images are created
-# https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#run
-RUN apt-get update &&\
-	apt-get install -y libmagic-dev cmake libimage-exiftool-perl ffmpeg &&\
-	mix local.hex --force &&\
-	mix local.rebar --force

ci/elixir-1.14.5-otp-25/build_and_push.sh

@@ -1 +0,0 @@
-docker buildx build --platform linux/amd64,linux/arm64 -t git.pleroma.social:5050/pleroma/pleroma/ci-base:elixir-1.14.5-otp-25 --push .

ci/elixir-1.15.8-otp-26/Dockerfile

@@ -1,8 +0,0 @@
-FROM elixir:1.15.8-otp-26
-
-# Single RUN statement, otherwise intermediate images are created
-# https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#run
-RUN apt-get update &&\
-	apt-get install -y libmagic-dev cmake libimage-exiftool-perl ffmpeg &&\
-	mix local.hex --force &&\
-	mix local.rebar --force

ci/elixir-1.15.8-otp-26/build_and_push.sh

@@ -1 +0,0 @@
-docker buildx build --platform linux/amd64,linux/arm64 -t git.pleroma.social:5050/pleroma/pleroma/ci-base:elixir-1.15.8-otp-26 --push .

ci/elixir-1.16.3-otp-26/Dockerfile

@@ -1,8 +0,0 @@
-FROM elixir:1.16.3-otp-26
-
-# Single RUN statement, otherwise intermediate images are created
-# https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#run
-RUN apt-get update &&\
-	apt-get install -y libmagic-dev cmake libimage-exiftool-perl ffmpeg &&\
-	mix local.hex --force &&\
-	mix local.rebar --force

ci/elixir-1.16.3-otp-26/build_and_push.sh

@@ -1 +0,0 @@
-docker buildx build --platform linux/amd64,linux/arm64 -t git.pleroma.social:5050/pleroma/pleroma/ci-base:elixir-1.16.3-otp-26 --push .

ci/elixir-1.17.1-otp-26/Dockerfile

@@ -1,8 +0,0 @@
-FROM elixir:1.17.1-otp-26
-
-# Single RUN statement, otherwise intermediate images are created
-# https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#run
-RUN apt-get update &&\
-	apt-get install -y libmagic-dev cmake libimage-exiftool-perl ffmpeg &&\
-	mix local.hex --force &&\
-	mix local.rebar --force

ci/elixir-1.17.1-otp-26/build_and_push.sh

@@ -1 +0,0 @@
-docker buildx build --platform linux/amd64,linux/arm64 -t git.pleroma.social:5050/pleroma/pleroma/ci-base:elixir-1.17.1-otp-26 --push .

ci/postgres-with-rum-13/Dockerfile

@@ -1,3 +0,0 @@
-FROM postgres:13-bullseye
-
-RUN apt-get update && apt-get install -y postgresql-13-rum/bullseye-pgdg

ci/postgres-with-rum-13/build_and_push.sh

@@ -1 +0,0 @@
-docker buildx build --platform linux/amd64,linux/arm64 -t git.pleroma.social:5050/pleroma/pleroma/postgres-with-rum-13:latest --push .

config/benchmark.exs

@@ -1,10 +1,11 @@
-import Config
+use Mix.Config
 
 # We don't run a server during test. If one is required,
 # you can enable the server option below.
 config :pleroma, Pleroma.Web.Endpoint,
   http: [port: 4001],
-  url: [port: 4001]
+  url: [port: 4001],
+  server: true
 
 # Disable captha for tests
 config :pleroma, Pleroma.Captcha,
@@ -14,7 +15,7 @@ config :pleroma, Pleroma.Captcha,
   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: []
 
@@ -40,11 +41,10 @@ config :pleroma, Pleroma.Repo,
   password: "postgres",
   database: "pleroma_benchmark",
   hostname: System.get_env("DB_HOST") || "localhost",
-  port: System.get_env("DB_PORT") || "5432",
   pool_size: 10
 
 # Reduce hash rounds for testing
-config :pleroma, :password, iterations: 1
+config :pbkdf2_elixir, rounds: 1
 
 config :tesla, adapter: Tesla.Mock
 
@@ -59,6 +59,8 @@ config :web_push_encryption, :vapid_details,
     "BLH1qVhJItRGCfxgTtONfsOKDc9VRAraXw-3NsmjMngWSh7NxOizN6bkuRA7iLTMPS82PjwJAr3UoK9EC1IFrz4",
   private_key: "_-XZ0iebPrRfZ_o0-IatTdszYa8VCH1yLN-JauK7HHA"
 
+config :web_push_encryption, :http_client, Pleroma.Web.WebPushHttpClientMock
+
 config :pleroma, Pleroma.ScheduledActivity,
   daily_user_limit: 2,
   total_user_limit: 3,
@@ -79,10 +81,6 @@ IO.puts("RUM enabled: #{rum_enabled}")
 
 config :pleroma, Pleroma.ReverseProxy.Client, Pleroma.ReverseProxy.ClientMock
 
-config :pleroma, Pleroma.Application,
-  background_migrators: false,
-  streamer_registry: false
-
 if File.exists?("./config/benchmark.secret.exs") do
   import_config "benchmark.secret.exs"
 else

config/config.exs

@@ -37,18 +37,19 @@
 # FIGURATION! EDIT YOUR SECRET FILE (either prod.secret.exs, dev.secret.exs).
 #
 # This file is responsible for configuring your application
-# and its dependencies with the aid of the Config module.
+# and its dependencies with the aid of the Mix.Config module.
 #
 # This configuration file is loaded before any dependency and
 # is restricted to this project.
-import Config
+use Mix.Config
 
 # General application configuration
 config :pleroma, ecto_repos: [Pleroma.Repo]
 
 config :pleroma, Pleroma.Repo,
+  types: Pleroma.PostgresTypes,
   telemetry_event: [Pleroma.Repo.Instrumenter],
-  migration_lock: :pg_advisory_lock
+  migration_lock: nil
 
 config :pleroma, Pleroma.Captcha,
   enabled: true,
@@ -63,29 +64,23 @@ config :pleroma, Pleroma.Upload,
   filters: [Pleroma.Upload.Filter.Dedupe],
   link_name: false,
   proxy_remote: false,
+  proxy_opts: [
+    redirect_on_failure: false,
+    max_body_length: 25 * 1_048_576,
+    http: [
+      follow_redirect: true,
+      pool: :upload
+    ]
+  ],
   filename_display_max_length: 30,
-  default_description: nil,
-  base_url: nil,
-  allowed_mime_types: ["image", "audio", "video"]
+  default_description: nil
 
 config :pleroma, Pleroma.Uploaders.Local, uploads: "uploads"
 
 config :pleroma, Pleroma.Uploaders.S3,
   bucket: nil,
-  bucket_namespace: nil,
-  truncated_namespace: nil,
-  streaming_enabled: true
-
-config :ex_aws, :s3,
-  # host: "s3.wasabisys.com", # required if not Amazon AWS
-  access_key_id: nil,
-  secret_access_key: nil,
-  # region: "us-east-1", # may be required for Amazon AWS
-  scheme: "https://"
-
-config :pleroma, Pleroma.Uploaders.IPFS,
-  post_gateway_url: "http://localhost:5001",
-  get_gateway_url: "http://localhost:8080"
+  streaming_enabled: true,
+  public_endpoint: "https://s3.amazonaws.com"
 
 config :pleroma, :emoji,
   shortcode_globs: ["/emoji/custom/**/*.png"],
@@ -115,46 +110,67 @@ config :pleroma, :uri_schemes,
     "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,
+  instrumenters: [Pleroma.Web.Endpoint.Instrumenter],
   url: [host: "localhost"],
   http: [
-    ip: {127, 0, 0, 1}
+    ip: {127, 0, 0, 1},
+    dispatch: [
+      {:_,
+       [
+         {"/api/v1/streaming", Pleroma.Web.MastodonAPI.WebsocketHandler, []},
+         {"/websocket", Phoenix.Endpoint.CowboyWebSocket,
+          {Phoenix.Transports.WebSocket,
+           {Pleroma.Web.Endpoint, Pleroma.Web.UserSocket, websocket_config}}},
+         {:_, Phoenix.Endpoint.Cowboy2Handler, {Pleroma.Web.Endpoint, []}}
+       ]}
+    ]
   ],
   protocol: "https",
   secret_key_base: "aK4Abxf29xU9TTDKre9coZPUgevcVCFQJe/5xP/7Lt4BEif6idBIbjupVbOrbKxl",
-  live_view: [signing_salt: "U5ELgdEwTD3n1+D5s0rY0AMg8/y1STxZ3Zvsl3bWh+oBcGrYdil0rXqPMRd3Glcq"],
   signing_salt: "CqaoopA2",
   render_errors: [view: Pleroma.Web.ErrorView, accepts: ~w(json)],
-  pubsub_server: Pleroma.PubSub,
+  pubsub: [name: Pleroma.PubSub, adapter: Phoenix.PubSub.PG2],
   secure_cookie_flag: true,
   extra_cookie_attrs: [
     "SameSite=Lax"
   ]
 
 # Configures Elixir's Logger
-config :logger, backends: [:console]
-
 config :logger, :console,
   level: :debug,
   format: "\n$time $metadata[$level] $message\n",
-  metadata: [:actor, :path, :type, :user]
+  metadata: [:request_id]
 
 config :logger, :ex_syslogger,
   level: :debug,
   ident: "pleroma",
   format: "$metadata[$level] $message",
-  metadata: [:actor, :path, :type, :user]
+  metadata: [:request_id]
+
+config :quack,
+  level: :warn,
+  meta: [:all],
+  webhook_url: "https://hooks.slack.com/services/YOUR-KEY-HERE"
 
 config :mime, :types, %{
   "application/xml" => ["xml"],
   "application/xrd+xml" => ["xrd+xml"],
   "application/jrd+json" => ["jrd+json"],
   "application/activity+json" => ["activity+json"],
-  "application/ld+json" => ["activity+json"],
-  # Can be removed when bumping MIME past 2.0.5
-  # see https://akkoma.dev/AkkomaGang/akkoma/issues/657
-  "image/apng" => ["apng"]
+  "application/ld+json" => ["activity+json"]
 }
 
 config :tesla, adapter: Tesla.Adapter.Hackney
@@ -171,12 +187,11 @@ config :pleroma, :instance,
   email: "example@example.com",
   notify_email: "noreply@example.com",
   description: "Pleroma: An efficient and flexible fediverse server",
-  short_description: "",
   background_image: "/images/city.jpg",
   instance_thumbnail: "/instance/thumbnail.jpeg",
-  favicon: "/favicon.png",
   limit: 5_000,
   description_limit: 5_000,
+  chat_limit: 5_000,
   remote_limit: 100_000,
   upload_limit: 16_000_000,
   avatar_upload_limit: 2_000_000,
@@ -195,10 +210,13 @@ config :pleroma, :instance,
   federating: true,
   federation_incoming_replies_max_depth: 100,
   federation_reachability_timeout_days: 7,
+  federation_publisher_modules: [
+    Pleroma.Web.ActivityPub.Publisher
+  ],
   allow_relay: true,
   public: true,
   quarantined_instances: [],
-  rejected_instances: [],
+  managed_config: true,
   static_dir: "instance/static/",
   allowed_post_formats: [
     "text/plain",
@@ -207,11 +225,9 @@ config :pleroma, :instance,
     "text/bbcode"
   ],
   autofollowed_nicknames: [],
-  autofollowing_nicknames: [],
   max_pinned_statuses: 1,
   attachment_links: false,
   max_report_comment_size: 1000,
-  report_strip_status: true,
   safe_dm_mentions: false,
   healthcheck: false,
   remote_post_retention_days: 90,
@@ -238,30 +254,7 @@ config :pleroma, :instance,
       length: 16
     ]
   ],
-  show_reactions: true,
-  password_reset_token_validity: 60 * 60 * 24,
-  profile_directory: true,
-  admin_privileges: [
-    :users_read,
-    :users_manage_invites,
-    :users_manage_activation_state,
-    :users_manage_tags,
-    :users_manage_credentials,
-    :users_delete,
-    :messages_read,
-    :messages_delete,
-    :instances_delete,
-    :reports_manage_reports,
-    :moderation_log_read,
-    :announcements_manage_announcements,
-    :emoji_manage_emoji,
-    :statistics_read
-  ],
-  moderator_privileges: [:messages_delete, :reports_manage_reports],
-  max_endorsed_users: 20,
-  birthday_required: false,
-  birthday_min_age: 0,
-  max_media_attachments: 1_000
+  show_reactions: true
 
 config :pleroma, :welcome,
   direct_message: [
@@ -313,7 +306,7 @@ config :pleroma, :frontend_configurations,
     hideSitename: false,
     hideUserStats: false,
     loginMethod: "password",
-    logo: "/static/logo.svg",
+    logo: "/static/logo.png",
     logoMargin: ".1em",
     logoMask: true,
     minimalScopesMode: false,
@@ -329,6 +322,9 @@ config :pleroma, :frontend_configurations,
     subjectLineBehavior: "email",
     theme: "pleroma-dark",
     webPushNotifications: false
+  },
+  masto_fe: %{
+    showInstanceSpecificPanel: true
   }
 
 config :pleroma, :assets,
@@ -347,10 +343,8 @@ config :pleroma, :assets,
 config :pleroma, :manifest,
   icons: [
     %{
-      src: "/static/logo.svg",
-      sizes: "512x512",
-      purpose: "any",
-      type: "image/svg+xml"
+      src: "/static/logo.png",
+      type: "image/png"
     }
   ],
   theme_color: "#282c37",
@@ -359,12 +353,10 @@ config :pleroma, :manifest,
 config :pleroma, :activitypub,
   unfollow_blocked: true,
   outgoing_blocks: true,
-  blockers_visible: true,
   follow_handshake_timeout: 500,
   note_replies_output_limit: 5,
   sign_object_fetches: true,
-  authorized_fetch_mode: false,
-  client_api_enabled: false
+  authorized_fetch_mode: false
 
 config :pleroma, :streamer,
   workers: 3,
@@ -399,17 +391,6 @@ config :pleroma, :mrf_keyword,
   federated_timeline_removal: [],
   replace: []
 
-config :pleroma, :mrf_emoji,
-  remove_url: [],
-  remove_shortcode: [],
-  federated_timeline_removal_url: [],
-  federated_timeline_removal_shortcode: []
-
-config :pleroma, :mrf_hashtag,
-  sensitive: ["nsfw"],
-  reject: [],
-  federated_timeline_removal: []
-
 config :pleroma, :mrf_subchain, match_actor: %{}
 
 config :pleroma, :mrf_activity_expiration, days: 365
@@ -423,28 +404,6 @@ config :pleroma, :mrf_object_age,
   threshold: 604_800,
   actions: [:delist, :strip_followers]
 
-config :pleroma, :mrf_nsfw_api,
-  url: "http://127.0.0.1:5000/",
-  threshold: 0.7,
-  mark_sensitive: true,
-  unlist: false,
-  reject: false
-
-config :pleroma, :mrf_follow_bot, follower_nickname: nil
-
-config :pleroma, :mrf_inline_quote, template: "<bdi>RT:</bdi> {url}"
-
-config :pleroma, :mrf_remote_report,
-  reject_all: false,
-  reject_anonymous: true,
-  reject_empty_message: true
-
-config :pleroma, :mrf_force_mention,
-  mention_parent: true,
-  mention_quoted: true
-
-config :pleroma, :mrf_antimentionspam, user_age_limit: 30_000
-
 config :pleroma, :rich_media,
   enabled: true,
   ignore_hosts: [],
@@ -453,12 +412,8 @@ config :pleroma, :rich_media,
     Pleroma.Web.RichMedia.Parsers.TwitterCard,
     Pleroma.Web.RichMedia.Parsers.OEmbed
   ],
-  timeout: 5_000,
-  ttl_setters: [
-    Pleroma.Web.RichMedia.Parser.TTL.AwsSignedUrl,
-    Pleroma.Web.RichMedia.Parser.TTL.Opengraph
-  ],
-  max_body: 5_000_000
+  failure_backoff: 60_000,
+  ttl_setters: [Pleroma.Web.RichMedia.Parser.TTL.AwsSignedUrl]
 
 config :pleroma, :media_proxy,
   enabled: false,
@@ -469,8 +424,6 @@ config :pleroma, :media_proxy,
   proxy_opts: [
     redirect_on_failure: false,
     max_body_length: 25 * 1_048_576,
-    # Note: max_read_duration defaults to Pleroma.ReverseProxy.max_read_duration_default/1
-    max_read_duration: 30_000,
     http: [
       follow_redirect: true,
       pool: :media
@@ -483,23 +436,11 @@ config :pleroma, Pleroma.Web.MediaProxy.Invalidation.Http,
   headers: [],
   options: []
 
-config :pleroma, Pleroma.Web.MediaProxy.Invalidation.Script,
-  script_path: nil,
-  url_format: nil
+config :pleroma, Pleroma.Web.MediaProxy.Invalidation.Script, script_path: nil
 
-# Note: media preview proxy depends on media proxy to be enabled
-config :pleroma, :media_preview_proxy,
-  enabled: false,
-  thumbnail_max_width: 600,
-  thumbnail_max_height: 600,
-  image_quality: 85,
-  min_content_length: 100 * 1024
+config :pleroma, :chat, enabled: true
 
-config :pleroma, :shout,
-  enabled: true,
-  limit: 5_000
-
-config :phoenix, :format_encoders, json: Jason, "activity+json": Jason
+config :phoenix, :format_encoders, json: Jason
 
 config :phoenix, :json_library, Jason
 
@@ -527,8 +468,7 @@ config :pleroma, :http_security,
   sts: false,
   sts_max_age: 31_536_000,
   ct_max_age: 2_592_000,
-  referrer_policy: "same-origin",
-  allow_unsafe_eval: false
+  referrer_policy: "same-origin"
 
 config :cors_plug,
   max_age: 86_400,
@@ -585,25 +525,35 @@ config :pleroma, Pleroma.User,
   ],
   email_blacklist: []
 
-# The Pruner :max_age must be longer than Worker :unique
-# value or it cannot enforce uniqueness.
 config :pleroma, Oban,
   repo: Pleroma.Repo,
   log: false,
   queues: [
     activity_expiration: 10,
-    federator_incoming: 5,
-    federator_outgoing: 25,
+    federator_incoming: 50,
+    federator_outgoing: 50,
     web_push: 50,
-    background: 20,
-    search_indexing: [limit: 10, paused: true],
-    slow: 5
+    mailer: 10,
+    transmogrifier: 20,
+    scheduled_activities: 10,
+    background: 5,
+    remote_fetcher: 2,
+    attachments_cleanup: 5,
+    new_users_digest: 1
   ],
-  plugins: [{Oban.Plugins.Pruner, max_age: 900}],
+  plugins: [Oban.Plugins.Pruner],
   crontab: [
+    {"0 0 * * *", Pleroma.Workers.Cron.ClearOauthTokenWorker},
+    {"0 * * * *", Pleroma.Workers.Cron.StatsWorker},
+    {"* * * * *", Pleroma.Workers.Cron.PurgeExpiredActivitiesWorker},
     {"0 0 * * 0", Pleroma.Workers.Cron.DigestEmailsWorker},
-    {"0 0 * * *", Pleroma.Workers.Cron.NewUsersDigestWorker},
-    {"*/10 * * * *", Pleroma.Workers.Cron.AppCleanupWorker}
+    {"0 0 * * *", Pleroma.Workers.Cron.NewUsersDigestWorker}
+  ]
+
+config :pleroma, :workers,
+  retries: [
+    federator_incoming: 5,
+    federator_outgoing: 5
   ]
 
 config :pleroma, Pleroma.Formatter,
@@ -617,17 +567,17 @@ config :pleroma, Pleroma.Formatter,
 
 config :pleroma, :ldap,
   enabled: System.get_env("LDAP_ENABLED") == "true",
-  host: System.get_env("LDAP_HOST", "localhost"),
-  port: String.to_integer(System.get_env("LDAP_PORT", "389")),
+  host: System.get_env("LDAP_HOST") || "localhost",
+  port: String.to_integer(System.get_env("LDAP_PORT") || "389"),
   ssl: System.get_env("LDAP_SSL") == "true",
   sslopts: [],
   tls: System.get_env("LDAP_TLS") == "true",
   tlsopts: [],
-  base: System.get_env("LDAP_BASE", "dc=example,dc=com"),
-  uid: System.get_env("LDAP_UID", "cn"),
-  # defaults to CAStore's Mozilla roots
-  cacertfile: System.get_env("LDAP_CACERTFILE", nil),
-  mail: System.get_env("LDAP_MAIL", "mail")
+  base: System.get_env("LDAP_BASE") || "dc=example,dc=com",
+  uid: System.get_env("LDAP_UID") || "cn"
+
+config :esshd,
+  enabled: false
 
 oauth_consumer_strategies =
   System.get_env("OAUTH_CONSUMER_STRATEGIES")
@@ -647,7 +597,10 @@ config :ueberauth,
        base_path: "/oauth",
        providers: ueberauth_providers
 
-config :pleroma, :auth, oauth_consumer_strategies: oauth_consumer_strategies
+config :pleroma,
+       :auth,
+       enforce_oauth_admin_scope_usage: true,
+       oauth_consumer_strategies: oauth_consumer_strategies
 
 config :pleroma, Pleroma.Emails.Mailer, adapter: Swoosh.Adapters.Sendmail, enabled: false
 
@@ -664,26 +617,7 @@ config :pleroma, Pleroma.Emails.UserEmail,
 
 config :pleroma, Pleroma.Emails.NewUsersDigestEmail, enabled: false
 
-config :pleroma, Pleroma.PromEx,
-  disabled: false,
-  manual_metrics_start_delay: :no_delay,
-  drop_metrics_groups: [],
-  grafana: [
-    host: System.get_env("GRAFANA_HOST", "http://localhost:3000"),
-    auth_token: System.get_env("GRAFANA_TOKEN"),
-    upload_dashboards_on_start: false,
-    folder_name: "BEAM",
-    annotate_app_lifecycle: true
-  ],
-  metrics_server: [
-    port: 4021,
-    path: "/metrics",
-    protocol: :http,
-    pool_size: 5,
-    cowboy_opts: [],
-    auth_strategy: :none
-  ],
-  datasource: "Prometheus"
+config :prometheus, Pleroma.Web.Endpoint.MetricsExporter, path: "/api/pleroma/app_metrics"
 
 config :pleroma, Pleroma.ScheduledActivity,
   daily_user_limit: 25,
@@ -698,18 +632,12 @@ config :pleroma, :email_notifications,
   }
 
 config :pleroma, :oauth2,
-  token_expires_in: 3600 * 24 * 365 * 100,
+  token_expires_in: 600,
   issue_new_refresh_token: true,
   clean_expired_tokens: false
 
 config :pleroma, :database, rum_enabled: false
 
-config :pleroma, :features, improved_hashtag_timeline: :auto
-
-config :pleroma, :populate_hashtags_table, fault_rate_allowance: 0.01
-
-config :pleroma, :delete_context_objects, fault_rate_allowance: 0.01
-
 config :pleroma, :env, Mix.env()
 
 config :http_signatures,
@@ -720,7 +648,6 @@ config :pleroma, :rate_limit,
   timeline: {500, 3},
   search: [{1000, 10}, {1000, 30}],
   app_account_creation: {1_800_000, 25},
-  oauth_app_creation: {900_000, 5},
   relations_actions: {10_000, 10},
   relation_id_action: {60_000, 2},
   statuses_actions: {10_000, 15},
@@ -729,20 +656,9 @@ config :pleroma, :rate_limit,
   account_confirmation_resend: {8_640_000, 5},
   ap_routes: {60_000, 15}
 
-config :pleroma, Pleroma.Workers.PurgeExpiredActivity, enabled: true, min_lifetime: 600
+config :pleroma, Pleroma.ActivityExpiration, enabled: true
 
-config :pleroma, Pleroma.Web.Plugs.RemoteIp,
-  enabled: true,
-  headers: ["x-forwarded-for"],
-  proxies: [],
-  reserved: [
-    "127.0.0.0/8",
-    "::1/128",
-    "fc00::/7",
-    "10.0.0.0/8",
-    "172.16.0.0/12",
-    "192.168.0.0/16"
-  ]
+config :pleroma, Pleroma.Plugs.RemoteIp, enabled: true
 
 config :pleroma, :static_fe, enabled: false
 
@@ -754,7 +670,7 @@ config :pleroma, :static_fe, enabled: false
 # With no frontend configuration, the bundled files from the `static` directory will
 # be used.
 #
-# config :pleroma, :frontends,
+# config :pleroma, :frontends, 
 # primary: %{"name" => "pleroma-fe", "ref" => "develop"},
 # admin: %{"name" => "admin-fe", "ref" => "stable"},
 # available: %{...}
@@ -779,11 +695,8 @@ config :pleroma, :frontends,
       "name" => "fedi-fe",
       "git" => "https://git.pleroma.social/pleroma/fedi-fe",
       "build_url" =>
-        "https://git.pleroma.social/pleroma/fedi-fe/-/jobs/artifacts/${ref}/download?job=build_release",
-      "ref" => "master",
-      "custom-http-headers" => [
-        {"service-worker-allowed", "/"}
-      ]
+        "https://git.pleroma.social/pleroma/fedi-fe/-/jobs/artifacts/${ref}/download?job=build",
+      "ref" => "master"
     },
     "admin-fe" => %{
       "name" => "admin-fe",
@@ -792,28 +705,13 @@ config :pleroma, :frontends,
         "https://git.pleroma.social/pleroma/admin-fe/-/jobs/artifacts/${ref}/download?job=build",
       "ref" => "develop"
     },
-    "soapbox" => %{
-      "name" => "soapbox",
-      "git" => "https://gitlab.com/soapbox-pub/soapbox",
+    "soapbox-fe" => %{
+      "name" => "soapbox-fe",
+      "git" => "https://gitlab.com/soapbox-pub/soapbox-fe",
       "build_url" =>
-        "https://gitlab.com/soapbox-pub/soapbox/-/jobs/artifacts/${ref}/download?job=build-production",
-      "ref" => "v3.0.0-beta.1",
+        "https://gitlab.com/soapbox-pub/soapbox-fe/-/jobs/artifacts/${ref}/download?job=build-production",
+      "ref" => "v1.0.0",
       "build_dir" => "static"
-    },
-    "glitch-lily" => %{
-      "name" => "glitch-lily",
-      "git" => "https://lily-is.land/infra/glitch-lily",
-      "build_url" =>
-        "https://lily-is.land/infra/glitch-lily/-/jobs/artifacts/${ref}/download?job=build",
-      "ref" => "servant",
-      "build_dir" => "public"
-    },
-    "pl-fe" => %{
-      "name" => "pl-fe",
-      "git" => "https://github.com/mkljczk/pl-fe",
-      "build_url" => "https://pl.mkljczk.pl/pl-fe.zip",
-      "ref" => "develop",
-      "build_dir" => "."
     }
   }
 
@@ -826,7 +724,7 @@ config :pleroma, :modules, runtime_dir: "instance/modules"
 config :pleroma, configurable_from_database: false
 
 config :pleroma, Pleroma.Repo,
-  parameters: [gin_fuzzy_search_limit: "500", jit: "off"],
+  parameters: [gin_fuzzy_search_limit: "500"],
   prepare: :unnamed
 
 config :pleroma, :connections_pool,
@@ -836,55 +734,44 @@ config :pleroma, :connections_pool,
   max_connections: 250,
   max_idle_time: 30_000,
   retry: 0,
-  connect_timeout: 5_000
+  await_up_timeout: 5_000
 
 config :pleroma, :pools,
   federation: [
-    size: 75,
-    max_waiting: 20,
-    recv_timeout: 10_000
+    size: 50,
+    max_waiting: 10,
+    timeout: 10_000
   ],
   media: [
-    size: 75,
-    max_waiting: 20,
-    recv_timeout: 15_000
-  ],
-  rich_media: [
-    size: 25,
-    max_waiting: 20,
-    recv_timeout: 15_000
+    size: 50,
+    max_waiting: 10,
+    timeout: 10_000
   ],
   upload: [
     size: 25,
-    max_waiting: 20,
-    recv_timeout: 15_000
+    max_waiting: 5,
+    timeout: 15_000
   ],
   default: [
-    size: 50,
+    size: 10,
     max_waiting: 2,
-    recv_timeout: 5_000
+    timeout: 5_000
   ]
 
 config :pleroma, :hackney_pools,
   federation: [
     max_connections: 50,
-    timeout: 10_000
+    timeout: 150_000
   ],
   media: [
     max_connections: 50,
-    timeout: 15_000
-  ],
-  rich_media: [
-    max_connections: 50,
-    timeout: 15_000
+    timeout: 150_000
   ],
   upload: [
     max_connections: 25,
-    timeout: 15_000
+    timeout: 300_000
   ]
 
-config :pleroma, :majic_pool, size: 2
-
 private_instance? = :if_instance_is_private
 
 config :pleroma, :restrict_unauthenticated,
@@ -895,11 +782,7 @@ config :pleroma, :restrict_unauthenticated,
 config :pleroma, Pleroma.Web.ApiSpec.CastAndValidate, strict: false
 
 config :pleroma, :mrf,
-  policies: [
-    Pleroma.Web.ActivityPub.MRF.ObjectAgePolicy,
-    Pleroma.Web.ActivityPub.MRF.TagPolicy,
-    Pleroma.Web.ActivityPub.MRF.InlineQuotePolicy
-  ],
+  policies: Pleroma.Web.ActivityPub.MRF.ObjectAgePolicy,
   transparency: true,
   transparency_exclusions: []
 
@@ -907,56 +790,12 @@ config :tzdata, :http_client, Pleroma.HTTP.Tzdata
 
 config :ex_aws, http_client: Pleroma.HTTP.ExAws
 
-config :web_push_encryption, http_client: Pleroma.HTTP.WebPush
-
 config :pleroma, :instances_favicons, enabled: false
 
 config :floki, :html_parser, Floki.HTMLParser.FastHtml
 
 config :pleroma, Pleroma.Web.Auth.Authenticator, Pleroma.Web.Auth.PleromaAuthenticator
 
-config :pleroma, Pleroma.User.Backup,
-  purge_after_days: 30,
-  limit_days: 7,
-  dir: nil,
-  process_chunk_size: 100,
-  timeout: :timer.minutes(30)
-
-config :pleroma, ConcurrentLimiter, [
-  {Pleroma.Search, [max_running: 30, max_waiting: 50]}
-]
-
-config :pleroma, Pleroma.Web.WebFinger, domain: nil, update_nickname_on_user_fetch: true
-
-config :pleroma, Pleroma.Search, module: Pleroma.Search.DatabaseSearch
-
-config :pleroma, Pleroma.Search.Meilisearch,
-  url: "http://127.0.0.1:7700/",
-  private_key: nil,
-  initial_indexing_chunk_size: 100_000
-
-config :pleroma, Pleroma.Application,
-  background_migrators: true,
-  internal_fetch: true,
-  load_custom_modules: true,
-  max_restarts: 3,
-  streamer_registry: true
-
-config :pleroma, Pleroma.Uploaders.Uploader, timeout: 30_000
-
-config :pleroma, Pleroma.Search.QdrantSearch,
-  qdrant_url: "http://127.0.0.1:6333/",
-  qdrant_api_key: "",
-  openai_url: "http://127.0.0.1:11345",
-  # The healthcheck url has to be set to nil when used with the real openai
-  # API, as it doesn't have a healthcheck endpoint.
-  openai_healthcheck_url: "http://127.0.0.1:11345/health",
-  openai_model: "snowflake/snowflake-arctic-embed-xs",
-  openai_api_key: "",
-  qdrant_index_configuration: %{
-    vectors: %{size: 384, distance: "Cosine"}
-  }
-
 # 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"

config/dev.exs

@@ -1,4 +1,4 @@
-import Config
+use Mix.Config
 
 # For development, we disable any cache and enable
 # debugging and code reloading.
@@ -8,7 +8,8 @@ import Config
 # with brunch.io to recompile .js and .css sources.
 config :pleroma, Pleroma.Web.Endpoint,
   http: [
-    port: 4000
+    port: 4000,
+    protocol_options: [max_request_line_length: 8192, max_header_value_length: 8192]
   ],
   protocol: "http",
   debug_errors: true,
@@ -35,8 +36,8 @@ config :pleroma, Pleroma.Emails.Mailer, adapter: Swoosh.Adapters.Local
 # configured to run both http and https servers on
 # different ports.
 
-# Do not include timestamps in development logs
-config :logger, Logger.Backends.Console, format: "$metadata[$level] $message\n"
+# Do not include metadata nor timestamps in development logs
+config :logger, :console, format: "[$level] $message\n"
 
 # Set a higher stacktrace during development. Avoid configuring such
 # in production as building large stacktraces may be expensive.
@@ -53,15 +54,10 @@ config :pleroma, Pleroma.Repo,
 
 config :pleroma, Pleroma.Web.ApiSpec.CastAndValidate, strict: true
 
-# Reduce recompilation time
-# https://dashbit.co/blog/speeding-up-re-compilation-of-elixir-projects
-config :phoenix, :plug_init_mode, :runtime
-
 if File.exists?("./config/dev.secret.exs") do
   import_config "dev.secret.exs"
 else
   IO.puts(
-    :stderr,
     "!!! RUNNING IN LOCALHOST DEV MODE! !!!\nFEDERATION WON'T WORK UNTIL YOU CONFIGURE A dev.secret.exs"
   )
 end

config/docker.exs

@@ -18,7 +18,6 @@ config :pleroma, Pleroma.Repo,
   password: System.fetch_env!("DB_PASS"),
   database: System.get_env("DB_NAME", "pleroma"),
   hostname: System.get_env("DB_HOST", "db"),
-  port: System.get_env("DB_PORT", "5432"),
   pool_size: 10
 
 # Configure web push notifications

config/dokku.exs

@@ -1,4 +1,4 @@
-import Config
+use Mix.Config
 
 config :pleroma, Pleroma.Web.Endpoint,
   http: [

config/emoji.txt

@@ -1,3 +1,2 @@
 firefox, /emoji/Firefox.gif, Gif,Fun
 blank, /emoji/blank.png, Fun
-dinosaur, /emoji/dino walking.gif, Gif

config/prod.exs

@@ -1,4 +1,4 @@
-import Config
+use Mix.Config
 
 # For production, we often load configuration from external
 # sources, such as your system environment. For this reason,
@@ -20,7 +20,6 @@ config :pleroma, Pleroma.Web.Endpoint,
 config :phoenix, serve_endpoints: true
 
 # Do not print debug messages in production
-config :logger, Logger.Backends.Console, level: :info
 config :logger, :console, level: :info
 config :logger, :ex_syslogger, level: :info
 
@@ -64,12 +63,7 @@ config :logger, :ex_syslogger, level: :info
 
 # Finally import the config/prod.secret.exs
 # which should be versioned separately.
-if File.exists?("./config/prod.secret.exs") do
-  import_config "prod.secret.exs"
-else
-  "`config/prod.secret.exs` not found. You may want to create one by running `mix pleroma.instance gen`"
-  |> IO.warn([])
-end
+import_config "prod.secret.exs"
 
 if File.exists?("./config/prod.exported_from_db.secret.exs"),
   do: import_config("prod.exported_from_db.secret.exs")

config/releases.exs

@@ -0,0 +1,31 @@
+import Config
+
+config :pleroma, :instance, static_dir: "/var/lib/pleroma/static"
+config :pleroma, Pleroma.Uploaders.Local, uploads: "/var/lib/pleroma/uploads"
+config :pleroma, :modules, runtime_dir: "/var/lib/pleroma/modules"
+
+config_path = System.get_env("PLEROMA_CONFIG_PATH") || "/etc/pleroma/config.exs"
+
+config :pleroma, release: true, config_path: config_path
+
+if File.exists?(config_path) do
+  import_config config_path
+else
+  warning = [
+    IO.ANSI.red(),
+    IO.ANSI.bright(),
+    "!!! #{config_path} not found! Please ensure it exists and that PLEROMA_CONFIG_PATH is unset or points to an existing file",
+    IO.ANSI.reset()
+  ]
+
+  IO.puts(warning)
+end
+
+exported_config =
+  config_path
+  |> Path.dirname()
+  |> Path.join("prod.exported_from_db.secret.exs")
+
+if File.exists?(exported_config) do
+  import_config exported_config
+end

config/test.exs

@@ -1,4 +1,4 @@
-import Config
+use Mix.Config
 
 # We don't run a server during test. If one is required,
 # you can enable the server option below.
@@ -16,7 +16,7 @@ config :pleroma, Pleroma.Captcha,
 
 # 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: []
@@ -38,10 +38,7 @@ config :pleroma, :instance,
   external_user_synchronization: false,
   static_dir: "test/instance_static/"
 
-config :pleroma, :activitypub,
-  sign_object_fetches: false,
-  follow_handshake_timeout: 0,
-  client_api_enabled: true
+config :pleroma, :activitypub, sign_object_fetches: false
 
 # Configure your database
 config :pleroma, Pleroma.Repo,
@@ -50,23 +47,17 @@ config :pleroma, Pleroma.Repo,
   password: "postgres",
   database: "pleroma_test",
   hostname: System.get_env("DB_HOST") || "localhost",
-  port: System.get_env("DB_PORT") || "5432",
-  pool: Ecto.Adapters.SQL.Sandbox,
-  pool_size: System.schedulers_online() * 2,
-  log: false
-
-config :pleroma, :dangerzone, override_repo_pool_size: true
+  pool: Ecto.Adapters.SQL.Sandbox
 
 # Reduce hash rounds for testing
-config :pleroma, :password, iterations: 1
+config :pbkdf2_elixir, rounds: 1
 
 config :tesla, adapter: Tesla.Mock
 
 config :pleroma, :rich_media,
   enabled: false,
   ignore_hosts: [],
-  ignore_tld: ["local", "localdomain", "lan"],
-  max_body: 2_000_000
+  ignore_tld: ["local", "localdomain", "lan"]
 
 config :pleroma, :instance,
   multi_factor_authentication: [
@@ -87,7 +78,12 @@ config :web_push_encryption, :vapid_details,
     "BLH1qVhJItRGCfxgTtONfsOKDc9VRAraXw-3NsmjMngWSh7NxOizN6bkuRA7iLTMPS82PjwJAr3UoK9EC1IFrz4",
   private_key: "_-XZ0iebPrRfZ_o0-IatTdszYa8VCH1yLN-JauK7HHA"
 
-config :pleroma, Oban, testing: :manual
+config :web_push_encryption, :http_client, Pleroma.Web.WebPushHttpClientMock
+
+config :pleroma, Oban,
+  queues: false,
+  crontab: false,
+  plugins: false
 
 config :pleroma, Pleroma.ScheduledActivity,
   daily_user_limit: 2,
@@ -114,93 +110,21 @@ config :pleroma, Pleroma.Gun, Pleroma.GunMock
 
 config :pleroma, Pleroma.Emails.NewUsersDigestEmail, enabled: true
 
-config :pleroma, Pleroma.Web.Plugs.RemoteIp, enabled: false
+config :pleroma, Pleroma.Plugs.RemoteIp, enabled: false
 
 config :pleroma, Pleroma.Web.ApiSpec.CastAndValidate, strict: true
 
+config :pleroma, :instances_favicons, enabled: false
+
+config :pleroma, Pleroma.Uploaders.S3,
+  bucket: nil,
+  streaming_enabled: true,
+  public_endpoint: nil
+
 config :tzdata, :autoupdate, :disabled
 
 config :pleroma, :mrf, policies: []
 
-config :pleroma, :pipeline,
-  object_validator: Pleroma.Web.ActivityPub.ObjectValidatorMock,
-  mrf: Pleroma.Web.ActivityPub.MRFMock,
-  activity_pub: Pleroma.Web.ActivityPub.ActivityPubMock,
-  side_effects: Pleroma.Web.ActivityPub.SideEffectsMock,
-  federator: Pleroma.Web.FederatorMock,
-  config: Pleroma.ConfigMock
-
-config :pleroma, :cachex, provider: Pleroma.CachexMock
-
-config :pleroma, Pleroma.Web.WebFinger, update_nickname_on_user_fetch: false
-
-config :pleroma, :side_effects,
-  ap_streamer: Pleroma.Web.ActivityPub.ActivityPubMock,
-  logger: Pleroma.LoggerMock
-
-config :pleroma, Pleroma.Search, module: Pleroma.Search.DatabaseSearch
-
-config :pleroma, Pleroma.Search.Meilisearch, url: "http://127.0.0.1:7700/", private_key: nil
-
-# Reduce recompilation time
-# https://dashbit.co/blog/speeding-up-re-compilation-of-elixir-projects
-config :phoenix, :plug_init_mode, :runtime
-
-config :pleroma, :config_impl, Pleroma.UnstubbedConfigMock
-config :pleroma, :datetime_impl, Pleroma.DateTimeMock
-
-config :pleroma, Pleroma.PromEx, disabled: true
-
-# Mox definitions. Only read during compile time.
-config :pleroma, Pleroma.User.Backup, config_impl: Pleroma.UnstubbedConfigMock
-config :pleroma, Pleroma.Uploaders.S3, ex_aws_impl: Pleroma.Uploaders.S3.ExAwsMock
-config :pleroma, Pleroma.Uploaders.S3, config_impl: Pleroma.UnstubbedConfigMock
-config :pleroma, Pleroma.Upload, config_impl: Pleroma.UnstubbedConfigMock
-config :pleroma, Pleroma.Language.LanguageDetector, config_impl: Pleroma.StaticStubbedConfigMock
-config :pleroma, Pleroma.ScheduledActivity, config_impl: Pleroma.UnstubbedConfigMock
-config :pleroma, Pleroma.Web.RichMedia.Helpers, config_impl: Pleroma.StaticStubbedConfigMock
-config :pleroma, Pleroma.Uploaders.IPFS, config_impl: Pleroma.UnstubbedConfigMock
-config :pleroma, Pleroma.Web.Plugs.HTTPSecurityPlug, config_impl: Pleroma.StaticStubbedConfigMock
-config :pleroma, Pleroma.Web.Plugs.HTTPSignaturePlug, config_impl: Pleroma.StaticStubbedConfigMock
-
-config :pleroma, Pleroma.Upload.Filter.AnonymizeFilename,
-  config_impl: Pleroma.StaticStubbedConfigMock
-
-config :pleroma, Pleroma.Upload.Filter.Mogrify, config_impl: Pleroma.StaticStubbedConfigMock
-config :pleroma, Pleroma.Upload.Filter.Mogrify, mogrify_impl: Pleroma.MogrifyMock
-
-config :pleroma, Pleroma.Signature, http_signatures_impl: Pleroma.StubbedHTTPSignaturesMock
-
-peer_module =
-  if String.to_integer(System.otp_release()) >= 25 do
-    :peer
-  else
-    :slave
-  end
-
-config :pleroma, Pleroma.Cluster, peer_module: peer_module
-
-config :pleroma, Pleroma.Application,
-  background_migrators: false,
-  internal_fetch: false,
-  load_custom_modules: false,
-  max_restarts: 100,
-  streamer_registry: false,
-  test_http_pools: true
-
-config :pleroma, Pleroma.Web.Streaming, sync_streaming: true
-
-config :pleroma, Pleroma.Uploaders.Uploader, timeout: 1_000
-
-config :pleroma, Pleroma.Emoji.Loader, test_emoji: true
-
-config :pleroma, Pleroma.Web.RichMedia.Backfill,
-  stream_out: Pleroma.Web.ActivityPub.ActivityPubMock
-
-config :pleroma, Pleroma.Web.Plugs.HTTPSecurityPlug, enable: false
-
-config :pleroma, Pleroma.User.Backup, tempdir: "test/tmp"
-
 if File.exists?("./config/test.secret.exs") do
   import_config "test.secret.exs"
 else

coveralls.json

@@ -1,7 +1,6 @@
 {
   "skip_files": [
     "test/support",
-    "lib/mix/tasks/pleroma/benchmark.ex",
-    "lib/credo/check/consistency/file_location.ex"
+    "lib/mix/tasks/pleroma/benchmark.ex"
   ]
 }

docker-entrypoint.sh

@@ -3,7 +3,7 @@
 set -e
 
 echo "-- Waiting for database..."
-while ! pg_isready -U ${DB_USER:-pleroma} -d postgres://${DB_HOST:-db}:${DB_PORT:-5432}/${DB_NAME:-pleroma} -t 1; do
+while ! pg_isready -U ${DB_USER:-pleroma} -d postgres://${DB_HOST:-db}:5432/${DB_NAME:-pleroma} -t 1; do
     sleep 1s
 done
 

docs/API/chats.md

@@ -116,10 +116,6 @@ The modified chat message
 This will return a list of chats that you have been involved in, sorted by their
 last update (so new chats will be at the top).
 
-Parameters:
-
-- with_muted: Include chats from muted users (boolean).
-
 Returned data:
 
 ```json
@@ -177,14 +173,11 @@ Returned data:
     "created_at": "2020-04-21T15:06:45.000Z",
     "emojis": [],
     "id": "12",
-    "unread": false,
-    "idempotency_key": "75442486-0874-440c-9db1-a7006c25a31f"
+    "unread": false
   }
 ]
 ```
 
-- idempotency_key: The copy of the `idempotency-key` HTTP request header that can be used for optimistic message sending. Included only during the first few minutes after the message creation.
-
 ### Posting a chat message
 
 Posting a chat message for given Chat id works like this:

docs/API/differences_in_mastoapi_responses.md

@@ -0,0 +1,290 @@
+# Differences in Mastodon API responses from vanilla Mastodon
+
+A Pleroma instance can be identified by "<Mastodon version> (compatible; Pleroma <version>)" present in `version` field in response from `/api/v1/instance`
+
+## Flake IDs
+
+Pleroma uses 128-bit ids as opposed to Mastodon's 64 bits. However just like Mastodon's ids they are lexically sortable strings
+
+## Timelines
+
+Adding the parameter `with_muted=true` to the timeline queries will also return activities by muted (not by blocked!) users.
+Adding the parameter `exclude_visibilities` to the timeline queries will exclude the statuses with the given visibilities. The parameter accepts an array of visibility types (`public`, `unlisted`, `private`, `direct`), e.g., `exclude_visibilities[]=direct&exclude_visibilities[]=private`.
+Adding the parameter `reply_visibility` to the public and home timelines queries will filter replies. Possible values: without parameter (default) shows all replies, `following` - replies directed to you or users you follow, `self` - replies directed to you.
+
+## Statuses
+
+- `visibility`: has an additional possible value `list`
+
+Has these additional fields under the `pleroma` object:
+
+- `local`: true if the post was made on the local instance
+- `conversation_id`: the ID of the AP context the status is associated with (if any)
+- `direct_conversation_id`: the ID of the Mastodon direct message conversation the status is associated with (if any)
+- `in_reply_to_account_acct`: the `acct` property of User entity for replied user (if any)
+- `content`: a map consisting of alternate representations of the `content` property with the key being it's mimetype. Currently the only alternate representation supported is `text/plain`
+- `spoiler_text`: a map consisting of alternate representations of the `spoiler_text` property with the key being it's 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: 1, me: true}`. Contains no information about the reacting users, for that use the `/statuses/:id/reactions` endpoint.
+- `parent_visible`: If the parent of this post is visible to the user or not.
+
+## Media Attachments
+
+Has these additional fields under the `pleroma` object:
+
+- `mime_type`: mime type of the attachment.
+
+### Attachment cap
+
+Some apps operate under the assumption that no more than 4 attachments can be returned or uploaded. Pleroma however does not enforce any limits on attachment count neither when returning the status object nor when posting.
+
+### Limitations
+
+Pleroma does not process remote images and therefore cannot include fields such as `meta` and `blurhash`. It does not support focal points or aspect ratios. The frontend is expected to handle it.
+
+## Accounts
+
+The `id` parameter can also be the `nickname` of the user. This only works in these endpoints, not the deeper nested ones for following etc.
+
+- `/api/v1/accounts/:id`
+- `/api/v1/accounts/:id/statuses`
+
+Has these additional fields under the `pleroma` object:
+
+- `ap_id`: nullable URL string, ActivityPub id of the user
+- `background_image`: nullable URL string, background image of the user
+- `tags`: Lists an array of tags for the user
+- `relationship` (object): Includes fields as documented for Mastodon API https://docs.joinmastodon.org/entities/relationship/
+- `is_moderator`: boolean, nullable,  true if user is a moderator
+- `is_admin`: boolean, nullable, true if user is an admin
+- `confirmation_pending`: boolean, true if a new user account is waiting on email confirmation to be activated
+- `hide_favorites`: boolean, true when the user has hiding favorites enabled
+- `hide_followers`: boolean, true when the user has follower hiding enabled
+- `hide_follows`: boolean, true when the user has follow hiding enabled
+- `hide_followers_count`: boolean, true when the user has follower stat hiding enabled
+- `hide_follows_count`: boolean, true when the user has follow stat hiding enabled
+- `settings_store`: A generic map of settings for frontends. Opaque to the backend. Only returned in `/api/v1/accounts/verify_credentials` and `/api/v1/accounts/update_credentials`
+- `chat_token`: The token needed for Pleroma chat. Only returned in `/api/v1/accounts/verify_credentials`
+- `deactivated`: boolean, true when the user is deactivated
+- `allow_following_move`: boolean, true when the user allows automatically follow moved following accounts
+- `unread_conversation_count`: The count of unread conversations. Only returned to the account owner.
+- `unread_notifications_count`: The count of unread notifications. Only returned to the account owner.
+- `notification_settings`: object, can be absent. See `/api/pleroma/notification_settings` for the parameters/keys returned.
+- `accepts_chat_messages`: boolean, but can be null if we don't have that information about a user
+- `favicon`: nullable URL string, Favicon image of the user's instance
+
+### Source
+
+Has these additional fields under the `pleroma` object:
+
+- `show_role`: boolean, nullable, true when the user wants his role (e.g admin, moderator) to be shown
+- `no_rich_text` - boolean, nullable, true when html tags are stripped from all statuses requested from the API
+- `discoverable`: boolean, true when the user allows discovery of the account in search results and other services.
+- `actor_type`: string, the type of this account.
+
+## Conversations
+
+Has an additional field under the `pleroma` object:
+
+- `recipients`: The list of the recipients of this Conversation. These will be addressed when replying to this conversation.
+
+## GET `/api/v1/conversations`
+
+Accepts additional parameters:
+
+- `recipients`: Only return conversations with the given recipients (a list of user ids). Usage example: `GET /api/v1/conversations?recipients[]=1&recipients[]=2`
+
+## Account Search
+
+Behavior has changed:
+
+- `/api/v1/accounts/search`: Does not require authentication
+
+## Search (global)
+
+Unlisted posts are available in search results, they are considered to be public posts that shouldn't be shown in local/federated timeline.
+
+## Notifications
+
+Has these additional fields under the `pleroma` object:
+
+- `is_seen`: true if the notification was read by the user
+
+### Move Notification
+
+The `type` value is `move`. Has an additional field:
+
+- `target`: new account
+
+### EmojiReact Notification
+
+The `type` value is `pleroma:emoji_reaction`. Has these fields:
+
+- `emoji`: The used emoji
+- `account`: The account of the user who reacted
+- `status`: The status that was reacted on
+
+## GET `/api/v1/notifications`
+
+Accepts additional parameters:
+
+- `exclude_visibilities`: will exclude the notifications for activities with the given visibilities. The parameter accepts an array of visibility types (`public`, `unlisted`, `private`, `direct`). Usage example: `GET /api/v1/notifications?exclude_visibilities[]=direct&exclude_visibilities[]=private`.
+- `include_types`: will include the notifications for activities with the given types. The parameter accepts an array of types (`mention`, `follow`, `reblog`, `favourite`, `move`, `pleroma:emoji_reaction`). Usage example: `GET /api/v1/notifications?include_types[]=mention&include_types[]=reblog`.
+
+## DELETE `/api/v1/notifications/destroy_multiple`
+
+An endpoint to delete multiple statuses by IDs.
+
+Required parameters:
+
+- `ids`: array of activity ids
+
+Usage example: `DELETE /api/v1/notifications/destroy_multiple/?ids[]=1&ids[]=2`.
+
+Returns on success: 200 OK `{}`
+
+## POST `/api/v1/statuses`
+
+Additional parameters can be added to the JSON body/Form data:
+
+- `preview`: boolean, if set to `true` the post won't be actually posted, but the status entitiy would still be rendered back. This could be useful for previewing rich text/custom emoji, for example.
+- `content_type`: string, contain the MIME type of the status, it is transformed into HTML by the backend. You can get the list of the supported MIME types with the nodeinfo endpoint.
+- `to`: A list of nicknames (like `lain@soykaf.club` or `lain` on the local server) that will be used to determine who is going to be addressed by this post. Using this will disable the implicit addressing by mentioned names in the `status` body, only the people in the `to` list will be addressed. The normal rules for for post visibility are not affected by this and will still apply.
+- `visibility`: string, besides standard MastoAPI values (`direct`, `private`, `unlisted` or `public`) it can be used to address a List by setting it to `list:LIST_ID`.
+- `expires_in`: The number of seconds the posted activity should expire in. When a posted activity expires it will be deleted from the server, and a delete request for it will be federated. This needs to be longer than an hour.
+- `in_reply_to_conversation_id`: Will reply to a given conversation, addressing only the people who are part of the recipient set of that conversation. Sets the visibility to `direct`.
+
+## GET `/api/v1/statuses`
+
+An endpoint to get multiple statuses by IDs.
+
+Required parameters:
+
+- `ids`: array of activity ids
+
+Usage example: `GET /api/v1/statuses/?ids[]=1&ids[]=2`.
+
+Returns: array of Status.
+
+The maximum number of statuses is limited to 100 per request.
+
+## PATCH `/api/v1/accounts/update_credentials`
+
+Additional parameters can be added to the JSON body/Form data:
+
+- `no_rich_text` - if true, html tags are stripped from all statuses requested from the API
+- `hide_followers` - if true, user's followers will be hidden
+- `hide_follows` - if true, user's follows will be hidden
+- `hide_followers_count` - if true, user's follower count will be hidden
+- `hide_follows_count` - if true, user's follow count will be hidden
+- `hide_favorites` - if true, user's favorites timeline will be hidden
+- `show_role` - if true, user's role (e.g admin, moderator) will be exposed to anyone in the API
+- `default_scope` - the scope returned under `privacy` key in Source subentity
+- `pleroma_settings_store` - Opaque user settings to be saved on the backend.
+- `skip_thread_containment` - if true, skip filtering out broken threads
+- `allow_following_move` - if true, allows automatically follow moved following accounts
+- `pleroma_background_image` - sets the background image of the user. Can be set to "" (an empty string) to reset.
+- `discoverable` - if true, discovery of this account in search results and other services is allowed.
+- `actor_type` - the type of this account.
+- `accepts_chat_messages` - if false, this account will reject all chat messages.
+
+All images (avatar, banner and background) can be reset to the default by sending an empty string ("") instead of a file.
+
+### Pleroma Settings Store
+
+Pleroma has mechanism that allows frontends to save blobs of json for each user on the backend. This can be used to save frontend-specific settings for a user that the backend does not need to know about.
+
+The parameter should have a form of `{frontend_name: {...}}`, with `frontend_name` identifying your type of client, e.g. `pleroma_fe`. It will overwrite everything under this property, but will not overwrite other frontend's settings.
+
+This information is returned in the `/api/v1/accounts/verify_credentials` endpoint.
+
+## Authentication
+
+*Pleroma supports refreshing tokens.*
+
+`POST /oauth/token`
+
+Post here request with `grant_type=refresh_token` to obtain new access token. Returns an access token.
+
+## Account Registration
+
+`POST /api/v1/accounts`
+
+Has theses additional parameters (which are the same as in Pleroma-API):
+
+- `fullname`: optional
+- `bio`: optional
+- `captcha_solution`: optional, contains provider-specific captcha solution,
+- `captcha_token`: optional, contains provider-specific captcha token
+- `captcha_answer_data`: optional, contains provider-specific captcha data
+- `token`: invite token required when the registrations aren't public.
+
+## Instance
+
+`GET /api/v1/instance` has additional fields
+
+- `max_toot_chars`: The maximum characters per post
+- `chat_limit`: The maximum characters per chat message
+- `description_limit`: The maximum characters per image description
+- `poll_limits`: The limits of polls
+- `upload_limit`: The maximum upload file size
+- `avatar_upload_limit`: The same for avatars
+- `background_upload_limit`: The same for backgrounds
+- `banner_upload_limit`: The same for banners
+- `background_image`: A background image that frontends can use
+- `pleroma.metadata.features`: A list of supported features
+- `pleroma.metadata.federation`: The federation restrictions of this instance
+- `pleroma.metadata.fields_limits`: A list of values detailing the length and count limitation for various instance-configurable fields.
+- `pleroma.metadata.post_formats`: A list of the allowed post format types
+- `vapid_public_key`: The public key needed for push messages
+
+## Markers
+
+Has these additional fields under the `pleroma` object:
+
+- `unread_count`: contains number unread notifications
+
+## Streaming
+
+There is an additional `user:pleroma_chat` stream. Incoming chat messages will make the current chat be sent to this `user` stream. The `event` of an incoming chat message is `pleroma:chat_update`. The payload is the updated chat with the incoming chat message in the `last_message` field.
+
+## Not implemented
+
+Pleroma is generally compatible with the Mastodon 2.7.2 API, but some newer features and non-essential features are omitted. These features usually return an HTTP 200 status code, but with an empty response. While they may be added in the future, they are considered low priority.
+
+### Suggestions
+
+*Added in Mastodon 2.4.3*
+
+- `GET /api/v1/suggestions`: Returns an empty array, `[]`
+
+### Trends
+
+*Added in Mastodon 3.0.0*
+
+- `GET /api/v1/trends`: Returns an empty array, `[]`
+
+### Identity proofs
+
+*Added in Mastodon 2.8.0*
+
+- `GET /api/v1/identity_proofs`: Returns an empty array, `[]`
+
+### Endorsements
+
+*Added in Mastodon 2.5.0*
+
+- `GET /api/v1/endorsements`: Returns an empty array, `[]`
+
+### Profile directory
+
+*Added in Mastodon 3.0.0*
+
+- `GET /api/v1/directory`: Returns HTTP 404
+
+### Featured tags
+
+*Added in Mastodon 3.0.0*
+
+- `GET /api/v1/featured_tags`: Returns HTTP 404

docs/API/pleroma_api.md

@@ -0,0 +1,572 @@
+# Pleroma API
+
+Requests that require it can be authenticated with [an OAuth token](https://tools.ietf.org/html/rfc6749), the `_pleroma_key` cookie, or [HTTP Basic Authentication](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Authorization).
+
+Request parameters can be passed via [query strings](https://en.wikipedia.org/wiki/Query_string) or as [form data](https://www.w3.org/TR/html401/interact/forms.html). Files must be uploaded as `multipart/form-data`.
+
+## `/api/pleroma/emoji`
+### Lists the custom emoji on that server.
+* Method: `GET`
+* Authentication: not required
+* Params: none
+* Response: JSON
+* Example response:
+```json
+{
+  "girlpower": {
+    "tags": [
+      "Finmoji"
+    ],
+    "image_url": "/finmoji/128px/girlpower-128.png"
+  },
+  "education": {
+    "tags": [
+      "Finmoji"
+    ],
+    "image_url": "/finmoji/128px/education-128.png"
+  },
+  "finnishlove": {
+    "tags": [
+      "Finmoji"
+    ],
+    "image_url": "/finmoji/128px/finnishlove-128.png"
+  }
+}
+```
+* Note: Same data as Mastodon API’s `/api/v1/custom_emojis` but in a different format
+
+## `/api/pleroma/follow_import`
+### Imports your follows, for example from a Mastodon CSV file.
+* Method: `POST`
+* Authentication: required
+* Params:
+    * `list`: STRING or FILE containing a whitespace-separated list of accounts to follow
+* Response: HTTP 200 on success, 500 on error
+* Note: Users that can't be followed are silently skipped.
+
+## `/api/pleroma/captcha`
+### Get a new captcha
+* Method: `GET`
+* Authentication: not required
+* Params: none
+* Response: Provider specific JSON, the only guaranteed parameter is `type`
+* Example response: `{"type": "kocaptcha", "token": "whatever", "url": "https://captcha.kotobank.ch/endpoint", "seconds_valid": 300}`
+
+## `/api/pleroma/delete_account`
+### Delete an account
+* Method `POST`
+* Authentication: required
+* Params:
+    * `password`: user's password
+* Response: JSON. Returns `{"status": "success"}` if the deletion was successful, `{"error": "[error message]"}` otherwise
+* Example response: `{"error": "Invalid password."}`
+
+## `/api/pleroma/disable_account`
+### Disable an account
+* Method `POST`
+* Authentication: required
+* Params:
+    * `password`: user's password
+* Response: JSON. Returns `{"status": "success"}` if the account was successfully disabled, `{"error": "[error message]"}` otherwise
+* Example response: `{"error": "Invalid password."}`
+
+## `/api/pleroma/accounts/mfa`
+#### Gets current MFA settings
+* method: `GET`
+* Authentication: required
+* OAuth scope: `read:security`
+* Response: JSON. Returns `{"enabled": "false", "totp": false }`
+
+## `/api/pleroma/accounts/mfa/setup/totp`
+#### Pre-setup the MFA/TOTP method
+* method: `GET`
+* Authentication: required
+* OAuth scope: `write:security`
+* Response: JSON. Returns `{"key": [secret_key], "provisioning_uri": "[qr code uri]"  }` when successful, otherwise returns HTTP 422 `{"error": "error_msg"}`
+
+## `/api/pleroma/accounts/mfa/confirm/totp`
+#### Confirms & enables MFA/TOTP support for user account.
+* method: `POST`
+* Authentication: required
+* OAuth scope: `write:security`
+* Params:
+    * `password`: user's password
+    * `code`: token from TOTP App
+* Response: JSON. Returns `{}` if the enable was successful, HTTP 422 `{"error": "[error message]"}` otherwise
+
+
+## `/api/pleroma/accounts/mfa/totp`
+####  Disables MFA/TOTP method for user account.
+* method: `DELETE`
+* Authentication: required
+* OAuth scope: `write:security`
+* Params:
+    * `password`: user's password
+* Response: JSON. Returns `{}` if the disable was successful, HTTP 422 `{"error": "[error message]"}` otherwise
+* Example response: `{"error": "Invalid password."}`
+
+## `/api/pleroma/accounts/mfa/backup_codes`
+####  Generstes backup codes MFA for user account.
+* method: `GET`
+* Authentication: required
+* OAuth scope: `write:security`
+* Response: JSON. Returns `{"codes": codes}`when successful, otherwise HTTP 422 `{"error": "[error message]"}`
+
+## `/api/pleroma/admin/`
+See [Admin-API](admin_api.md)
+
+## `/api/v1/pleroma/notifications/read`
+### Mark notifications as read
+* Method `POST`
+* Authentication: required
+* Params (mutually exclusive):
+    * `id`: a single notification id to read
+    * `max_id`: read all notifications up to this id
+* Response: Notification entity/Array of Notification entities that were read. In case of `max_id`, only the first 80 read notifications will be returned.
+
+## `/api/v1/pleroma/accounts/:id/subscribe`
+### Subscribe to receive notifications for all statuses posted by a user
+* Method `POST`
+* Authentication: required
+* Params:
+    * `id`: account id to subscribe to
+* Response: JSON, returns a mastodon relationship object on success, otherwise returns `{"error": "error_msg"}`
+* Example response:
+```json
+{
+  "id": "abcdefg",
+  "following": true,
+  "followed_by": false,
+  "blocking": false,
+  "muting": false,
+  "muting_notifications": false,
+  "subscribing": true,
+  "requested": false,
+  "domain_blocking": false,
+  "showing_reblogs": true,
+  "endorsed": false
+}
+```
+
+## `/api/v1/pleroma/accounts/:id/unsubscribe`
+### Unsubscribe to stop receiving notifications from user statuses
+* Method `POST`
+* Authentication: required
+* Params:
+    * `id`: account id to unsubscribe from
+* Response: JSON, returns a mastodon relationship object on success, otherwise returns `{"error": "error_msg"}`
+* Example response:
+```json
+{
+  "id": "abcdefg",
+  "following": true,
+  "followed_by": false,
+  "blocking": false,
+  "muting": false,
+  "muting_notifications": false,
+  "subscribing": false,
+  "requested": false,
+  "domain_blocking": false,
+  "showing_reblogs": true,
+  "endorsed": false
+}
+```
+
+## `/api/v1/pleroma/accounts/:id/favourites`
+### Returns favorites timeline of any user
+* Method `GET`
+* Authentication: not required
+* Params:
+    * `id`: the id of the account for whom to return results
+    * `limit`: optional, the number of records to retrieve
+    * `since_id`: optional, returns results that are more recent than the specified id
+    * `max_id`: optional, returns results that are older than the specified id
+* Response: JSON, returns a list of Mastodon Status entities on success, otherwise returns `{"error": "error_msg"}`
+* Example response:
+```json
+[
+  {
+    "account": {
+      "id": "9hptFmUF3ztxYh3Svg",
+      "url": "https://pleroma.example.org/users/nick2",
+      "username": "nick2",
+      ...
+    },
+    "application": {"name": "Web", "website": null},
+    "bookmarked": false,
+    "card": null,
+    "content": "This is :moominmamma: note 0",
+    "created_at": "2019-04-15T15:42:15.000Z",
+    "emojis": [],
+    "favourited": false,
+    "favourites_count": 1,
+    "id": "9hptFmVJ02khbzYJaS",
+    "in_reply_to_account_id": null,
+    "in_reply_to_id": null,
+    "language": null,
+    "media_attachments": [],
+    "mentions": [],
+    "muted": false,
+    "pinned": false,
+    "pleroma": {
+      "content": {"text/plain": "This is :moominmamma: note 0"},
+      "conversation_id": 13679,
+      "local": true,
+      "spoiler_text": {"text/plain": "2hu"}
+    },
+    "reblog": null,
+    "reblogged": false,
+    "reblogs_count": 0,
+    "replies_count": 0,
+    "sensitive": false,
+    "spoiler_text": "2hu",
+    "tags": [{"name": "2hu", "url": "/tag/2hu"}],
+    "uri": "https://pleroma.example.org/objects/198ed2a1-7912-4482-b559-244a0369e984",
+    "url": "https://pleroma.example.org/notice/9hptFmVJ02khbzYJaS",
+    "visibility": "public"
+  }
+]
+```
+
+## `/api/v1/pleroma/accounts/update_*`
+### Set and clear account avatar, banner, and background
+
+- PATCH `/api/v1/pleroma/accounts/update_avatar`: Set/clear user avatar image
+- PATCH `/api/v1/pleroma/accounts/update_banner`: Set/clear user banner image
+- PATCH `/api/v1/pleroma/accounts/update_background`: Set/clear user background image
+
+## `/api/v1/pleroma/accounts/confirmation_resend`
+### Resend confirmation email
+* Method `POST`
+* Params:
+    * `email`: email of that needs to be verified
+* Authentication: not required
+* Response: 204 No Content
+
+## `/api/v1/pleroma/mascot`
+### Gets user mascot image
+* Method `GET`
+* Authentication: required
+
+* Response: JSON. Returns a mastodon media attachment entity.
+* Example response:
+```json
+{
+    "id": "abcdefg",
+    "url": "https://pleroma.example.org/media/abcdefg.png",
+    "type": "image",
+    "pleroma": {
+        "mime_type": "image/png"
+    }
+}
+```
+
+### Updates user mascot image
+* Method `PUT`
+* Authentication: required
+* Params:
+    * `file`: Multipart image
+* Response: JSON. Returns a mastodon media attachment entity
+  when successful, otherwise returns HTTP 415 `{"error": "error_msg"}`
+* Example response:
+```json
+{
+    "id": "abcdefg",
+    "url": "https://pleroma.example.org/media/abcdefg.png",
+    "type": "image",
+    "pleroma": {
+        "mime_type": "image/png"
+    }
+}
+```
+* Note: Behaves exactly the same as `POST /api/v1/upload`.
+  Can only accept images - any attempt to upload non-image files will be met with `HTTP 415 Unsupported Media Type`.
+
+## `/api/pleroma/notification_settings`
+### Updates user notification settings
+* Method `PUT`
+* Authentication: required
+* Params:
+    * `block_from_strangers`: BOOLEAN field, blocks notifications from accounts you do not follow
+    * `hide_notification_contents`: BOOLEAN field. When set to true, it removes the contents of a message from the push notification.
+* Response: JSON. Returns `{"status": "success"}` if the update was successful, otherwise returns `{"error": "error_msg"}`
+
+## `/api/pleroma/healthcheck`
+### Healthcheck endpoint with additional system data.
+* Method `GET`
+* Authentication: not required
+* Params: none
+* Response: JSON, statuses (200 - healthy, 503 unhealthy).
+* Example response:
+```json
+{
+  "pool_size": 0, # database connection pool
+  "active": 0, # active processes
+  "idle": 0, # idle processes
+  "memory_used": 0.00, # Memory used
+  "healthy": true, # Instance state
+  "job_queue_stats": {} # Job queue stats
+}
+```
+
+## `/api/pleroma/change_email`
+### Change account email
+* Method `POST`
+* Authentication: required
+* Params:
+    * `password`: user's password
+    * `email`: new email
+* Response: JSON. Returns `{"status": "success"}` if the change was successful, `{"error": "[error message]"}` otherwise
+* Note: Currently, Mastodon has no API for changing email. If they add it in future it might be incompatible with Pleroma.
+
+# Pleroma Conversations
+
+Pleroma Conversations have the same general structure that Mastodon Conversations have. The behavior differs in the following ways when using these endpoints:
+
+1. Pleroma Conversations never add or remove recipients, unless explicitly changed by the user.
+2. Pleroma Conversations statuses can be requested by Conversation id.
+3. Pleroma Conversations can be replied to.
+
+Conversations have the additional field `recipients` under the `pleroma` key. This holds a list of all the accounts that will receive a message in this conversation.
+
+The status posting endpoint takes an additional parameter, `in_reply_to_conversation_id`, which, when set, will set the visiblity to direct and address only the people who are the recipients of that Conversation.
+
+⚠ Conversation IDs can be found in direct messages with the `pleroma.direct_conversation_id` key, do not confuse it with `pleroma.conversation_id`.
+
+## `GET /api/v1/pleroma/conversations/:id/statuses`
+### Timeline for a given conversation
+* Method `GET`
+* Authentication: required
+* Params: Like other timelines
+* Response: JSON, statuses (200 - healthy, 503 unhealthy).
+
+## `GET /api/v1/pleroma/conversations/:id`
+### The conversation with the given ID.
+* Method `GET`
+* Authentication: required
+* Params: None
+* Response: JSON, statuses (200 - healthy, 503 unhealthy).
+
+## `PATCH /api/v1/pleroma/conversations/:id`
+### Update a conversation. Used to change the set of recipients.
+* Method `PATCH`
+* Authentication: required
+* Params:
+    * `recipients`: A list of ids of users that should receive posts to this conversation. This will replace the current list of recipients, so submit the full list. The owner of owner of the conversation will always be part of the set of recipients, though.
+* Response: JSON, statuses (200 - healthy, 503 unhealthy)
+
+## `POST /api/v1/pleroma/conversations/read`
+### Marks all user's conversations as read.
+* Method `POST`
+* Authentication: required
+* Params: None
+* Response: JSON, returns a list of Mastodon Conversation entities that were marked as read (200 - healthy, 503 unhealthy).
+
+## `GET /api/pleroma/emoji/packs/import`
+### Imports packs from filesystem
+* Method `GET`
+* Authentication: required
+* Params: None
+* Response: JSON, returns a list of imported packs.
+
+## `GET /api/pleroma/emoji/packs/remote`
+### Make request to another instance for packs list
+* Method `GET`
+* Authentication: required
+* Params:
+  * `url`: url of the instance to get packs from
+* Response: JSON with the pack list, hashmap with pack name and pack contents
+
+## `POST /api/pleroma/emoji/packs/download`
+### Download pack from another instance
+* Method `POST`
+* Authentication: required
+* Params:
+  * `url`: url of the instance to download from
+  * `name`: pack to download from that instance
+  * `as`: (*optional*) name how to save pack
+* Response: JSON, "ok" with 200 status if the pack was downloaded, or 500 if there were
+  errors downloading the pack
+
+## `POST /api/pleroma/emoji/packs/:name`
+### Creates an empty pack
+* Method `POST`
+* Authentication: required
+* Params: None
+* Response: JSON, "ok" and 200 status or 409 if the pack with that name already exists
+
+## `PATCH /api/pleroma/emoji/packs/:name`
+### Updates (replaces) pack metadata
+* Method `PATCH`
+* Authentication: required
+* Params:
+  * `metadata`: metadata to replace the old one
+    * `license`: Pack license
+    * `homepage`: Pack home page url
+    * `description`: Pack description
+    * `fallback-src`: Fallback url to download pack from
+    * `fallback-src-sha256`: SHA256 encoded for fallback pack archive
+    * `share-files`: is pack allowed for sharing (boolean)
+* Response: JSON, updated "metadata" section of the pack and 200 status or 400 if there was a
+  problem with the new metadata (the error is specified in the "error" part of the response JSON)
+
+## `DELETE /api/pleroma/emoji/packs/:name`
+### Delete a custom emoji pack
+* Method `DELETE`
+* Authentication: required
+* Params: None
+* Response: JSON, "ok" and 200 status or 500 if there was an error deleting the pack
+
+## `POST /api/pleroma/emoji/packs/:name/files`
+### Add new file to the pack
+* Method `POST`
+* Authentication: required
+* Params:
+  * `file`: file needs to be uploaded with the multipart request or link to remote file.
+  * `shortcode`: (*optional*) shortcode for new emoji, must be unique for all emoji. If not sended, shortcode will be taken from original filename.
+  * `filename`: (*optional*) new emoji file name. If not specified will be taken from original filename.
+* Response: JSON, list of files for updated pack (hashmap -> shortcode => filename) with status 200, either error status with error message.
+
+## `PATCH /api/pleroma/emoji/packs/:name/files`
+### Update emoji file from pack
+* Method `PATCH`
+* Authentication: required
+* Params:
+  * `shortcode`: emoji file shortcode
+  * `new_shortcode`: new emoji file shortcode
+  * `new_filename`: new filename for emoji file
+  * `force`: (*optional*) with true value to overwrite existing emoji with new shortcode
+* Response: JSON, list with updated files for updated pack (hashmap -> shortcode => filename) with status 200, either error status with error message.
+
+## `DELETE /api/pleroma/emoji/packs/:name/files`
+### Delete emoji file from pack
+* Method `DELETE`
+* Authentication: required
+* Params:
+  * `shortcode`: emoji file shortcode
+* Response: JSON, list with updated files for updated pack (hashmap -> shortcode => filename) with status 200, either error status with error message.
+
+## `GET /api/pleroma/emoji/packs`
+
+### Lists local custom emoji packs
+
+* Method `GET`
+* Authentication: not required
+* Params:
+  * `page`: page number for packs (default 1)
+  * `page_size`: page size for packs (default 50)
+* Response: `packs` key with JSON hashmap of pack name to pack contents and `count` key for count of packs.
+
+```json
+{
+  "packs": {
+    "pack_name": {...}, // pack contents
+    ...
+  },
+  "count": 0 // packs count
+}
+```
+
+## `GET /api/pleroma/emoji/packs/:name`
+
+### Get pack.json for the pack
+
+* Method `GET`
+* Authentication: not required
+* Params:
+  * `page`: page number for files (default 1)
+  * `page_size`: page size for files (default 30)
+* Response: JSON, pack json with `files`, `files_count` and `pack` keys with 200 status or 404 if the pack does not exist.
+
+```json
+{
+  "files": {...},
+  "files_count": 0, // emoji count in pack
+  "pack": {...}
+}
+```
+
+## `GET /api/pleroma/emoji/packs/:name/archive`
+### Requests a local pack archive from the instance
+* Method `GET`
+* Authentication: not required
+* Params: None
+* Response: the archive of the pack with a 200 status code, 403 if the pack is not set as shared,
+  404 if the pack does not exist
+
+## `GET /api/v1/pleroma/accounts/:id/scrobbles`
+### Requests a list of current and recent Listen activities for an account
+* Method `GET`
+* Authentication: not required
+* Params: None
+* Response: An array of media metadata entities.
+* Example response:
+```json
+[
+   {
+       "account": {...},
+       "id": "1234",
+       "title": "Some Title",
+       "artist": "Some Artist",
+       "album": "Some Album",
+       "length": 180000,
+       "created_at": "2019-09-28T12:40:45.000Z"
+   }
+]
+```
+
+## `POST /api/v1/pleroma/scrobble`
+### Creates a new Listen activity for an account
+* Method `POST`
+* Authentication: required
+* Params:
+  * `title`: the title of the media playing
+  * `album`: the album of the media playing [optional]
+  * `artist`: the artist of the media playing [optional]
+  * `length`: the length of the media playing [optional]
+* Response: the newly created media metadata entity representing the Listen activity
+
+# Emoji Reactions
+
+Emoji reactions work a lot like favourites do. They make it possible to react to a post with a single emoji character. To detect the presence of this feature, you can check `pleroma_emoji_reactions` entry in the features list of nodeinfo.
+
+## `PUT /api/v1/pleroma/statuses/:id/reactions/:emoji`
+### React to a post with a unicode emoji
+* Method: `PUT`
+* Authentication: required
+* Params: `emoji`: A single character unicode emoji
+* Response: JSON, the status.
+
+## `DELETE /api/v1/pleroma/statuses/:id/reactions/:emoji`
+### Remove a reaction to a post with a unicode emoji
+* Method: `DELETE`
+* Authentication: required
+* Params: `emoji`: A single character unicode emoji
+* Response: JSON, the status.
+
+## `GET /api/v1/pleroma/statuses/:id/reactions`
+### Get an object of emoji to account mappings with accounts that reacted to the post
+* Method: `GET`
+* Authentication: optional
+* Params: None
+* Response: JSON, a list of emoji/account list tuples, sorted by emoji insertion date, in ascending order, e.g, the first emoji in the list is the oldest.
+* Example Response:
+```json
+[
+  {"name": "😀", "count": 2, "me": true, "accounts": [{"id" => "xyz.."...}, {"id" => "zyx..."}]},
+  {"name": "☕", "count": 1, "me": false, "accounts": [{"id" => "abc..."}]}
+]
+```
+
+## `GET /api/v1/pleroma/statuses/:id/reactions/:emoji`
+### Get an object of emoji to account mappings with accounts that reacted to the post for a specific emoji
+* Method: `GET`
+* Authentication: optional
+* Params: None
+* Response: JSON, a list of emoji/account list tuples
+* Example Response:
+```json
+[
+  {"name": "😀", "count": 2, "me": true, "accounts": [{"id" => "xyz.."...}, {"id" => "zyx..."}]}
+]
+```

docs/API/prometheus.md

@@ -0,0 +1,22 @@
+# Prometheus Metrics
+
+Pleroma includes support for exporting metrics via the [prometheus_ex](https://github.com/deadtrickster/prometheus.ex) library.
+
+## `/api/pleroma/app_metrics`
+### Exports Prometheus application metrics
+* Method: `GET`
+* Authentication: not required
+* Params: none
+* Response: JSON
+
+## Grafana
+### Config example
+The following is a config example to use with [Grafana](https://grafana.com)
+
+```
+  - job_name: 'beam'
+    metrics_path: /api/pleroma/app_metrics
+    scheme: https
+    static_configs:
+    - targets: ['pleroma.soykaf.com']
+```

docs/administration/CLI_tasks/config.md

@@ -1,4 +1,4 @@
-# Transferring the config to/from the database
+# Transfering the config to/from the database
 
 {! backend/administration/CLI_tasks/general_cli_task_info.include !}
 
@@ -32,141 +32,14 @@
     config :pleroma, configurable_from_database: false
     ```
 
-Options:
-
-- `<path>` - where to save migrated config. E.g. `--path=/tmp`. If file saved into non-standard folder, you must manually copy file into directory where Pleroma can read it. For OTP install path will be `PLEROMA_CONFIG_PATH` or `/etc/pleroma`. For installation from source - `config` directory in the pleroma folder.
-- `<env>` - environment, for which is migrated config. By default is `prod`.
-- To delete transferred settings from database optional flag `-d` can be used
+To delete transfered settings from database optional flag `-d` can be used. `<env>` is `prod` by default.
 
 === "OTP"
     ```sh
-     ./bin/pleroma_ctl config migrate_from_db [--env=<env>] [-d] [--path=<path>]
+     ./bin/pleroma_ctl config migrate_from_db [--env=<env>] [-d]
     ```
 
 === "From Source"
     ```sh
-    mix pleroma.config migrate_from_db [--env=<env>] [-d] [--path=<path>]
+    mix pleroma.config migrate_from_db [--env=<env>] [-d]
     ```
-
-## Dump all of the config settings defined in the database
-
-=== "OTP"
-
-    ```sh
-     ./bin/pleroma_ctl config dump
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.config dump
-    ```
-
-## List individual configuration groups in the database
-
-=== "OTP"
-
-    ```sh
-     ./bin/pleroma_ctl config groups
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.config groups
-    ```
-
-## Dump the saved configuration values for a specific group or key
-
-e.g., this shows all the settings under `config :pleroma`
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl config dump pleroma
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.config dump pleroma
-    ```
-
-To get values under a specific key:
-
-e.g., this shows all the settings under `config :pleroma, :instance`
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl config dump pleroma instance
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.config dump pleroma instance
-    ```
-
-## Delete the saved configuration values for a specific group or key
-
-e.g., this deletes all the settings under `config :tesla`
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl config delete [--force] tesla
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.config delete [--force] tesla
-    ```
-
-To delete values under a specific key:
-
-e.g., this deletes all the settings under `config :phoenix, :stacktrace_depth`
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl config delete [--force] phoenix stacktrace_depth
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.config delete [--force] phoenix stacktrace_depth
-    ```
-
-## Remove all settings from the database
-
-This forcibly removes all saved values in the database.
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl config [--force] reset
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.config [--force] reset
-
-    ```
-
-## Remove invalid MRF modules from the database
-
-This forcibly removes any enabled MRF that does not exist and will fix the ability of the instance to start.
-
-=== "OTP"
-    ```sh
-    ./bin/pleroma_ctl config fix_mrf_policies
-    ```
-
-=== "From Source"
-    ```sh
-    mix pleroma.config fix_mrf_policies
-    ```

docs/administration/CLI_tasks/database.md

@@ -21,18 +21,16 @@ Replaces embedded objects with references to them in the `objects` table. Only n
     mix pleroma.database remove_embedded_objects [option ...]
     ```
 
+
 ### Options
 - `--vacuum` - run `VACUUM FULL` after the embedded objects are replaced with their references
 
 ## Prune old remote posts from the database
 
-This will prune remote posts older than 90 days (configurable with [`config :pleroma, :instance, remote_post_retention_days`](../../configuration/cheatsheet.md#instance)) from the database. Pruned posts may be refetched in some cases.
-
-!!! note
-    The disk space will only be reclaimed after a proper vacuum. By default Postgresql does this for you on a regular basis, but if your instance has been running for a long time and there are many rows deleted, it may be advantageous to use `VACUUM FULL` (e.g. by using the `--vacuum` option).
+This will prune remote posts older than 90 days (configurable with [`config :pleroma, :instance, remote_post_retention_days`](../../configuration/cheatsheet.md#instance)) from the database, they will be refetched from source when accessed.
 
 !!! danger
-    You may run out of disk space during the execution of the task or vacuuming if you don't have about 1/3rds of the database size free. Vacuum causes a substantial increase in I/O traffic, and may lead to a degraded experience while it is running.
+    The disk space will only be reclaimed after `VACUUM FULL`. You may run out of disk space during the execution of the task or vacuuming if you don't have about 1/3rds of the database size free.
 
 === "OTP"
 
@@ -47,11 +45,7 @@ This will prune remote posts older than 90 days (configurable with [`config :ple
     ```
 
 ### Options
-
-- `--keep-threads` - Don't prune posts when they are part of a thread where at least one post has seen local interaction (e.g. one of the posts is a local post, or is favourited by a local user, or has been repeated by a local user...). It also won't 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.  Note: this can take a very long time.
-- `--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.
+- `--vacuum` - run `VACUUM FULL` after the objects are pruned
 
 ## 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.**
@@ -150,21 +141,3 @@ but should only be run if necessary. **It is safe to cancel this.**
     ```sh
     mix pleroma.database ensure_expiration
     ```
-
-## Change Text Search Configuration
-
-Change `default_text_search_config` for database and (if necessary) text_search_config used in index, then rebuild index (it may take time). 
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl database set_text_search_config english
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.database set_text_search_config english
-    ```
-
-See [PostgreSQL documentation](https://www.postgresql.org/docs/current/textsearch-configuration.html) and `docs/configuration/howto_search_cjk.md` for more detail.

docs/administration/CLI_tasks/email.md

@@ -1,4 +1,4 @@
-# EMail administration tasks
+# Managing emails
 
 {! backend/administration/CLI_tasks/general_cli_task_info.include !}
 
@@ -16,7 +16,8 @@
     mix pleroma.email test [--to <destination email address>]
     ```
 
-Example:
+
+Example: 
 
 === "OTP"
 
@@ -29,17 +30,3 @@ Example:
     ```sh
     mix pleroma.email test --to root@example.org
     ```
-
-## Send confirmation emails to all unconfirmed user accounts
-
-=== "OTP"
-
-    ```sh
-     ./bin/pleroma_ctl email resend_confirmation_emails
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.email resend_confirmation_emails
-    ```

docs/administration/CLI_tasks/frontend.md

@@ -1,28 +1,17 @@
 # Managing frontends
 
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl frontend install <frontend> [--ref <ref>] [--file <file>] [--build-url <build-url>] [--path <path>] [--build-dir <build-dir>]
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.frontend install <frontend> [--ref <ref>] [--file <file>] [--build-url <build-url>] [--path <path>] [--build-dir <build-dir>]
-    ```
+`mix pleroma.frontend install <frontend> [--ref <ref>] [--file <file>] [--build-url <build-url>] [--path <path>] [--build-dir <build-dir>]`
 
 Frontend can be installed either from local zip file, or automatically downloaded from the web.
 
-You can give all the options directly on the command line, but missing information will be filled out by looking at the data configured under `frontends.available` in the config files.
-
-Currently, known `<frontend>` values are:
+You can give all the options directly on the command like, but missing information will be filled out by looking at the data configured under `frontends.available` in the config files.
 
+Currently known `<frontend>` values are:
 - [admin-fe](https://git.pleroma.social/pleroma/admin-fe)
 - [kenoma](http://git.pleroma.social/lambadalambda/kenoma)
 - [pleroma-fe](http://git.pleroma.social/pleroma/pleroma-fe)
 - [fedi-fe](https://git.pleroma.social/pleroma/fedi-fe)
-- [soapbox](https://gitlab.com/soapbox-pub/soapbox)
+- [soapbox-fe](https://gitlab.com/soapbox-pub/soapbox-fe)
 
 You can still install frontends that are not configured, see below.
 
@@ -30,67 +19,51 @@ You can still install frontends that are not configured, see below.
 
 For a frontend configured under the `available` key, it's enough to install it by name.
 
-=== "OTP"
+```sh tab="OTP"
+./bin/pleroma_ctl frontend install pleroma
+```
 
-    ```sh
-    ./bin/pleroma_ctl frontend install pleroma
-    ```
+```sh tab="From Source"
+mix pleroma.frontend install pleroma
+```
 
-=== "From Source"
+This will download the latest build for the 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`).
 
-    ```sh
-    mix pleroma.frontend install pleroma
-    ```
+You can override any of the details. To install a pleroma build from a different url, you could do this:
 
-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`).
+```sh tab="OPT"
+./bin/pleroma_ctl frontend install pleroma --ref 2hu_edition --build-url https://example.org/raymoo.zip
+```
 
-You can override any of the details. To install a pleroma build from a different URL, you could do this:
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl frontend install pleroma --ref 2hu_edition --build-url https://example.org/raymoo.zip
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.frontend install pleroma --ref 2hu_edition --build-url https://example.org/raymoo.zip
-    ```
+```sh tab="From Source"
+mix pleroma.frontend install pleroma --ref 2hu_edition --build-url https://example.org/raymoo.zip
+```
 
 Similarly, you can also install from a local zip file.
 
-=== "OTP"
+```sh tab="OTP"
+./bin/pleroma_ctl frontend install pleroma --ref mybuild --file ~/Downloads/doomfe.zip
+```
 
-    ```sh
-    ./bin/pleroma_ctl frontend install pleroma --ref mybuild --file ~/Downloads/doomfe.zip
-    ```
+```sh tab="From Source"
+mix pleroma.frontend install pleroma --ref mybuild --file ~/Downloads/doomfe.zip
+```
 
-=== "From Source"
+The resulting frontend will always be installed into a folder of this template: `${instance_static}/frontends/${name}/${ref}`
 
-    ```sh
-    mix pleroma.frontend install pleroma --ref mybuild --file ~/Downloads/doomfe.zip
-    ```
-
-The resulting frontend will always be installed into a folder of this template: `${instance_static}/frontends/${name}/${ref}`.
-
-Careful: This folder will be completely replaced on installation.
+Careful: This folder will be completely replaced on installation
 
 ## Example installation for an unknown frontend
 
-The installation process is the same, but you will have to give all the needed options on the command line. For example:
+The installation process is the same, but you will have to give all the needed options on the commond line. For example:
 
-=== "OTP"
+```sh tab="OTP"
+./bin/pleroma_ctl frontend install gensokyo --ref master --build-url https://gensokyo.2hu/builds/marisa.zip
+```
 
-    ```sh
-    ./bin/pleroma_ctl frontend install gensokyo --ref master --build-url https://gensokyo.2hu/builds/marisa.zip
-    ```
+```sh tab="From Source"
+mix pleroma.frontend install gensokyo --ref master --build-url https://gensokyo.2hu/builds/marisa.zip
+```
 
-=== "From Source"
-
-    ```sh
-    mix pleroma.frontend install gensokyo --ref master --build-url https://gensokyo.2hu/builds/marisa.zip
-    ```
-
-If you don't have a zip file but just want to install a frontend from a local path, you can simply copy the files over a folder of this template: `${instance_static}/frontends/${name}/${ref}`.
+If you don't have a zip file but just want to install a frontend from a local path, you can simply copy the files over a folder of this template: `${instance_static}/frontends/${name}/${ref}`
 

docs/administration/CLI_tasks/instance.md

@@ -37,9 +37,3 @@ If any of the options are left unspecified, you will be prompted interactively.
 - `--static-dir <path>` - the directory custom public files should be read from (custom emojis, frontend bundle overrides, robots.txt, etc.)
 - `--listen-ip <ip>` - the ip the app should listen to, defaults to 127.0.0.1
 - `--listen-port <port>` - the port the app should listen to, defaults to 4000
-- `--strip-uploads-location <Y|N>` - use ExifTool to strip uploads of sensitive location data
-- `--read-uploads-description <Y|N>` - use ExifTool to read image descriptions from uploads
-- `--anonymize-uploads <Y|N>` - randomize uploaded filenames
-- `--dedupe-uploads <Y|N>` - store files based on their hash to reduce data storage requirements if duplicates are uploaded with different filenames
-- `--skip-release-env` - skip generation the release environment file
-- `--release-env-file` - release environment file path

docs/administration/CLI_tasks/user.md

@@ -133,20 +133,22 @@
     mix pleroma.user sign_out <nickname>
     ```
 
-## Activate a user
+
+## Deactivate or activate a user
 
 === "OTP"
 
     ```sh
-     ./bin/pleroma_ctl user activate NICKNAME
+     ./bin/pleroma_ctl user toggle_activated <nickname>
     ```
 
 === "From Source"
 
     ```sh
-    mix pleroma.user activate NICKNAME
+    mix pleroma.user toggle_activated <nickname>
     ```
 
+
 ## Deactivate a user and unsubscribes local users from the user
 
 === "OTP"
@@ -222,10 +224,9 @@
     ```
 
 ### Options
-- `--admin`/`--no-admin` - whether the user should be an admin
-- `--confirmed`/`--no-confirmed` - whether the user account is confirmed
 - `--locked`/`--no-locked` - whether the user should be locked
 - `--moderator`/`--no-moderator` - whether the user should be a moderator
+- `--admin`/`--no-admin` - whether the user should be an admin
 
 ## Add tags to a user
 
@@ -262,41 +263,11 @@
 === "OTP"
 
     ```sh
-     ./bin/pleroma_ctl user confirm <nickname>
+     ./bin/pleroma_ctl user toggle_confirmed <nickname>
     ```
 
 === "From Source"
 
     ```sh
-    mix pleroma.user confirm <nickname>
-    ```
-
-## Set confirmation status for all regular active users
-*Admins and moderators are excluded*
-
-=== "OTP"
-
-    ```sh
-     ./bin/pleroma_ctl user confirm_all
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.user confirm_all
-    ```
-
-## Revoke confirmation status for all regular active users
-*Admins and moderators are excluded*
-
-=== "OTP"
-
-    ```sh
-     ./bin/pleroma_ctl user unconfirm_all
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.user unconfirm_all
+    mix pleroma.user toggle_confirmed <nickname>
     ```

docs/administration/backup.md

@@ -5,25 +5,20 @@
 1. Stop the Pleroma service.
 2. Go to the working directory of Pleroma (default is `/opt/pleroma`)
 3. Run `sudo -Hu postgres pg_dump -d <pleroma_db> --format=custom -f </path/to/backup_location/pleroma.pgdump>` (make sure the postgres user has write access to the destination file)
-4. Copy `pleroma.pgdump`, `config/prod.secret.exs`, `config/setup_db.psql` (if still available) and the `uploads` folder to your backup destination. If you have other modifications, copy those changes too.
+4. Copy `pleroma.pgdump`, `config/prod.secret.exs` and the `uploads` folder to your backup destination. If you have other modifications, copy those changes too.
 5. Restart the Pleroma service.
 
 ## Restore/Move
 
-1. Optionally reinstall Pleroma (either on the same server or on another server if you want to move servers).
+1. Optionally reinstall Pleroma (either on the same server or on another server if you want to move servers). Try to use the same database name.
 2. Stop the Pleroma service.
 3. Go to the working directory of Pleroma (default is `/opt/pleroma`)
 4. Copy the above mentioned files back to their original position.
-5. Drop the existing database and user if restoring in-place. `sudo -Hu postgres psql -c 'DROP DATABASE <pleroma_db>;';` `sudo -Hu postgres psql -c 'DROP USER <pleroma_db>;'`
-6. Restore the database schema and pleroma postgres role the with the original `setup_db.psql` if you have it: `sudo -Hu postgres psql -f config/setup_db.psql`. 
-
-  Alternatively, run the `mix pleroma.instance gen` task again. You can ignore most of the questions, but make the database user, name, and password the same as found in your backup of `config/prod.secret.exs`. Then run the restoration of the pleroma role and schema with of the generated `config/setup_db.psql` as instructed above. You may delete the `config/generated_config.exs` file as it is not needed.
-
-7. Now restore the Pleroma instance's data into the empty database schema: `sudo -Hu postgres pg_restore -d <pleroma_db> -v -1 </path/to/backup_location/pleroma.pgdump>`
-8. If you installed a newer Pleroma version, you should run `mix ecto.migrate`[^1]. This task performs database migrations, if there were any.
-9. Restart the Pleroma 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/pleroma.nginx` config sample or reference the Pleroma installation guide for your OS which contains the Nginx configuration instructions.
+5. Drop the existing database and recreate an empty one `sudo -Hu postgres psql -c 'DROP DATABASE <pleroma_db>;';` `sudo -Hu postgres psql -c 'CREATE DATABASE <pleroma_db>;';`
+6. Run `sudo -Hu postgres pg_restore -d <pleroma_db> -v -1 </path/to/backup_location/pleroma.pgdump>`
+7. If you installed a newer Pleroma version, you should run `mix ecto.migrate`[^1]. This task performs database migrations, if there were any.
+8. Restart the Pleroma service.
+9. Run `sudo -Hu postgres vacuumdb --all --analyze-in-stages`. This will quickly generate the statistics so that postgres can properly plan queries.
 
 [^1]: Prefix with `MIX_ENV=prod` to run it using the production config file.
 
@@ -31,11 +26,11 @@
 
 1. Optionally you can remove the users of your instance. This will trigger delete requests for their accounts and posts. Note that this is 'best effort' and doesn't mean that all traces of your instance will be gone from the fediverse.
     * You can do this from the admin-FE where you can select all local users and delete the accounts using the *Moderate multiple users* dropdown.
-    * You can also list local users and delete them individually using the CLI tasks for [Managing users](./CLI_tasks/user.md).
+    * You can also list local users and delete them individualy using the CLI tasks for [Managing users](./CLI_tasks/user.md).
 2. Stop the Pleroma service `systemctl stop pleroma`
 3. Disable pleroma from systemd `systemctl disable pleroma`
 4. Remove the files and folders you created during installation (see installation guide). This includes the pleroma, nginx and systemd files and folders.
 5. Reload nginx now that the configuration is removed `systemctl reload nginx`
-6. Remove the database and database user `sudo -Hu postgres psql -c 'DROP DATABASE <pleroma_db>;';` `sudo -Hu postgres psql -c 'DROP USER <pleroma_db>;'`
+6. Remove the database and database user `sudo -Hu postgres psql -c 'DROP DATABASE <pleroma_db>;';` `sudo -Hu postgres psql -c 'DROP USER <pleroma_db>;';`
 7. Remove the system user `userdel pleroma`
 8. Remove the dependencies that you don't need anymore (see installation guide). Make sure you don't remove packages that are still needed for other software that you have running!

docs/administration/frontends-management.md

@@ -1,71 +0,0 @@
-# Managing installed frontends
-
-Pleroma lets you install multiple frontends including multiple versions of same frontend. Right now it's only possible to switch which frontend is the default, but in the future it would be possible for user to select which frontend they prefer to use.
-
-As of 2.6.0 there are two ways of managing frontends - through PleromaFE's Admin Dashboard (preferred, easier method) or through AdminFE (clunky but also works on versions older than 2.6.0).
-
-!!! note
-    Managing frontends through UI requires [in-database configuration](../configuration/howto_database_config.md) to be enabled (default on newer instances but might be off on older ones).
-
-## How it works
-
-When installing frontends, it creates a folder in [static directory](../configuration/static_dir.md) that follows this pattern: `/frontends/${front-end name}/${front-end version}/`, puts contents of the built frontend in there. Then when accessing the server backend checks what front-end name and version are set to be default and serves index.html and assets from appropriate path.
-
-!!! warning
-
-    If you've been putting your frontend build directly into static dir as an antiquated way of serving custom frontend, this system will not work and will still serve the custom index.html you put in there. You can still serve custom frontend builds if you put your build into `/frontends/$name/$version` instead and set the "default frontend" fields appropriately.
-    
-Currently, there is no backup system, i.e. when installing `master` version it _will_ overwrite installed `master` version, for now if you want to keep previous version you should back it up manually, i.e. running `cp -r ./frontends/pleroma-fe/master ./frontends/pleroma-fe/master_old` in your static dir.
-
-## Managing front-ends through Admin Dashboard
-
-Open up Admin Dashboard (gauge icon in top bar, same as where link to AdminFE was),__
-![location of Admin Dashboard icon](../assets/admin_dash_location.png)
-switch to "Front-ends" tab.  
-![screenshot of Front-ends tab](../assets/frontends_tab.png)
-This page is designed to be self-explanatory and easy to use, while avoiding issues and pitfalls of AdminFE, but it's also early in development, everything is subject to change.
-
-!!! warning
-    This goes without saying, but if you set default frontend to anything except >2.6.0 version of PleromaFE you'll lose the access to Admin Dashboard and will have to use AdminFE to get it back. See below on how to use AdminFE.
-
-### Limitations 
-
-Currently the list of available for install frontends is essentially hard-coded in backend's configuration, each providing only one version, with exception for PleromaFE which overrides 'pleroma-fe' to also include `develop` version. There is no way to manually install build with a URL (coming soon) nor add more available frontends to the repository (it's broken).
-
-There is also no way to tell if there is an update available or not, for now you should watch for [announcements](https://pleroma.social/announcements/) of new PleromaFE stable releases to see if there is new stable version. For `develop` version it's up to you whether you want to follow the development process or just reinstall it periodically hoping for new stuff.
-
-## Using AdminFE to manage frontends
-
-Access AdminFE either directly by going to `/pleroma/admin` of your instance or by opening Admin Dashboard and clicking the link at the bottom of the window  
-![link to open old AdminFE](../assets/old_adminfe_link.png)
-
-
-Go to Settings -> Frontend.
-
-### Installing front-ends
-
-At the very top of the page there's a list of available frontends and button to install custom front-end
-
-!!! tip
-    Remember to click "Submit" in bottom right corner to save your changes!
-
-!!! bug
-    **Available Frontends** section lets you _install_ frontends but **NOT** update/reinstall them. It's only useful for installing a frontend once.
-    
-Due to aforementioned bug, preferred way of installing frontends in AdminFE is by clicking the "Install another frontend"  
-![screenshot of admin-fe with instructions on how to install a frontend](../assets/way_to_install_frontends.png)
-and filling in the fields. Unfortunately AdminFE does not provide the raw data necessary for you to fill those fields, so your best bet is to see what backend returns in browser's devtools or refer to the [source code](https://git.pleroma.social/pleroma/pleroma/-/blob/develop/config/config.exs?ref_type=heads#L742-791). For the most part, only **Name**, **Ref** (i.e. version) and **Build URL** fields are required, although some frontends might also require **Build Directory** to work. 
-
-For pleroma-fe you can use either `master` or `develop` refs, or potentially any ref in GitLab that has artifacts for `build` job, but that's outside scope of this document.
-
-### Selecting default frontend
-
-Scroll page waaaaay down, search for "Frontends" section, subtitled "Installed frontends management", change the name and reference of the "Primary" frontend.  
-![screenshot of admin-fe with instructions on how to install a frontend](../assets/primary_frontend_section.png)
-
-
-!!! danger
-    If you change "Admin" frontend name/reference you risk losing access to AdminFE as well.
-    
-!!! warning
-    Don't put anything into the "Available" section as it will break the list of available frontends completely, including the "add another frontend" button. If you accidentally put something in there, click the trashbin icon next to "Available" to reset it and restore the frontends list.

docs/administration/updating.md

@@ -17,11 +17,10 @@ su pleroma -s $SHELL -lc "./bin/pleroma_ctl migrate"
 ## For from source installations (using git)
 
 1. Go to the working directory of Pleroma (default is `/opt/pleroma`)
-2. Run `git checkout <tagged release>` [^1]. e.g. `git checkout v2.4.5` This pulls the [tagged release](https://git.pleroma.social/pleroma/pleroma/-/releases) from upstream.
-3. Run `mix deps.get` [^1]. This pulls in any new dependencies.
+2. Run `git pull`. This pulls the latest changes from upstream.
+3. Run `mix deps.get`. This pulls in any new dependencies.
 4. Stop the Pleroma service.
-5. Run `mix ecto.migrate` [^1] [^2]. This task performs database migrations, if there were any.
+5. Run `mix ecto.migrate`[^1]. This task performs database migrations, if there were any.
 6. Start the Pleroma service.
 
-[^1]: Depending on which install guide you followed (for example on Debian/Ubuntu), you want to run `git` and `mix` tasks as `pleroma` user by adding `sudo -Hu pleroma` before the command.
-[^2]: Prefix with `MIX_ENV=prod` to run it using the production config file.
+[^1]: Prefix with `MIX_ENV=prod` to run it using the production config file.

docs/ap_extensions.md

@@ -0,0 +1,35 @@
+# ChatMessages
+
+ChatMessages are the messages sent in 1-on-1 chats. They are similar to
+`Note`s, but the addresing is done by having a single AP actor in the `to`
+field. Addressing multiple actors is not allowed. These messages are always
+private, there is no public version of them. They are created with a `Create`
+activity.
+
+Example:
+
+```json
+{
+  "actor": "http://2hu.gensokyo/users/raymoo",
+  "id": "http://2hu.gensokyo/objects/1",
+  "object": {
+    "attributedTo": "http://2hu.gensokyo/users/raymoo",
+    "content": "You expected a cute girl? Too bad.",
+    "id": "http://2hu.gensokyo/objects/2",
+    "published": "2020-02-12T14:08:20Z",
+    "to": [
+      "http://2hu.gensokyo/users/marisa"
+    ],
+    "type": "ChatMessage"
+  },
+  "published": "2018-02-12T14:08:20Z",
+  "to": [
+    "http://2hu.gensokyo/users/marisa"
+  ],
+  "type": "Create"
+}
+```
+
+This setup does not prevent multi-user chats, but these will have to go through
+a `Group`, which will be the recipient of the messages and then `Announce` them
+to the users in the `Group`.

docs/clients.md

@@ -3,110 +3,101 @@ Note: Additional clients may be working but theses are officially supporting Ple
 Feel free to contact us to be added to this list!
 
 ## Desktop
+### Roma for Desktop
+- Homepage: <https://www.pleroma.com/#desktopApp>
+- Source Code: <https://github.com/roma-apps/roma-desktop>
+- Platforms: Windows, Mac, Linux
+- Features: Streaming Ready
+
 ### Social
 - Source Code: <https://gitlab.gnome.org/World/Social>
 - Contact: [@brainblasted@social.libre.fi](https://social.libre.fi/users/brainblasted)
 - Platforms: Linux (GNOME)
 - Note(2019-01-28): Not at a pre-alpha stage yet
-- Features: MastoAPI
 
 ### Whalebird
-- Homepage: <https://whalebird.social/>
+- Homepage: <https://whalebird.org/>
 - Source Code: <https://github.com/h3poteto/whalebird-desktop>
-- Contact: [@whalebird@pleroma.io](https://pleroma.io/users/whalebird)
+- Contact: [@h3poteto@pleroma.io](https://pleroma.io/users/h3poteto)
 - Platforms: Windows, Mac, Linux
-- Features: MastoAPI, Streaming Ready
-
-### Fedistar
-- Homepage: <https://fedistar.net>
-- Source Code: <https://github.com/h3poteto/fedistar>
-- Contact: [@fedistar@pleroma.io](https://pleroma.io/users/fedistar)
-- Platforms: Windows, Mac, Linux
-- Features: MastoAPI, Streaming Ready
+- Features: Streaming Ready
 
 ## Handheld
-### AndStatus
-- Homepage: <http://andstatus.org/>
-- Source Code: <https://github.com/andstatus/andstatus/>
-- Platforms: Android
-- Features: MastoAPI, ActivityPub (Client-to-Server)
-
 ### Amaroq
 - Homepage: <https://itunes.apple.com/us/app/amaroq-for-mastodon/id1214116200>
 - Source Code: <https://github.com/ReticentJohn/Amaroq>
 - Contact: [@eurasierboy@mastodon.social](https://mastodon.social/users/eurasierboy)
 - Platforms: iOS
-- Features: MastoAPI, No Streaming
+- Features: No Streaming
 
 ### Fedilab
 - Homepage: <https://fedilab.app/>
 - Source Code: <https://framagit.org/tom79/fedilab/>
 - Contact: [@fedilab@framapiaf.org](https://framapiaf.org/users/fedilab)
 - Platforms: Android
-- Features: MastoAPI, Streaming Ready, Moderation, Text Formatting
+- Features: Streaming Ready, Moderation, Text Formatting
 
 ### Kyclos
 - Source Code: <https://git.pleroma.social/pleroma/harbour-kyclos>
 - Platforms: SailfishOS
-- Features: MastoAPI, No Streaming
+- Features: No Streaming
 
 ### Husky
 - Source code: <https://git.mentality.rip/FWGS/Husky>
 - Contact: [@Husky@enigmatic.observer](https://enigmatic.observer/users/Husky)
 - Platforms: Android
-- Features: MastoAPI, No Streaming, Emoji Reactions, Text Formatting, FE Stickers
+- Features: No Streaming, Emoji Reactions, Text Formatting, FE Stickers
 
 ### Fedi
 - Homepage: <https://www.fediapp.com/>
 - Source Code: Proprietary, but gratis
 - Platforms: iOS, Android
-- Features: MastoAPI, Pleroma-specific features like Reactions
+- Features: Pleroma-specific features like Reactions
 
 ### Tusky
 - Homepage: <https://tuskyapp.github.io/>
 - Source Code: <https://github.com/tuskyapp/Tusky>
 - Contact: [@ConnyDuck@mastodon.social](https://mastodon.social/users/ConnyDuck)
 - Platforms: Android
-- Features: MastoAPI, No Streaming
+- Features: No Streaming
 
 ### Twidere
 - Homepage: <https://twidere.mariotaku.org/>
 - Source Code: <https://github.com/TwidereProject/Twidere-Android/>
 - Contact: <me@mariotaku.org>
 - Platform: Android
-- Features: MastoAPI, No Streaming
+- Features: No Streaming
 
 ### Indigenous
 - Homepage: <https://indigenous.realize.be/>
 - Source Code: <https://github.com/swentel/indigenous-android/>
-- Contact: [@swentel@realize.be](https://realize.be)
+- Contact: [@realize.be@realize.be](@realize.be@realize.be)
 - Platforms: Android
-- Features: MastoAPI, No Streaming
+- Features: No Streaming
 
 ## Alternative Web Interfaces
 ### Brutaldon
 - Homepage: <https://jfm.carcosa.net/projects/software/brutaldon/>
 - Source Code: <https://git.carcosa.net/jmcbray/brutaldon>
 - Contact: [@gcupc@glitch.social](https://glitch.social/users/gcupc)
-- Features: MastoAPI, No Streaming
+- Features: No Streaming
 
 ### Halcyon
 - Source Code: <https://notabug.org/halcyon-suite/halcyon>
 - Contact: [@halcyon@social.csswg.org](https://social.csswg.org/users/halcyon)
-- Features: MastoAPI, Streaming Ready
+- Features: Streaming Ready
 
 ### Pinafore
 - Homepage: <https://pinafore.social/>
 - Source Code: <https://github.com/nolanlawson/pinafore>
 - Contact: [@pinafore@mastodon.technology](https://mastodon.technology/users/pinafore)
 - Note: Pleroma support is a secondary goal
-- Features: MastoAPI, No Streaming
+- Features: No Streaming
 
 ### Sengi
 - Homepage: <https://nicolasconstant.github.io/sengi/>
 - Source Code: <https://github.com/NicolasConstant/sengi>
 - Contact: [@sengi_app@mastodon.social](https://mastodon.social/users/sengi_app)
-- Features: MastoAPI
 
 ### DashFE
 - Source Code: <https://notabug.org/daisuke/DashboardFE>
@@ -116,10 +107,3 @@ Feel free to contact us to be added to this list!
 - Source Code: <https://git.freesoftwareextremist.com/bloat/>
 - Contact: [@r@freesoftwareextremist.com](https://freesoftwareextremist.com/users/r)
 - Features: Does not requires JavaScript
-- Features: MastoAPI
-
-### Glitch-lily
-- Source Code: <https://lily.kazv.moe/infra/glitch-lily>
-- Contact: [@tusooa@kazv.moe](https://kazv.moe/users/tusooa)
-- Features: MastoAPI
-- Based on [glitch-soc](https://github.com/glitch-soc/mastodon) frontend

docs/configuration/auth.md

@@ -1 +0,0 @@
-See `Authentication` section of [the configuration cheatsheet](../configuration/cheatsheet.md#authentication).

docs/configuration/cheatsheet.md

@@ -8,19 +8,18 @@ For from source installations Pleroma configuration works by first importing the
 
 To add configuration to your config file, you can copy it from the base config. The latest version of it can be viewed [here](https://git.pleroma.social/pleroma/pleroma/blob/develop/config/config.exs). You can also use this file if you don't know how an option is supposed to be formatted.
 
-## :shout
+## :chat
 
-* `enabled` - Enables the backend Shoutbox chat feature. Defaults to `true`.
-* `limit` - Shout character limit. Defaults to `5_000`
+* `enabled` - Enables the backend chat. Defaults to `true`.
 
 ## :instance
 * `name`: The instance’s name.
 * `email`: Email used to reach an Administrator/Moderator of the instance.
 * `notify_email`: Email used for notifications.
 * `description`: The instance’s description, can be seen in nodeinfo and ``/api/v1/instance``.
-* `short_description`: Shorter version of instance description, can be seen on ``/api/v1/instance``.
 * `limit`: Posts character limit (CW/Subject included in the counter).
-* `description_limit`: The character limit for image descriptions.
+* `discription_limit`: The character limit for image descriptions.
+* `chat_limit`: Character limit of the instance chat messages.
 * `remote_limit`: Hard character limit beyond which remote posts will be dropped.
 * `upload_limit`: File size limit of uploads (except for avatar, background, banner).
 * `avatar_upload_limit`: File size limit of user’s profile avatars.
@@ -38,21 +37,19 @@ To add configuration to your config file, you can copy it from the base config.
 * `federating`: Enable federation with other instances.
 * `federation_incoming_replies_max_depth`: Max. depth of reply-to activities fetching on incoming federation, to prevent out-of-memory situations while fetching very long threads. If set to `nil`, threads of any depth will be fetched. Lower this value if you experience out-of-memory crashes.
 * `federation_reachability_timeout_days`: Timeout (in days) of each external federation target being unreachable prior to pausing federating to it.
-* `allow_relay`: Permits remote instances to subscribe to all public posts of your instance. This may increase the visibility of your instance.
+* `allow_relay`: Enable Pleroma’s Relay, which makes it possible to follow a whole instance.
 * `public`: Makes the client API in authenticated mode-only except for user-profiles. Useful for disabling the Local Timeline and The Whole Known Network. Note that there is a dependent setting restricting or allowing unauthenticated access to specific resources, see `restrict_unauthenticated` for more details.
-* `quarantined_instances`: ActivityPub instances where private (DMs, followers-only) activities will not be send.
-* `rejected_instances`: ActivityPub instances to reject requests from if authorized_fetch_mode is enabled.
+* `quarantined_instances`: List of ActivityPub instances where private (DMs, followers-only) activities will not be send.
+* `managed_config`: Whenether the config for pleroma-fe is configured in [:frontend_configurations](#frontend_configurations) or in ``static/config.json``.
 * `allowed_post_formats`: MIME-type list of formats allowed to be posted (transformed into HTML).
 * `extended_nickname_format`: Set to `true` to use extended local nicknames format (allows underscores/dashes). This will break federation with
     older software for theses nicknames.
 * `max_pinned_statuses`: The maximum number of pinned statuses. `0` will disable the feature.
 * `autofollowed_nicknames`: Set to nicknames of (local) users that every new user should automatically follow.
-* `autofollowing_nicknames`: Set to nicknames of (local) users that automatically follows every newly registered user.
 * `attachment_links`: Set to true to enable automatically adding attachment link text to statuses.
 * `max_report_comment_size`: The maximum size of the report comment (Default: `1000`).
-* `report_strip_status`: Strip associated statuses in reports to ids when closed/resolved, otherwise keep a copy.
 * `safe_dm_mentions`: If set to true, only mentions at the beginning of a post will be used to address people in direct messages. This is to prevent accidental mentioning of people when talking about them (e.g. "@friend hey i really don't like @enemy"). Default: `false`.
-* `healthcheck`: If set to true, system data will be shown on ``/api/v1/pleroma/healthcheck``.
+* `healthcheck`: If set to true, system data will be shown on ``/api/pleroma/healthcheck``.
 * `remote_post_retention_days`: The default amount of days to retain remote posts when pruning the database.
 * `user_bio_length`: A user bio maximum length (default: `5000`).
 * `user_name_length`: A user name maximum length (default: `100`).
@@ -66,44 +63,6 @@ To add configuration to your config file, you can copy it from the base config.
 * `external_user_synchronization`: Enabling following/followers counters synchronization for external users.
 * `cleanup_attachments`: Remove attachments along with statuses. Does not affect duplicate files and attachments without status. Enabling this will increase load to database when deleting statuses on larger instances.
 * `show_reactions`: Let favourites and emoji reactions be viewed through the API (default: `true`).
-* `password_reset_token_validity`: The time after which reset tokens aren't accepted anymore, in seconds (default: one day).
-* `admin_privileges`: A list of privileges an admin has (e.g. delete messages, manage reports...)
-    * Possible values are:
-      * `:users_read`
-        * Allows admins to fetch users through the admin API.
-      * `:users_manage_invites`
-        * Allows admins to manage invites. This includes sending, resending, revoking and approving invites.
-      * `:users_manage_activation_state`
-        * Allows admins to activate and deactivate accounts. This also allows them to see deactivated users through the Mastodon API.
-      * `:users_manage_tags`
-        * Allows admins to set and remove tags for users. This can be useful in combination with MRF policies, such as `Pleroma.Web.ActivityPub.MRF.TagPolicy`.
-      * `:users_manage_credentials`
-        * Allows admins to trigger a password reset and set new credentials for an user.
-      * `:users_delete`
-        * Allows admins to delete accounts. Note that deleting an account is actually deactivating it and removing all data like posts, profile information, etc.
-      * `:messages_read`
-        * Allows admins to read messages through the admin API, including non-public posts and chats.
-      * `:messages_delete`
-        * Allows admins to delete messages from other users.
-      * `:instances_delete,`
-        * Allows admins to remove a whole remote instance from your instance. This will delete all users and messages from that remote instance.
-      * `:reports_manage_reports`
-        * Allows admins to see and manage reports.
-      * `:moderation_log_read,`
-        * Allows admins to read the entries in the moderation log.
-      * `:emoji_manage_emoji`
-        * Allows admins to manage custom emoji on the instance.
-      * `:statistics_read,`
-        * Allows admins to see some simple statistics about the instance.
-* `moderator_privileges`: A list of privileges a moderator has (e.g. delete messages, manage reports...)
-    * Possible values are the same as for `admin_privileges`
-
-## :features
-* `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).
-
-## Background migrations
-* `populate_hashtags_table/sleep_interval_ms`: Sleep interval between each chunk of processed records in order to decrease the load on the system (defaults to 0 and should be keep default on most instances).
-* `populate_hashtags_table/fault_rate_allowance`: Max rate of failed objects to actually processed objects in order to enable the feature (any value from 0.0 which tolerates no errors to 1.0 which will enable the feature even if hashtags transfer failed for all records).
 
 ## Welcome
 * `direct_message`: - welcome message sent as a direct message.
@@ -155,15 +114,7 @@ To add configuration to your config file, you can copy it from the base config.
     * `Pleroma.Web.ActivityPub.MRF.MentionPolicy`: Drops posts mentioning configurable users. (See [`:mrf_mention`](#mrf_mention)).
     * `Pleroma.Web.ActivityPub.MRF.VocabularyPolicy`: Restricts activities to a configured set of vocabulary. (See [`:mrf_vocabulary`](#mrf_vocabulary)).
     * `Pleroma.Web.ActivityPub.MRF.ObjectAgePolicy`: Rejects or delists posts based on their age when received. (See [`:mrf_object_age`](#mrf_object_age)).
-    * `Pleroma.Web.ActivityPub.MRF.ActivityExpirationPolicy`: Sets a default expiration on all posts made by users of the local instance. Requires `Pleroma.Workers.PurgeExpiredActivity` to be enabled for processing the scheduled deletions.
-    * `Pleroma.Web.ActivityPub.MRF.ForceBotUnlistedPolicy`: Makes all bot posts to disappear from public timelines.
-    * `Pleroma.Web.ActivityPub.MRF.FollowBotPolicy`: Automatically follows newly discovered users from the specified bot account. Local accounts, locked accounts, and users with "#nobot" in their bio are respected and excluded from being followed.
-    * `Pleroma.Web.ActivityPub.MRF.AntiFollowbotPolicy`: Drops follow requests from followbots. Users can still allow bots to follow them by first following the bot.
-    * `Pleroma.Web.ActivityPub.MRF.KeywordPolicy`: Rejects or removes from the federated timeline or replaces keywords. (See [`:mrf_keyword`](#mrf_keyword)).
-    * `Pleroma.Web.ActivityPub.MRF.ForceMentionsInContent`: Forces every mentioned user to be reflected in the post content.
-    * `Pleroma.Web.ActivityPub.MRF.InlineQuotePolicy`: Forces quote post URLs to be reflected in the message content inline.
-    * `Pleroma.Web.ActivityPub.MRF.QuoteToLinkTagPolicy`: Force a Link tag for posts quoting another post. (may break outgoing federation of quote posts with older Pleroma versions).
-    * `Pleroma.Web.ActivityPub.MRF.ForceMention`: Forces posts to include a mention of the author of parent post or the author of quoted post.
+    * `Pleroma.Web.ActivityPub.MRF.ActivityExpirationPolicy`: Sets a default expiration on all posts made by users of the local instance. Requires `Pleroma.ActivityExpiration` to be enabled for processing the scheduled delections.
 * `transparency`: Make the content of your Message Rewrite Facility settings public (via nodeinfo).
 * `transparency_exclusions`: Exclude specific instance names from MRF transparency.  The use of the exclusions feature will be disclosed in nodeinfo as a boolean value.
 
@@ -174,16 +125,15 @@ To add configuration to your config file, you can copy it from the base config.
     Configuring MRF policies is not enough for them to take effect. You have to enable them by specifying their module in `policies` under [:mrf](#mrf) section.
 
 #### :mrf_simple
-* `media_removal`: List of instances to strip media attachments from and the reason for doing so.
-* `media_nsfw`: List of instances to tag all media as NSFW (sensitive) from and the reason for doing so.
-* `federated_timeline_removal`: List of instances to remove from the Federated Timeline (aka The Whole Known Network) and the reason for doing so.
-* `reject`: List of instances to reject activities (except deletes) from and the reason for doing so.
-* `accept`: List of instances to only accept activities (except deletes) from and the reason for doing so.
-* `followers_only`: Force posts from the given instances to be visible by followers only and the reason for doing so.
-* `report_removal`: List of instances to reject reports from and the reason for doing so.
-* `avatar_removal`: List of instances to strip avatars from and the reason for doing so.
-* `banner_removal`: List of instances to strip banners from and the reason for doing so.
-* `reject_deletes`: List of instances to reject deletions from and the reason for doing so.
+* `media_removal`: List of instances to remove media from.
+* `media_nsfw`: List of instances to put media as NSFW(sensitive) from.
+* `federated_timeline_removal`: List of instances to remove from Federated (aka The Whole Known Network) Timeline.
+* `reject`: List of instances to reject any activities from.
+* `accept`: List of instances to accept any activities from.
+* `followers_only`: List of instances to decrease post visibility to only the followers, including for DM mentions.
+* `report_removal`: List of instances to reject reports from.
+* `avatar_removal`: List of instances to strip avatars from.
+* `banner_removal`: List of instances to strip banners from.
 
 #### :mrf_subchain
 This policy processes messages through an alternate pipeline when a given message matches certain criteria.
@@ -239,7 +189,7 @@ config :pleroma, :mrf_user_allowlist, %{
   e.g., A value of 900 results in any post with a timestamp older than 15 minutes will be acted upon.
 * `actions`: A list of actions to apply to the post:
   * `:delist` removes the post from public timelines
-  * `:strip_followers` removes followers from the ActivityPub recipient list, ensuring they won't be delivered to home timelines, additionally for followers-only it degrades to a direct message
+  * `:strip_followers` removes followers from the ActivityPub recipient list, ensuring they won't be delivered to home timelines
   * `:reject` rejects the message entirely
 
 #### :mrf_steal_emoji
@@ -251,41 +201,12 @@ config :pleroma, :mrf_user_allowlist, %{
 
 * `days`: Default global expiration time for all local Create activities (in days)
 
-#### :mrf_hashtag
-
-* `sensitive`: List of hashtags to mark activities as sensitive (default: `nsfw`)
-* `federated_timeline_removal`: List of hashtags to remove activities from the federated timeline (aka TWNK)
-* `reject`: List of hashtags to reject activities from
-
-Notes:
-- The hashtags in the configuration do not have a leading `#`.
-- This MRF Policy is always enabled, if you want to disable it you have to set empty lists
-
-#### :mrf_follow_bot
-
-* `follower_nickname`: The name of the bot account to use for following newly discovered users. Using `followbot` or similar is strongly suggested.
-
-#### :mrf_emoji
-* `remove_url`: A list of patterns which result in emoji whose URL matches being removed from the message. This will apply to statuses, emoji reactions, and user profiles. Each pattern can be a string or a [regular expression](https://hexdocs.pm/elixir/Regex.html).
-* `remove_shortcode`: A list of patterns which result in emoji whose shortcode matches being removed from the message. This will apply to statuses, emoji reactions, and user profiles. Each pattern can be a string or a [regular expression](https://hexdocs.pm/elixir/Regex.html).
-* `federated_timeline_removal_url`: A list of patterns which result in message with emojis whose URLs match being removed from federated timelines (a.k.a unlisted). This will apply only to statuses. Each pattern can be a string or a [regular expression](https://hexdocs.pm/elixir/Regex.html).
-* `federated_timeline_removal_shortcode`: A list of patterns which result in message with emojis whose shortcodes match being removed from federated timelines (a.k.a unlisted). This will apply only to statuses. Each pattern can be a string or a [regular expression](https://hexdocs.pm/elixir/Regex.html).
-
-#### :mrf_inline_quote
-* `template`: The template to append to the post. `{url}` will be replaced with the actual link to the quoted post. Default: `<bdi>RT:</bdi> {url}`
-
-#### :mrf_force_mention
-* `mention_parent`: Whether to append mention of parent post author
-* `mention_quoted`: Whether to append mention of parent quoted author
-
 ### :activitypub
 * `unfollow_blocked`: Whether blocks result in people getting unfollowed
 * `outgoing_blocks`: Whether to federate blocks to other instances
-* `blockers_visible`: Whether a user can see the posts of users who blocked them
 * `deny_follow_blocked`: Whether to disallow following an account that has blocked the user in question
 * `sign_object_fetches`: Sign object fetches with HTTP signatures
 * `authorized_fetch_mode`: Require HTTP signatures for AP fetches
-* `authorized_fetch_mode_exceptions`: List of IPs (CIDR format accepted) to exempt from HTTP Signatures requirement (for example to allow debugging, you shouldn't otherwise need this)
 
 ## Pleroma.User
 
@@ -298,11 +219,19 @@ Notes:
 * `total_user_limit`: the number of scheduled activities a user is allowed to create in total (Default: `300`)
 * `enabled`: whether scheduled activities are sent to the job queue to be executed
 
+## Pleroma.ActivityExpiration
+
+Enables the worker which processes posts scheduled for deletion. Pinned posts are exempt from expiration.
+
+* `enabled`: whether expired activities will be sent to the job queue to be deleted
+
+## Frontends
+
 ### :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` are configured. You can find the documentation for `pleroma_fe` configuration into [Pleroma-FE configuration and customization for instance administrators](/frontend/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](/frontend/CONFIGURATION/#options).
 
-Frontends can access these settings at `/api/v1/pleroma/frontend_configurations`
+Frontends can access these settings at `/api/pleroma/frontend_configurations`
 
 To add your own configuration for PleromaFE, use it like this:
 
@@ -311,7 +240,10 @@ config :pleroma, :frontend_configurations,
   pleroma_fe: %{
     theme: "pleroma-dark",
     # ... see /priv/static/static/config.json for the available keys.
-}
+},
+  masto_fe: %{
+    showInstanceSpecificPanel: true
+  }
 ```
 
 These settings **need to be complete**, they will override the defaults.
@@ -382,23 +314,14 @@ This section describe PWA manifest instance-specific values. Currently this opti
   * `enabled`: Enables purge cache
   * `provider`: Which one of  the [purge cache strategy](#purge-cache-strategy) to use.
 
-## :media_preview_proxy
-
-* `enabled`: Enables proxying of remote media preview to the instance’s proxy. Requires enabled media proxy (`media_proxy/enabled`).
-* `thumbnail_max_width`: Max width of preview thumbnail for images (video preview always has original dimensions).
-* `thumbnail_max_height`: Max height of preview thumbnail for images (video preview always has original dimensions).
-* `image_quality`: Quality of the output. Ranges from 0 (min quality) to 100 (max quality).
-* `min_content_length`: Min content length to perform preview, in bytes. If greater than 0, media smaller in size will be served as is, without thumbnailing.
-
 ### Purge cache strategy
 
 #### Pleroma.Web.MediaProxy.Invalidation.Script
 
 This strategy allow perform external shell script to purge cache.
-Urls of attachments are passed to the script as arguments.
+Urls of attachments pass to script as arguments.
 
-* `script_path`: Path to the external script.
-* `url_format`: Set to `:htcacheclean` if using Apache's htcacheclean utility.
+* `script_path`: path to external script.
 
 Example:
 
@@ -436,7 +359,7 @@ config :pleroma, Pleroma.Web.MediaProxy.Invalidation.Http,
 * `ignore_hosts`: list of hosts which will be ignored by the metadata parser. For example `["accounts.google.com", "xss.website"]`, defaults to `[]`.
 * `ignore_tld`: list TLDs (top-level domains) which will ignore for parse metadata. default is ["local", "localdomain", "lan"].
 * `parsers`: list of Rich Media parsers.
-* `timeout`: Amount of milliseconds after which the HTTP request is forcibly terminated.
+* `failure_backoff`: Amount of milliseconds after request failure, during which the request will not be retried.
 
 ## HTTP server
 
@@ -474,27 +397,26 @@ This will make Pleroma listen on `127.0.0.1` port `8080` and generate urls start
 * ``ct_max_age``: The maximum age for the `Expect-CT` header if sent.
 * ``referrer_policy``: The referrer policy to use, either `"same-origin"` or `"no-referrer"`.
 * ``report_uri``: Adds the specified url to `report-uri` and `report-to` group in CSP header.
-* `allow_unsafe_eval`: Adds `wasm-unsafe-eval` to the CSP header. Needed for some non-essential frontend features like Flash emulation.
 
-### Pleroma.Web.Plugs.RemoteIp
+### Pleroma.Plugs.RemoteIp
 
 !!! warning
     If your instance is not behind at least one reverse proxy, you should not enable this plug.
 
-`Pleroma.Web.Plugs.RemoteIp` is a shim to call [`RemoteIp`](https://git.pleroma.social/pleroma/remote_ip) but with runtime configuration.
+`Pleroma.Plugs.RemoteIp` is a shim to call [`RemoteIp`](https://git.pleroma.social/pleroma/remote_ip) but with runtime configuration.
 
 Available options:
 
 * `enabled` - Enable/disable the plug. Defaults to `false`.
-* `headers` - A list of strings naming the HTTP headers to use when deriving the true client IP address. Defaults to `["x-forwarded-for"]`.
-* `proxies` - A list of upstream proxy IP subnets in CIDR notation from which we will parse the content of `headers`. Defaults to `[]`. IPv4 entries without a bitmask will be assumed to be /32 and IPv6 /128.
-* `reserved` - A list of reserved IP subnets in CIDR notation which should be ignored if found in `headers`. Defaults to `["127.0.0.0/8", "::1/128", "fc00::/7", "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16"]`.
+* `headers` - A list of strings naming the `req_headers` to use when deriving the `remote_ip`. Order does not matter. Defaults to `["x-forwarded-for"]`.
+* `proxies` - A list of strings in [CIDR](https://en.wikipedia.org/wiki/CIDR) notation specifying the IPs of known proxies. Defaults to `[]`.
+* `reserved` - Defaults to [localhost](https://en.wikipedia.org/wiki/Localhost) and [private network](https://en.wikipedia.org/wiki/Private_network).
 
 
 ### :rate_limit
 
 !!! note
-   If your instance is behind a reverse proxy ensure [`Pleroma.Web.Plugs.RemoteIp`](#pleroma-plugs-remoteip) is enabled (it is enabled by default).
+   If your instance is behind a reverse proxy ensure [`Pleroma.Plugs.RemoteIp`](#pleroma-plugs-remoteip) is enabled (it is enabled by default).
 
 A keyword list of rate limiters where a key is a limiter name and value is the limiter configuration. The basic configuration is a tuple where:
 
@@ -514,7 +436,7 @@ config :pleroma, :rate_limit,
 Means that:
 
 1. In 60 seconds, 15 authentication attempts can be performed from the same IP address.
-2. In 1 second, 10 search requests can be performed from the same IP address by unauthenticated users, while authenticated users can perform 30 search requests per second.
+2. In 1 second, 10 search requests can be performed from the same IP adress by unauthenticated users, while authenticated users can perform 30 search requests per second.
 
 Supported rate limiters:
 
@@ -574,7 +496,7 @@ Settings for HTTP connection pool.
 * `:connection_acquisition_wait` - Timeout to acquire a connection from pool.The total max time is this value multiplied by the number of retries.
 * `connection_acquisition_retries` - Number of attempts to acquire the connection from the pool if it is overloaded. Each attempt is timed `:connection_acquisition_wait` apart.
 * `:max_connections` - Maximum number of connections in the pool.
-* `:connect_timeout` - Timeout to connect to the host.
+* `:await_up_timeout` - Timeout to connect to the host.
 * `:reclaim_multiplier` - Multiplied by `:max_connections` this will be the maximum number of idle connections that will be reclaimed in case the pool is overloaded.
 
 ### :pools
@@ -593,7 +515,7 @@ There are four pools used:
 For each pool, the options are:
 
 * `:size` - limit to how much requests can be concurrently executed.
-* `:recv_timeout` - timeout while `gun` will wait for response
+* `:timeout` - timeout while `gun` will wait for response
 * `:max_waiting` - limit to how much requests can be waiting for others to finish, after this is reached, subsequent requests will be dropped.
 
 ## Captcha
@@ -625,7 +547,7 @@ the source code is here: [kocaptcha](https://github.com/koto-bank/kocaptcha). Th
 * `uploader`: Which one of the [uploaders](#uploaders) to use.
 * `filters`: List of [upload filters](#upload-filters) to use.
 * `link_name`: When enabled Pleroma will add a `name` parameter to the url of the upload, for example `https://instance.tld/media/corndog.png?name=corndog.png`. This is needed to provide the correct filename in Content-Disposition headers when using filters like `Pleroma.Upload.Filter.Dedupe`
-* `base_url`: The base URL to access a user-uploaded file. Useful when you want to host the media files via another domain or are using a 3rd party S3 provider.
+* `base_url`: The base URL to access a user-uploaded file. Useful when you want to proxy the media files via another host.
 * `proxy_remote`: If you're using a remote uploader, Pleroma 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.
@@ -646,7 +568,10 @@ Don't forget to configure [Ex AWS S3](#ex-aws-s3-settings)
 
 * `bucket`: S3 bucket name.
 * `bucket_namespace`: S3 bucket namespace.
+* `public_endpoint`: S3 endpoint that the user finally accesses(ex. "https://s3.dualstack.ap-northeast-1.amazonaws.com")
 * `truncated_namespace`: If you use S3 compatible service such as Digital Ocean Spaces or CDN, set folder name or "" etc.
+For example, when using CDN to S3 virtual host format, set "".
+At this time, write CNAME to CDN in public_endpoint.
 * `streaming_enabled`: Enable streaming uploads, when enabled the file will be sent to the server in chunks as it's being read. This may be unsupported by some providers, try disabling this if you have upload problems.
 
 #### Ex AWS S3 settings
@@ -664,19 +589,6 @@ config :ex_aws, :s3,
   host: "s3.eu-central-1.amazonaws.com"
 ```
 
-#### Pleroma.Uploaders.IPFS
-
-* `post_gateway_url`: URL with port of POST Gateway (unauthenticated)
-* `get_gateway_url`: URL of public GET Gateway
-
-Example:
-
-```elixir
-config :pleroma, Pleroma.Uploaders.IPFS,
-  post_gateway_url: "http://localhost:5001",
-  get_gateway_url: "http://{CID}.ipfs.mydomain.com"
-```
-
 ### Upload filters
 
 #### Pleroma.Upload.Filter.AnonymizeFilename
@@ -690,24 +602,12 @@ This filter replaces the filename (not the path) of an upload. For complete obfu
 
 No specific configuration.
 
-#### Pleroma.Upload.Filter.Exiftool.StripLocation
+#### Pleroma.Upload.Filter.Exiftool
 
 This filter only strips the GPS and location metadata with Exiftool leaving color profiles and attributes intact.
 
 No specific configuration.
 
-#### Pleroma.Upload.Filter.Exiftool.ReadDescription
-
-This filter reads the ImageDescription and iptc:Caption-Abstract fields with Exiftool so clients can prefill the media description field.
-
-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"}]`.
@@ -742,21 +642,6 @@ config :pleroma, Pleroma.Emails.Mailer,
   auth: :always
 ```
 
-An example for Mua adapter:
-
-```elixir
-config :pleroma, Pleroma.Emails.Mailer,
-  enabled: true,
-  adapter: Swoosh.Adapters.Mua,
-  relay: "mail.example.com",
-  port: 465,
-  auth: [
-    username: "YOUR_USERNAME@domain.tld",
-    password: "YOUR_SMTP_PASSWORD"
-  ],
-  protocol: :ssl
-```
-
 ### :email_notifications
 
 Email notifications settings.
@@ -805,8 +690,9 @@ Pleroma has the following queues:
 
 Pleroma has these periodic job workers:
 
-* `Pleroma.Workers.Cron.DigestEmailsWorker` - digest emails for users with new mentions and follows
-* `Pleroma.Workers.Cron.NewUsersDigestWorker` - digest emails for admins with new registrations
+`Pleroma.Workers.Cron.ClearOauthTokenWorker` - a job worker to cleanup expired oauth tokens.
+
+Example:
 
 ```elixir
 config :pleroma, Oban,
@@ -818,8 +704,7 @@ config :pleroma, Oban,
     federator_outgoing: 50
   ],
   crontab: [
-    {"0 0 * * 0", Pleroma.Workers.Cron.DigestEmailsWorker},
-    {"0 0 * * *", Pleroma.Workers.Cron.NewUsersDigestWorker}
+    {"0 0 * * *", Pleroma.Workers.Cron.ClearOauthTokenWorker}
   ]
 ```
 
@@ -860,7 +745,7 @@ Web Push Notifications configuration. You can use the mix task `mix web_push.gen
 * ``private_key``: VAPID private key
 
 ## :logger
-* `backends`: `:console` is used to send logs to stdout, `{ExSyslogger, :ex_syslogger}` to log to syslog
+* `backends`: `:console` is used to send logs to stdout, `{ExSyslogger, :ex_syslogger}` to log to syslog, and `Quack.Logger` to log to Slack
 
 An example to enable ONLY ExSyslogger (f/ex in ``prod.secret.exs``) with info and debug suppressed:
 ```elixir
@@ -868,7 +753,7 @@ config :logger,
   backends: [{ExSyslogger, :ex_syslogger}]
 
 config :logger, :ex_syslogger,
-  level: :warning
+  level: :warn
 ```
 
 Another example, keeping console output and adding the pid to syslog output:
@@ -877,16 +762,16 @@ config :logger,
   backends: [:console, {ExSyslogger, :ex_syslogger}]
 
 config :logger, :ex_syslogger,
-  level: :warning,
+  level: :warn,
   option: [:pid, :ndelay]
 ```
 
 See: [logger’s documentation](https://hexdocs.pm/logger/Logger.html) and [ex_syslogger’s documentation](https://hexdocs.pm/ex_syslogger/)
 
-An example of logging info to local syslog, but debug to console:
+An example of logging info to local syslog, but warn to a Slack channel:
 ```elixir
 config :logger,
-  backends: [ {ExSyslogger, :ex_syslogger}, :console ],
+  backends: [ {ExSyslogger, :ex_syslogger}, Quack.Logger ],
   level: :info
 
 config :logger, :ex_syslogger,
@@ -894,12 +779,14 @@ config :logger, :ex_syslogger,
   ident: "pleroma",
   format: "$metadata[$level] $message"
 
-config :logger, :console,
-  level: :debug,
-  format: "\n$time $metadata[$level] $message\n",
-  metadata: [:request_id]
+config :quack,
+  level: :warn,
+  meta: [:all],
+  webhook_url: "https://hooks.slack.com/services/YOUR-API-KEY-HERE"
 ```
 
+See the [Quack Github](https://github.com/azohra/quack) for more details
+
 
 
 ## Database options
@@ -925,8 +812,21 @@ This will probably take a long time.
 
 ### BBS / SSH access
 
-This feature has been removed from Pleroma core.
-However, a client has been made and is available at https://git.pleroma.social/Duponin/sshocial.
+To enable simple command line interface accessible over ssh, add a setting like this to your configuration file:
+
+```exs
+app_dir = File.cwd!
+priv_dir = Path.join([app_dir, "priv/ssh_keys"])
+
+config :esshd,
+  enabled: true,
+  priv_dir: priv_dir,
+  handler: "Pleroma.BBS.Handler",
+  port: 10_022,
+  password_authenticator: "Pleroma.BBS.Authenticator"
+```
+
+Feel free to adjust the priv_dir and port number. Then you will have to create the key for the keys (in the example `priv/ssh_keys`) and create the host keys with `ssh-keygen -m PEM -N "" -b 2048 -t rsa -f ssh_host_rsa_key`. After restarting, you should be able to connect to your Pleroma instance with `ssh username@server -p $PORT`
 
 ### :gopher
 * `enabled`: Enables the gopher interface
@@ -948,13 +848,13 @@ config :pleroma, :admin_token, "somerandomtoken"
 You can then do
 
 ```shell
-curl "http://localhost:4000/api/v1/pleroma/admin/users/invites?admin_token=somerandomtoken"
+curl "http://localhost:4000/api/pleroma/admin/users/invites?admin_token=somerandomtoken"
 ```
 
 or
 
 ```shell
-curl -H "X-Admin-Token: somerandomtoken" "http://localhost:4000/api/v1/pleroma/admin/users/invites"
+curl -H "X-Admin-Token: somerandomtoken" "http://localhost:4000/api/pleroma/admin/users/invites"
 ```
 
 Warning: it's discouraged to use this feature because of the associated security risk: static / rarely changed instance-wide token is much weaker compared to email-password pair of a real admin user; consider using HTTP Basic Auth or OAuth-based authentication instead.
@@ -983,33 +883,16 @@ Pleroma account will be created with the same name as the LDAP user name.
 * `enabled`: enables LDAP authentication
 * `host`: LDAP server hostname
 * `port`: LDAP port, e.g. 389 or 636
-* `ssl`: true to use implicit SSL/TLS, usually port 636
+* `ssl`: true to use SSL, usually implies the port 636
 * `sslopts`: additional SSL options
-* `tls`: true to use explicit TLS (STARTTLS), usually port 389
+* `tls`: true to start TLS, usually implies the port 389
 * `tlsopts`: additional TLS options
 * `base`: LDAP base, e.g. "dc=example,dc=com"
 * `uid`: LDAP attribute name to authenticate the user, e.g. when "cn", the filter will be "cn=username,base"
-* `cacertfile`: Path to alternate CA root certificates file
 
 Note, if your LDAP server is an Active Directory server the correct value is commonly `uid: "cn"`, but if you use an
 OpenLDAP server the value may be `uid: "uid"`.
 
-### :oauth2 (Pleroma as OAuth 2.0 provider settings)
-
-OAuth 2.0 provider settings:
-
-* `token_expires_in` - The lifetime in seconds of the access token.
-* `issue_new_refresh_token` - Keeps old refresh token or generate new refresh token when to obtain an access token.
-* `clean_expired_tokens` - Enable a background job to clean expired oauth tokens. Defaults to `false`.
-
-OAuth 2.0 provider and related endpoints:
-
-* `POST /api/v1/apps` creates client app basing on provided params.
-* `GET/POST /oauth/authorize` renders/submits authorization form.
-* `POST /oauth/token` creates/renews OAuth token.
-* `POST /oauth/revoke` revokes provided OAuth token.
-* `GET /api/v1/accounts/verify_credentials` (with proper `Authorization` header or `access_token` URI param) returns user info on requester (with `acct` field containing local nickname and `fqn` field containing fully-qualified nickname which could generally be used as email stub for OAuth software that demands email field in identity endpoint response, like Peertube).
-
 ### OAuth consumer mode
 
 OAuth consumer mode allows sign in / sign up via external OAuth providers (e.g. Twitter, Facebook, Google, Microsoft, etc.).
@@ -1082,6 +965,14 @@ config :ueberauth, Ueberauth,
   ]
 ```
 
+### OAuth 2.0 provider - :oauth2
+
+Configure OAuth 2 provider capabilities:
+
+* `token_expires_in` - The lifetime in seconds of the access token.
+* `issue_new_refresh_token` - Keeps old refresh token or generate new refresh token when to obtain an access token.
+* `clean_expired_tokens` - Enable a background job to clean expired oauth tokens. Defaults to `false`. Interval settings sets in configuration periodic jobs [`Oban.Cron`](#obancron)
+
 ## Link parsing
 
 ### :uri_schemes
@@ -1118,7 +1009,7 @@ config :pleroma, Pleroma.Formatter,
 
 ## :configurable_from_database
 
-Boolean, enables/disables in-database configuration. Read [Transferring the config to/from the database](../administration/CLI_tasks/config.md) for more information.
+Boolean, enables/disables in-database configuration. Read [Transfering the config to/from the database](../administration/CLI_tasks/config.md) for more information.
 
 ## :database_config_whitelist
 
@@ -1174,21 +1065,6 @@ Control favicons for instances.
 
 * `enabled`: Allow/disallow displaying and getting instances favicons
 
-## Pleroma.User.Backup
-
-!!! note
-    Requires enabled email
-
-* `:purge_after_days` an integer, remove backup achieves after N days.
-* `:limit_days` an integer, limit user to export not more often than once per N days.
-* `:dir` a string with a path to backup temporary directory or `nil` to let Pleroma choose temporary directory in the following order:
-    1. the directory named by the TMPDIR environment variable
-    2. the directory named by the TEMP environment variable
-    3. the directory named by the TMP environment variable
-    4. C:\TMP on Windows or /tmp on Unix-like operating systems
-    5. as a last resort, the current working directory
-* `:timeout` an integer representing seconds
-
 ## Frontend management
 
 Frontends in Pleroma are swappable - you can specify which one to use here.
@@ -1214,22 +1090,3 @@ config :pleroma, :frontends,
 ```
 
 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.
-
-## Ephemeral activities (Pleroma.Workers.PurgeExpiredActivity)
-
-Settings to enable and configure expiration for ephemeral activities
-
-* `:enabled` - enables ephemeral activities creation
-* `:min_lifetime` - minimum lifetime for ephemeral activities (in seconds). Default: 10 minutes.
-
-## ConcurrentLimiter
-
-Settings to restrict concurrently running jobs. Jobs which can be configured:
-
-* `Pleroma.Web.RichMedia.Helpers` - generating link previews of URLs in activities
-* `Pleroma.Web.ActivityPub.MRF.MediaProxyWarmingPolicy` - warming remote media cache via MediaProxyWarmingPolicy
-
-Each job has these settings:
-
-* `:max_running` - max concurrently runnings jobs
-* `:max_waiting` - max waiting jobs

docs/configuration/custom_emoji.md

@@ -29,7 +29,7 @@ foo, /emoji/custom/foo.png
 
 The files should be PNG (APNG is okay with `.png` for `image/png` Content-type) and under 50kb for compatibility with mastodon.
 
-Default file extensions and locations for emojis are set in `config.exs`. To use different locations or file-extensions, add the `shortcode_globs` to your secrets file (`prod.secret.exs` or `dev.secret.exs`) and edit it. Note that not all fediverse-software will show emojis with other file extensions:
+Default file extentions and locations for emojis are set in `config.exs`. To use different locations or file-extentions, add the `shortcode_globs` to your secrets file (`prod.secret.exs` or `dev.secret.exs`) and edit it. Note that not all fediverse-software will show emojis with other file extentions:
 ```elixir
 config :pleroma, :emoji, shortcode_globs: ["/emoji/custom/**/*.png", "/emoji/custom/**/*.gif"]
 ```

docs/configuration/hardening.md

@@ -62,20 +62,6 @@ An additional “Expect-CT” header will be sent with the configured `ct_max_ag
 
 If you click on a link, your browser’s request to the other site will include from where it is coming from. The “Referrer policy” header tells the browser how and if it should send this information. (see [Referrer policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy))
 
-### Uploaded media and media proxy
-
-It is STRONGLY RECOMMENDED to serve both the locally-uploaded media and the media proxy from another domain than the domain that Pleroma runs on, if applicable.
-
-```elixir
-config :pleroma, :media_proxy,
-  base_url: "https://some.other.domain"
-
-config :pleroma, Pleroma.Upload,
-  base_url: "https://some.other.domain/media"
-```
-
-See `installation/pleroma-mediaproxy.nginx` for examples on how to configure your media proxy.
-
 ## systemd
 
 A systemd unit example is provided at `installation/pleroma.service`.

docs/configuration/how_to_serve_another_domain_for_webfinger.md

@@ -1,62 +0,0 @@
-# How to use a different domain name for Pleroma and the users it serves
-
-Pleroma users are primarily identified by a `user@example.org` handle, and you might want this identifier to be the same as your email or jabber account, for instance.
-However, in this case, you are almost certainly serving some web content on `https://example.org` already, and you might want to use another domain (say `pleroma.example.org`) for Pleroma itself.
-
-Pleroma supports that, but it might be tricky to set up, and any error might prevent you from federating with other instances.
-
-*If you are already running Pleroma on `example.org`, it is no longer possible to move it to `pleroma.example.org`.*
-
-## Account identifiers
-
-It is important to understand that for federation purposes, a user in Pleroma has two unique identifiers associated:
-
-- A webfinger `acct:` URI, used for discovery and as a verifiable global name for the user across Pleroma instances. In our example, our account's acct: URI is `acct:user@example.org`
-- An author/actor URI, used in every other aspect of federation. This is the way in which users are identified in ActivityPub, the underlying protocol used for federation with other Pleroma instances.
-In our case, it is `https://pleroma.example.org/users/user`.
-
-Both account identifiers are unique and required for Pleroma. An important risk if you set up your Pleroma instance incorrectly is to create two users (with different acct: URIs) with conflicting author/actor URIs.
-
-## WebFinger
-
-As said earlier, each Pleroma user has an `acct`: URI, which is used for discovery and authentication. When you add @user@example.org, a webfinger query is performed. This is done in two steps:
-
-1. Querying `https://example.org/.well-known/host-meta` (where the domain of the URL matches the domain part of the `acct`: URI) to get information on how to perform the query.
-This file will indeed contain a URL template of the form `https://example.org/.well-known/webfinger?resource={uri}` that will be used in the second step.
-2. Fill the returned template with the `acct`: URI to be queried and perform the query: `https://example.org/.well-known/webfinger?resource=acct:user@example.org`
-
-## Configuring your Pleroma instance
-
-**_DO NOT ATTEMPT TO CONFIGURE YOUR INSTANCE THIS WAY IF YOU DID NOT UNDERSTAND THE ABOVE_**
-
-### Configuring Pleroma
-
-Pleroma has a two configuration settings to enable using different domains for your users and Pleroma itself. `host` in `Pleroma.Web.Endpoint` and `domain` in `Pleroma.Web.WebFinger`. When the latter is not set, it defaults to the value of `host`.
-
-*Be extra careful when configuring your Pleroma instance, as changing `host` may cause remote instances to register different accounts with the same author/actor URI, which will result in federation issues!*
-
-```elixir
-config :pleroma, Pleroma.Web.Endpoint,
-  url: [host: "pleroma.example.org"]
-
-config :pleroma, Pleroma.Web.WebFinger, domain: "example.org"
-```
-
-- `domain` - is the domain for which your Pleroma instance has authority, it's the domain used in `acct:` URI. In our example, `domain` would be set to `example.org`. This is used in WebFinger account ids, which are the canonical account identifier in some other fediverse software like Mastodon. **If you change `domain`, the accounts on your server will be shown as different accounts in those software**.
-- `host` - is the domain used for any URL generated for your instance, including the author/actor URL's. In our case, that would be `pleroma.example.org`. This is used in AP ids, which are the canonical account identifier in Pleroma and some other fediverse software. **You should not change this after you have set up the instance**.
-
-### Configuring WebFinger domain
-
-Now, you have Pleroma running at `https://pleroma.example.org` as well as a website at `https://example.org`. If you recall how webfinger queries work, the first step is to query `https://example.org/.well-known/host-meta`, which will contain an URL template.
-
-Therefore, the easiest way to configure `example.org` is to redirect `/.well-known/host-meta` to `pleroma.example.org`.
-
-With nginx, it would be as simple as adding:
-
-```nginx
-location = /.well-known/host-meta {
-       return 301 https://pleroma.example.org$request_uri;
-}
-```
-
-in example.org's server block.

docs/configuration/howto_database_config.md

@@ -5,37 +5,50 @@ The configuration of Pleroma has traditionally been managed with a config file,
 
 ## Migration to database config
 
-1. Run the mix task to migrate to the database.
+1. Run the mix task to migrate to the database. You'll receive some debugging output and a few messages informing you of what happened.
 
   **Source:**
-
+  
   ```
   $ mix pleroma.config migrate_to_db
   ```
-
+  
   or
-
+  
   **OTP:**
-
+  
   *Note: OTP users need Pleroma to be running for `pleroma_ctl` commands to work*
-
+  
   ```
   $ ./bin/pleroma_ctl config migrate_to_db
   ```
 
   ```
+   10:04:34.155 [debug] QUERY OK source="config" db=1.6ms decode=2.0ms queue=33.5ms idle=0.0ms
+    SELECT c0."id", c0."key", c0."group", c0."value", c0."inserted_at", c0."updated_at" FROM "config" AS c0 []
     Migrating settings from file: /home/pleroma/config/dev.secret.exs
-
+    
+   10:04:34.240 [debug] QUERY OK db=4.5ms queue=0.3ms idle=92.2ms
+    TRUNCATE config; []
+  
+   10:04:34.244 [debug] QUERY OK db=2.8ms queue=0.3ms idle=97.2ms
+    ALTER SEQUENCE config_id_seq RESTART; []
+    
+   10:04:34.256 [debug] QUERY OK source="config" db=0.8ms queue=1.4ms idle=109.8ms
+   SELECT c0."id", c0."key", c0."group", c0."value", c0."inserted_at", c0."updated_at" FROM "config" AS c0 WHERE ((c0."group" = $1) AND (c0."key" = $2)) [":pleroma", ":instance"]
+    
+   10:04:34.292 [debug] QUERY OK db=2.6ms queue=1.7ms idle=137.7ms
+   INSERT INTO "config" ("group","key","value","inserted_at","updated_at") VALUES ($1,$2,$3,$4,$5) RETURNING "id" [":pleroma", ":instance", <<131, 108, 0, 0, 0, 1, 104, 2, 100, 0, 4, 110, 97, 109, 101, 109, 0, 0, 0, 7, 66, 108, 101, 114, 111, 109, 97, 106>>, ~N[2020-07-12 15:04:34], ~N[2020-07-12 15:04:34]]
    Settings for key instance migrated.
    Settings for group :pleroma migrated.
   ```
-
+  
 2. It is recommended to backup your config file now.
 
   ```
   cp config/dev.secret.exs config/dev.secret.exs.orig
   ```
-
+  
 3. Edit your Pleroma config to enable database configuration:
 
   ```
@@ -59,21 +72,21 @@ The configuration of Pleroma has traditionally been managed with a config file,
   Here is an example of a server config stripped down after migration:
 
   ```
-  import Config
+  use Mix.Config
 
   config :pleroma, Pleroma.Web.Endpoint,
     url: [host: "cool.pleroma.site", scheme: "https", port: 443]
-
+  
   config :pleroma, Pleroma.Repo,
     adapter: Ecto.Adapters.Postgres,
     username: "pleroma",
     password: "MySecretPassword",
     database: "pleroma_prod",
     hostname: "localhost"
-
+  
   config :pleroma, configurable_from_database: true
   ```
-
+ 
 5. Restart your instance and you can now access the Settings tab in AdminFE.
 
 
@@ -82,15 +95,15 @@ The configuration of Pleroma has traditionally been managed with a config file,
 1. Run the mix task to migrate back from the database. You'll receive some debugging output and a few messages informing you of what happened.
 
   **Source:**
-
+  
   ```
   $ mix pleroma.config migrate_from_db
   ```
-
+  
   or
-
+  
   **OTP:**
-
+  
   ```
   $ ./bin/pleroma_ctl config migrate_from_db
   ```
@@ -98,7 +111,7 @@ The configuration of Pleroma has traditionally been managed with a config file,
   ```
   10:26:30.593 [debug] QUERY OK source="config" db=9.8ms decode=1.2ms queue=26.0ms idle=0.0ms
   SELECT c0."id", c0."key", c0."group", c0."value", c0."inserted_at", c0."updated_at" FROM "config" AS c0 []
-
+  
   10:26:30.659 [debug] QUERY OK source="config" db=1.1ms idle=80.7ms
   SELECT c0."id", c0."key", c0."group", c0."value", c0."inserted_at", c0."updated_at" FROM "config" AS c0 []
   Database configuration settings have been saved to config/dev.exported_from_db.secret.exs
@@ -111,45 +124,30 @@ The configuration of Pleroma has traditionally been managed with a config file,
 ## Debugging
 
 ### Clearing database config
-You can clear the database config with the following command:
+You can clear the database config by truncating the `config` table in the database. e.g.,
 
-  **Source:**
-
-  ```
-  $ mix pleroma.config reset
-  ```
-
-  or
-
-  **OTP:**
-
-  ```
-  $ ./bin/pleroma_ctl config reset
-  ```
+```
+psql -d pleroma_dev
+pleroma_dev=# TRUNCATE config;
+TRUNCATE TABLE
+```
 
 Additionally, every time you migrate the configuration to the database the config table is automatically truncated to ensure a clean migration.
 
 ### Manually removing a setting
 If you encounter a situation where the server cannot run properly because of an invalid setting in the database and this is preventing you from accessing AdminFE, you can manually remove the offending setting if you know which one it is.
 
-e.g., here is an example showing a the removal of the `config :pleroma, :instance` settings:
+e.g., here is an example showing a minimal configuration in the database. Only the `config :pleroma, :instance` settings are in the table:
 
-  **Source:**
-
-  ```
-  $ mix pleroma.config delete pleroma instance
-  Are you sure you want to continue? [n]  y
-  config :pleroma, :instance deleted from the ConfigDB.
-  ```
-
-  or
-
-  **OTP:**
-
-  ```
-  $ ./bin/pleroma_ctl config delete pleroma instance
-  Are you sure you want to continue? [n]  y
-  config :pleroma, :instance deleted from the ConfigDB.
-  ```
+```
+psql -d pleroma_dev
+pleroma_dev=# select * from config;
+ id |    key    |                           value                            |     inserted_at     |     updated_at      |  group
+----+-----------+------------------------------------------------------------+---------------------+---------------------+----------
+  1 | :instance | \x836c0000000168026400046e616d656d00000007426c65726f6d616a | 2020-07-12 15:33:29 | 2020-07-12 15:33:29 | :pleroma
+(1 row)
+pleroma_dev=# delete from config where key = ':instance' and group = ':pleroma';
+DELETE 1
+```
 
 Now the `config :pleroma, :instance` settings have been removed from the database.

docs/configuration/howto_ejabberd.md

@@ -1,136 +0,0 @@
-# Configuring Ejabberd (XMPP Server) to use Pleroma for authentication
-
-If you want to give your Pleroma users an XMPP (chat) account, you can configure [Ejabberd](https://github.com/processone/ejabberd) to use your Pleroma server for user authentication, automatically giving every local user an XMPP account.
-
-In general, you just have to follow the configuration described at [https://docs.ejabberd.im/admin/configuration/authentication/#external-script](https://docs.ejabberd.im/admin/configuration/authentication/#external-script). Please read this section carefully. 
-
-Copy the script below to suitable path on your system and set owner and permissions. Also do not forget adjusting `PLEROMA_HOST` and `PLEROMA_PORT`, if necessary.
-
-```bash
-cp pleroma_ejabberd_auth.py /etc/ejabberd/pleroma_ejabberd_auth.py
-chown ejabberd /etc/ejabberd/pleroma_ejabberd_auth.py
-chmod 700 /etc/ejabberd/pleroma_ejabberd_auth.py
-```
-
-Set external auth params in ejabberd.yaml file:
-
-```bash
-auth_method: [external]
-extauth_program: "python3 /etc/ejabberd/pleroma_ejabberd_auth.py"
-extauth_instances: 3
-auth_use_cache: false
-```
-
-Restart / reload your ejabberd service.
-
-After restarting your Ejabberd server, your users should now be able to connect with their Pleroma credentials.
-
-
-```python
-import sys
-import struct
-import http.client
-from base64 import b64encode
-import logging
-
-
-PLEROMA_HOST = "127.0.0.1"
-PLEROMA_PORT = "4000"
-AUTH_ENDPOINT = "/api/v1/accounts/verify_credentials"
-USER_ENDPOINT = "/api/v1/accounts"
-LOGFILE = "/var/log/ejabberd/pleroma_auth.log"
-
-logging.basicConfig(filename=LOGFILE, level=logging.INFO)
-
-
-# Pleroma functions
-def create_connection():
-    return http.client.HTTPConnection(PLEROMA_HOST, PLEROMA_PORT)
-
-
-def verify_credentials(user: str, password: str) -> bool:
-    user_pass_b64 = b64encode("{}:{}".format(
-        user, password).encode('utf-8')).decode("ascii")
-    params = {}
-    headers = {
-        "Authorization": "Basic {}".format(user_pass_b64)
-    }
-
-    try:
-        conn = create_connection()
-        conn.request("GET", AUTH_ENDPOINT, params, headers)
-
-        response = conn.getresponse()
-        if response.status == 200:
-            return True
-
-        return False
-    except Exception as e:
-        logging.info("Can not connect: %s", str(e))
-        return False
-
-
-def does_user_exist(user: str) -> bool:
-    conn = create_connection()
-    conn.request("GET", "{}/{}".format(USER_ENDPOINT, user))
-
-    response = conn.getresponse()
-    if response.status == 200:
-        return True
-
-    return False
-
-
-def auth(username: str, server: str, password: str) -> bool:
-    return verify_credentials(username, password)
-
-
-def isuser(username, server):
-    return does_user_exist(username)
-
-
-def read():
-    (pkt_size,) = struct.unpack('>H', bytes(sys.stdin.read(2), encoding='utf8'))
-    pkt = sys.stdin.read(pkt_size)
-    cmd = pkt.split(':')[0]
-    if cmd == 'auth':
-        username, server, password = pkt.split(':', 3)[1:]
-        write(auth(username, server, password))
-    elif cmd == 'isuser':
-        username, server = pkt.split(':', 2)[1:]
-        write(isuser(username, server))
-    elif cmd == 'setpass':
-        # u, s, p = pkt.split(':', 3)[1:]
-        write(False)
-    elif cmd == 'tryregister':
-        # u, s, p = pkt.split(':', 3)[1:]
-        write(False)
-    elif cmd == 'removeuser':
-        # u, s = pkt.split(':', 2)[1:]
-        write(False)
-    elif cmd == 'removeuser3':
-        # u, s, p = pkt.split(':', 3)[1:]
-        write(False)
-    else:
-        write(False)
-
-
-def write(result):
-    if result:
-        sys.stdout.write('\x00\x02\x00\x01')
-    else:
-        sys.stdout.write('\x00\x02\x00\x00')
-    sys.stdout.flush()
-
-
-if __name__ == "__main__":
-    logging.info("Starting pleroma ejabberd auth daemon...")
-    while True:
-        try:
-            read()
-        except Exception as e:
-            logging.info(
-                "Error while processing data from ejabberd %s", str(e))
-            pass
-
-```

docs/configuration/howto_search_cjk.md

@@ -1,42 +0,0 @@
-# How to enable text search for Chinese, Japanese and Korean
-
-Pleroma's full text search feature is powered by PostgreSQL's native [text search](https://www.postgresql.org/docs/current/textsearch.html), it works well out of box for most of languages, but needs extra configurations for some asian languages like Chinese, Japanese and Korean (CJK).
-
-
-## Setup and test the new search config
-
-In most cases, you would need an extension installed to support parsing CJK text. Here are a few extensions you may choose from, or you are more than welcome to share additional ones you found working for you with the rest of Pleroma community.
-
- * [a generic n-gram parser](https://github.com/huangjimmy/pg_cjk_parser) supports Simplifed/Traditional Chinese, Japanese, and Korean
- * [a Korean parser](https://github.com/i0seph/textsearch_ko) based on mecab
- * [a Japanese parser](https://www.amris.co.jp/tsja/index.html) based on mecab
- * [zhparser](https://github.com/amutu/zhparser/) is a PostgreSQL extension base on the Simple Chinese Word Segmentation(SCWS)
- * [another Chinese parser](https://github.com/jaiminpan/pg_jieba) based on Jieba Chinese Word Segmentation
- 
-Once you have the new search config , make sure you test it with the `pleroma` user in PostgreSQL (change `YOUR.CONFIG` to your real configuration name)
-```
-SELECT ts_debug('YOUR.CONFIG', '安装和配置Nginx, ElixirとErlangをインストールします');
-```
-Check output of the query, and see if it matches your expectation.
-
-
-## Update text search config and index in database
-
-=== "OTP"
-
-    ```sh
-    ./bin/pleroma_ctl database set_text_search_config YOUR.CONFIG
-    ```
-
-=== "From Source"
-
-    ```sh
-    mix pleroma.database set_text_search_config YOUR.CONFIG
-    ```
-
-Note: index update may take a while, and it can be done while the instance is up and running, so you may restart db connection as soon as you see `Recreate index` in task output.
-
-## Restart database connection
-Since some changes above will only apply with a new database connection, you will have to restart either Pleroma or PostgreSQL process, or use `pg_terminate_backend` SQL command without restarting either. 
-
-Now the search results of statuses should be much more friendly for your language of choice, the results for searching users and tags were not changed, as the default parsing/matching should work for most cases. 

docs/configuration/i2p.md

@@ -1,4 +1,4 @@
-# I2P Federation and Accessibility
+# I2P Federation and Accessability
 
 This guide is going to focus on the Pleroma federation aspect. The actual installation is neatly explained in the official documentation, and more likely to remain up-to-date.
 It might be added to this guide if there will be a need for that.

docs/configuration/mrf.md

@@ -55,18 +55,18 @@ Servers should be configured as lists.
 
 ### Example
 
-This example will enable `SimplePolicy`, block media from `illegalporn.biz`, mark media as NSFW from `porn.biz` and `porn.business`, reject messages from `spam.com`, remove messages from `spam.university` from the federated timeline and block reports (flags) from `whiny.whiner`. We also give a reason why the moderation was done:
+This example will enable `SimplePolicy`, block media from `illegalporn.biz`, mark media as NSFW from `porn.biz` and `porn.business`, reject messages from `spam.com`, remove messages from `spam.university` from the federated timeline and block reports (flags) from `whiny.whiner`:
 
 ```elixir
 config :pleroma, :mrf,
   policies: [Pleroma.Web.ActivityPub.MRF.SimplePolicy]
 
 config :pleroma, :mrf_simple,
-  media_removal: [{"illegalporn.biz", "Media can contain illegal contant"}],
-  media_nsfw: [{"porn.biz", "unmarked nsfw media"}, {"porn.business", "A lot of unmarked nsfw media"}],
-  reject: [{"spam.com", "They keep spamming our users"}],
-  federated_timeline_removal: [{"spam.university", "Annoying low-quality posts who otherwise fill up TWKN"}],
-  report_removal: [{"whiny.whiner", "Keep spamming us with irrelevant reports"}]
+  media_removal: ["illegalporn.biz"],
+  media_nsfw: ["porn.biz", "porn.business"],
+  reject: ["spam.com"],
+  federated_timeline_removal: ["spam.university"],
+  report_removal: ["whiny.whiner"]
 ```
 
 ### Use with Care
@@ -82,7 +82,7 @@ For example, here is a sample policy module which rewrites all messages to "new
 ```elixir
 defmodule Pleroma.Web.ActivityPub.MRF.RewritePolicy do
   @moduledoc "MRF policy which rewrites all Notes to have 'new message content'."
-  @behaviour Pleroma.Web.ActivityPub.MRF.Policy
+  @behaviour Pleroma.Web.ActivityPub.MRF
 
   # Catch messages which contain Note objects with actual data to filter.
   # Capture the object as `object`, the message content as `content` and the
@@ -133,26 +133,3 @@ config :pleroma, :mrf,
 ```
 
 Please note that the Pleroma developers consider custom MRF policy modules to fall under the purview of the AGPL. As such, you are obligated to release the sources to your custom MRF policy modules upon request.
-
-### MRF policies descriptions
-
-If MRF policy depends on config, it can be added into MRF tab to adminFE by adding `config_description/0` method, which returns a map with a specific structure. See existing MRF's like `lib/pleroma/web/activity_pub/mrf/activity_expiration_policy.ex` for examples. Note that more complex inputs, like tuples or maps, may need extra changes in the adminFE and just adding it to `config_description/0` may not be enough to get these inputs working from the adminFE.
-
-Example:
-
-```elixir
-%{
-      key: :mrf_activity_expiration,
-      related_policy: "Pleroma.Web.ActivityPub.MRF.ActivityExpirationPolicy",
-      label: "MRF Activity Expiration Policy",
-      description: "Adds automatic expiration to all local activities",
-      children: [
-        %{
-          key: :days,
-          type: :integer,
-          description: "Default global expiration time for all local activities (in days)",
-          suggestions: [90, 365]
-        }
-      ]
-    }
-```

docs/configuration/onion_federation.md

@@ -29,7 +29,7 @@ HiddenServiceDir /var/lib/tor/pleroma_hidden_service/
 HiddenServicePort 80 127.0.0.1:8099
 HiddenServiceVersion 3  # Remove if Tor version is below 0.3 ( tor --version )
 ```
-Restart Tor to generate an address:
+Restart Tor to generate an adress:
 ```
 systemctl restart tor@default.service
 ```

docs/configuration/optimizing_beam.md

@@ -1,66 +0,0 @@
-# Optimizing the BEAM
-
-Pleroma is built upon the Erlang/OTP VM known as BEAM. The BEAM VM is highly optimized for latency, but this has drawbacks in environments without dedicated hardware. One of the tricks used by the BEAM VM is [busy waiting](https://en.wikipedia.org/wiki/Busy_waiting). This allows the application to pretend to be busy working so the OS kernel does not pause the application process and switch to another process waiting for the CPU to execute its workload. It does this by spinning for a period of time which inflates the apparent CPU usage of the application so it is immediately ready to execute another task. This can be observed with utilities like **top(1)** which will show consistently high CPU usage for the process. Switching between processes is a rather expensive operation and also clears CPU caches further affecting latency and performance. The goal of busy waiting is to avoid this penalty.
-
-This strategy is very successful in making a performant and responsive application, but is not desirable on Virtual Machines or hardware with few CPU cores. Pleroma instances are often deployed on the same server as the required PostgreSQL database which can lead to situations where the Pleroma application is holding the CPU in a busy-wait loop and as a result the database cannot process requests in a timely manner. The fewer CPUs available, the more this problem is exacerbated. The latency is further amplified by the OS being installed on a Virtual Machine as the Hypervisor uses CPU time-slicing to pause the entire OS and switch between other tasks.
-
-More adventurous admins can be creative with CPU affinity (e.g., *taskset* for Linux and *cpuset* on FreeBSD) to pin processes to specific CPUs and eliminate much of this contention. The most important advice is to run as few processes as possible on your server to achieve the best performance. Even idle background processes can occasionally create [software interrupts](https://en.wikipedia.org/wiki/Interrupt) and take attention away from the executing process creating latency spikes and invalidation of the CPU caches as they must be cleared when switching between processes for security.
-
-Please only change these settings if you are experiencing issues or really know what you are doing. In general, there's no need to change these settings.
-
-## VPS Provider Recommendations
-
-### Good
-
-* Hetzner Cloud
-
-### Bad
-
-* AWS (known to use burst scheduling)
-
-
-## Example configurations
-
-Tuning the BEAM requires you provide a config file normally called [vm.args](http://erlang.org/doc/man/erl.html#emulator-flags). If you are using systemd to manage the service you can modify the unit file as such:
-
-`ExecStart=/usr/bin/elixir --erl '-args_file /opt/pleroma/config/vm.args' -S /usr/bin/mix phx.server`
-
-Check your OS documentation to adopt a similar strategy on other platforms.
-
-### Virtual Machine and/or few CPU cores
-
-Disable the busy-waiting. This should generally only be done if you're on a platform that does burst scheduling, like AWS.
-
-**vm.args:**
-
-```
-+sbwt none
-+sbwtdcpu none
-+sbwtdio none
-```
-
-### Dedicated Hardware
-
-Enable more busy waiting, increase the internal maximum limit of BEAM processes and ports. You can use this if you run on dedicated hardware, but it is not necessary.
-
-**vm.args:**
-
-```
-+P 16777216
-+Q 16777216
-+K true
-+A 128
-+sbt db
-+sbwt very_long
-+swt very_low
-+sub true
-+Mulmbcs 32767
-+Mumbcgs 1
-+Musmbcs 2047
-```
-
-## Additional Reading
-
-* [WhatsApp: Scaling to Millions of Simultaneous Connections](https://www.erlang-factory.com/upload/presentations/558/efsf2012-whatsapp-scaling.pdf)
-* [Preemptive Scheduling and Spinlocks](https://www.uio.no/studier/emner/matnat/ifi/nedlagte-emner/INF3150/h03/annet/slides/preemptive.pdf)
-* [The Curious Case of BEAM CPU Usage](https://stressgrid.com/blog/beam_cpu_usage/)

docs/configuration/postgresql.md

@@ -1,28 +1,10 @@
-# Optimizing PostgreSQL performance
+# Optimizing your PostgreSQL performance
 
-Pleroma performance is largely dependent on performance of the underlying database. Better performance can be achieved by adjusting a few settings.
+Pleroma performance depends to a large extent on good database performance. The default PostgreSQL settings are mostly fine, but often you can get better performance by changing a few settings.
 
-## PGTune
+You can use [PGTune](https://pgtune.leopard.in.ua) to get recommendations for your setup. If you do, set the "Number of Connections" field to 20, as Pleroma will only use 10 concurrent connections anyway. If you don't, it will give you advice that might even hurt your performance.
 
-[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.
-
-## 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.
-
-By default PostgreSQL has an algorithm to decide which mode is more efficient for particular query, however this algorithm has been observed to be wrong on some of the queries Pleroma sends, leading to serious performance loss. Therefore, it is recommended to disable generic mode.
-
-
-Pleroma already avoids generic query plans by default, however the method it uses is not the most efficient because it needs to be compatible with all supported PostgreSQL versions. For PostgreSQL 12 and higher additional performance can be gained by adding the following to Pleroma configuration:
-```elixir
-config :pleroma, Pleroma.Repo,
-  prepare: :named,
-  parameters: [
-    plan_cache_mode: "force_custom_plan"
-  ]
-```
-
-A more detailed explanation of the issue can be found at <https://blog.soykaf.com/post/postgresql-elixir-troubles/>.
+We also recommend not using the "Network Storage" option.
 
 ## Example configurations
 
@@ -46,3 +28,4 @@ max_worker_processes = 2
 max_parallel_workers_per_gather = 1
 max_parallel_workers = 2
 ```
+

docs/configuration/search.md

@@ -1,147 +0,0 @@
-# Configuring search
-
-{! backend/administration/CLI_tasks/general_cli_task_info.include !}
-
-## Built-in search
-
-To use built-in search that has no external dependencies, set the search module to `Pleroma.Activity`:
-
-> config :pleroma, Pleroma.Search, module: Pleroma.Search.DatabaseSearch
-
-While it has no external dependencies, it has problems with performance and relevancy.
-
-## QdrantSearch
-
-This uses the vector search engine [Qdrant](https://qdrant.tech) to search the posts in a vector space. This needs a way to generate embeddings and uses the [OpenAI API](https://platform.openai.com/docs/guides/embeddings/what-are-embeddings). This is implemented by several project besides OpenAI itself, including the python-based fastembed-server found in `supplemental/search/fastembed-api`.
-
-The default settings will support a setup where both the fastembed server and Qdrant run on the same system as pleroma. To use it, set the search provider and run the fastembed server, see the README in `supplemental/search/fastembed-api`:
-
-> config :pleroma, Pleroma.Search, module: Pleroma.Search.QdrantSearch
-
-Then, start the Qdrant server, see [here](https://qdrant.tech/documentation/quick-start/) for instructions.
-
-You will also need to create the Qdrant index once by running `mix pleroma.search.indexer create_index`. Running `mix pleroma.search.indexer index` will retroactively index the last 100_000 activities.
-
-### Indexing and model options
-
-To see the available configuration options, check out the QdrantSearch section in `config/config.exs`.
-
-The default indexing option work for the default model (`snowflake-arctic-embed-xs`). To optimize for a low memory footprint, adjust the index configuration as described in the [Qdrant docs](https://qdrant.tech/documentation/guides/optimize/). See also [this blog post](https://qdrant.tech/articles/memory-consumption/) that goes into detail.
-
-Different embedding models will need different vector size settings. You can see a list of the models supported by the fastembed server [here](https://qdrant.github.io/fastembed/examples/Supported_Models), including their vector dimensions. These vector dimensions need to be set in the `qdrant_index_configuration`. 
-
-E.g, If you want to use `sentence-transformers/all-MiniLM-L6-v2` as a model, you will not need to adjust things, because it and `snowflake-arctic-embed-xs` are both 384 dimensional models. If you want to use `snowflake/snowflake-arctic-embed-l`, you will need to adjust the `size` parameter in the `qdrant_index_configuration` to 1024, as it has a dimension of 1024.
-
-When using a different model, you will need do drop the index and recreate it (`mix pleroma.search.indexer drop_index` and `mix pleroma.search.indexer create_index`), as the different embeddings are not compatible with each other.
-
-## Meilisearch
-
-Note that it's quite a bit more memory hungry than PostgreSQL (around 4-5G for ~1.2 million
-posts while idle and up to 7G while indexing initially). The disk usage for this additional index is also
-around 4 gigabytes. Like [RUM](./cheatsheet.md#rum-indexing-for-full-text-search) indexes, it offers considerably
-higher performance and ordering by timestamp in a reasonable amount of time.
-Additionally, the search results seem to be more accurate.
-
-Due to high memory usage, it may be best to set it up on a different machine, if running pleroma on a low-resource
-computer, and use private key authentication to secure the remote search instance.
-
-To use [meilisearch](https://www.meilisearch.com/), set the search module to `Pleroma.Search.Meilisearch`:
-
-> config :pleroma, Pleroma.Search, module: Pleroma.Search.Meilisearch
-
-You then need to set the address of the meilisearch instance, and optionally the private key for authentication. You might
-also want to change the `initial_indexing_chunk_size` to be smaller if you're server is not very powerful, but not higher than `100_000`,
-because meilisearch will refuse to process it if it's too big. However, in general you want this to be as big as possible, because meilisearch
-indexes faster when it can process many posts in a single batch.
-
-> config :pleroma, Pleroma.Search.Meilisearch,
->    url: "http://127.0.0.1:7700/",
->    private_key: "private key",
->    initial_indexing_chunk_size: 100_000
-
-Information about setting up meilisearch can be found in the
-[official documentation](https://docs.meilisearch.com/learn/getting_started/installation.html).
-You probably want to start it with `MEILI_NO_ANALYTICS=true` environment variable to disable analytics.
-At least version 0.25.0 is required, but you are strongly advised to use at least 0.26.0, as it introduces
-the `--enable-auto-batching` option which drastically improves performance. Without this option, the search
-is hardly usable on a somewhat big instance.
-
-### Private key authentication (optional)
-
-To set the private key, use the `MEILI_MASTER_KEY` environment variable when starting. After setting the _master key_,
-you have to get the _private key_, which is actually used for authentication.
-
-=== "OTP"
-    ```sh
-    ./bin/pleroma_ctl search.meilisearch show-keys <your master key here>
-    ```
-
-=== "From Source"
-    ```sh
-    mix pleroma.search.meilisearch show-keys <your master key here>
-    ```
-
-You will see a "Default Admin API Key", this is the key you actually put into your configuration file.
-
-### Initial indexing
-
-After setting up the configuration, you'll want to index all of your already existing posts. Only public posts are indexed.  You'll only
-have to do it one time, but it might take a while, depending on the amount of posts your instance has seen. This is also a fairly RAM
-consuming process for `meilisearch`, and it will take a lot of RAM when running if you have a lot of posts (seems to be around 5G for ~1.2
-million posts while idle and up to 7G while indexing initially, but your experience may be different).
-
-The sequence of actions is as follows:
-
-1. First, change the configuration to use `Pleroma.Search.Meilisearch` as the search backend
-2. Restart your instance, at this point it can be used while the search indexing is running, though search won't return anything
-3. Start the initial indexing process (as described below with `index`),
-   and wait until the task says it sent everything from the database to index
-4. Wait until everything is actually indexed (by checking with `stats` as described below),
-   at this point you don't have to do anything, just wait a while.
-
-To start the initial indexing, run the `index` command:
-
-=== "OTP"
-    ```sh
-    ./bin/pleroma_ctl search.meilisearch index
-    ```
-
-=== "From Source"
-    ```sh
-    mix pleroma.search.meilisearch index
-    ```
-
-This will show you the total amount of posts to index, and then show you the amount of posts indexed currently, until the numbers eventually
-become the same. The posts are indexed in big batches and meilisearch will take some time to actually index them, even after you have
-inserted all the posts into it. Depending on the amount of posts, this may be as long as several hours. To get information about the status
-of indexing and how many posts have actually been indexed, use the `stats` command:
-
-=== "OTP"
-    ```sh
-    ./bin/pleroma_ctl search.meilisearch stats
-    ```
-
-=== "From Source"
-    ```sh
-    mix pleroma.search.meilisearch stats
-    ```
-
-### Clearing the index
-
-In case you need to clear the index (for example, to re-index from scratch, if that needs to happen for some reason), you can
-use the `clear` command:
-
-=== "OTP"
-    ```sh
-    ./bin/pleroma_ctl search.meilisearch clear
-    ```
-
-=== "From Source"
-    ```sh
-    mix pleroma.search.meilisearch clear
-    ```
-
-This will clear **all** the posts from the search index. Note, that deleted posts are also removed from index by the instance itself, so
-there is no need to actually clear the whole index, unless you want **all** of it gone. That said, the index does not hold any information
-that cannot be re-created from the database, it should also generally be a lot smaller than the size of your database. Still, the size
-depends on the amount of text in posts.

docs/configuration/static_dir.md

@@ -88,8 +88,3 @@ config :pleroma, :frontend_configurations,
     Note the extra `static` folder for the terms-of-service.html
 
 Terms of Service will be shown to all users on the registration page. It's the best place where to write down the rules for your instance. You can modify the rules by adding and changing `$static_dir/static/terms-of-service.html`.
-
- 	
-## Styling rendered pages
-
-To overwrite the CSS stylesheet of the OAuth form and other static pages, you can upload your own CSS file to `instance/static/static.css`. This will completely replace the CSS used by those pages, so it might be a good idea to copy the one from `priv/static/instance/static.css` and make your changes.

docs/dev.md

@@ -0,0 +1,23 @@
+This document contains notes and guidelines for Pleroma developers.
+
+# Authentication & Authorization
+
+## OAuth token-based authentication & authorization
+
+* Pleroma supports hierarchical OAuth scopes, just like Mastodon but with added granularity of admin scopes. For a reference, see [Mastodon OAuth scopes](https://docs.joinmastodon.org/api/oauth-scopes/).
+
+* It is important to either define OAuth scope restrictions or explicitly mark OAuth scope check as skipped, for every controller action. To define scopes, call `plug(Pleroma.Plugs.OAuthScopesPlug, %{scopes: [...]})`. To explicitly set OAuth scopes check skipped, call `plug(:skip_plug, Pleroma.Plugs.OAuthScopesPlug <when ...>)`.
+
+* In controllers, `use Pleroma.Web, :controller` will result in `action/2` (see `Pleroma.Web.controller/0` for definition) be called prior to actual controller action, and it'll perform security / privacy checks before passing control to actual controller action.
+
+  For routes with `:authenticated_api` pipeline, authentication & authorization are expected, thus `OAuthScopesPlug` will be run unless explicitly skipped (also `EnsureAuthenticatedPlug` will be executed immediately before action even if there was an early run to give an early error, since `OAuthScopesPlug` supports `:proceed_unauthenticated` option, and other plugs may support similar options as well).
+
+  For `:api` pipeline routes, it'll be verified whether `OAuthScopesPlug` was called or explicitly skipped, and if it was not then auth information will be dropped for request. Then `EnsurePublicOrAuthenticatedPlug` will be called to ensure that either the instance is not private or user is authenticated (unless explicitly skipped). Such automated checks help to prevent human errors and result in higher security / privacy for users.
+
+## [HTTP Basic Authentication](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Authorization)
+
+* With HTTP Basic Auth, OAuth scopes check is _not_ performed for any action (since password is provided during the auth, requester is able to obtain a token with full permissions anyways). `Pleroma.Plugs.AuthenticationPlug` and `Pleroma.Plugs.LegacyAuthenticationPlug` both call `Pleroma.Plugs.OAuthScopesPlug.skip_plug(conn)` when password is provided.
+
+## Auth-related configuration, OAuth consumer mode etc.
+
+See `Authentication` section of [the configuration cheatsheet](configuration/cheatsheet.md#authentication).

docs/development/API/differences_in_mastoapi_responses.md

@@ -1,522 +0,0 @@
-# Differences in Mastodon API responses from vanilla Mastodon
-
-A Pleroma instance can be identified by "<Mastodon version> (compatible; Pleroma <version>)" present in `version` field in response from `/api/v1/instance` and `/api/v2/instance`
-
-## Flake IDs
-
-Pleroma uses 128-bit ids as opposed to Mastodon's 64 bits. However, just like Mastodon's ids, they are lexically sortable strings
-
-## Timelines
-
-Adding the parameter `with_muted=true` to the timeline queries will also return activities by muted (not by blocked!) users.
-
-Adding the parameter `exclude_visibilities` to the timeline queries will exclude the statuses with the given visibilities. The parameter accepts an array of visibility types (`public`, `unlisted`, `private`, `direct`), e.g., `exclude_visibilities[]=direct&exclude_visibilities[]=private`.
-
-Adding the parameter `reply_visibility` to the public and home timelines queries will filter replies. Possible values: without parameter (default) shows all replies, `following` - replies directed to you or users you follow, `self` - replies directed to you.
-
-Adding the parameter `instance=lain.com` to the public timeline will show only statuses originating from `lain.com` (or any remote instance).
-
-Home, public, hashtag & list timelines accept these parameters:
-
-- `only_media`: show only statuses with media attached
-- `local`: show only local statuses
-- `remote`: show only remote statuses
-
-## Statuses
-
-- `visibility`: has additional possible values `list` and `local` (for local-only statuses)
-
-Has these additional fields under the `pleroma` object:
-
-- `local`: true if the post was made on the local instance
-- `conversation_id`: the ID of the AP context the status is associated with (if any)
-- `direct_conversation_id`: the ID of the Mastodon direct message conversation the status is associated with (if any)
-- `in_reply_to_account_acct`: the `acct` property of User entity for replied user (if any)
-- `content`: a map consisting of alternate representations of the `content` property with the key being its mimetype. Currently, the only alternate representation supported is `text/plain`
-- `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: 1, me: true}`. Contains no information about the reacting users, for that use the `/statuses/:id/reactions` endpoint.
-- `parent_visible`: If the parent of this post is visible to the user or not.
-- `pinned_at`: a datetime (iso8601) when status was pinned, `null` otherwise.
-- `quotes_count`: the count of status quotes.
-- `non_anonymous`: true if the source post specifies the poll results are not anonymous. Currently only implemented by Smithereen.
-- `bookmark_folder`: the ID of the folder bookmark is stored within (if any).
-- `list_id`: the ID of the list the post is addressed to (if any, only returned to author).
-
-The `GET /api/v1/statuses/:id/source` endpoint additionally has the following attributes:
-
-- `content_type`: The content type of the status source.
-
-## Scheduled statuses
-
-Has these additional fields in `params`:
-
-- `expires_in`: the number of seconds the posted activity should expire in.
-
-## Media Attachments
-
-Has these additional fields under the `pleroma` object:
-
-- `mime_type`: mime type of the attachment.
-
-### Attachment cap
-
-Some apps operate under the assumption that no more than 4 attachments can be returned or uploaded. Pleroma however does not enforce any limits on attachment count neither when returning the status object nor when posting.
-
-### Limitations
-
-Pleroma does not process remote images and therefore cannot include fields such as `meta` and `blurhash`. It does not support focal points or aspect ratios. The frontend is expected to handle it.
-
-## Bookmarks
-
-The `GET /api/v1/bookmarks` endpoint accepts optional parameter `folder_id` for bookmark folder ID.
-
-The `POST /api/v1/statuses/:id/bookmark` endpoint accepts optional parameter `folder_id` for bookmark folder ID.
-
-## Accounts
-
-The `id` parameter can also be the `nickname` of the user. This only works in these endpoints, not the deeper nested ones for following etc.
-
-- `/api/v1/accounts/:id`
-- `/api/v1/accounts/:id/statuses`
-
-`/api/v1/accounts/:id/statuses` endpoint accepts these parameters:
-
-- `pinned`: include only pinned statuses
-- `tagged`: with tag
-- `only_media`: include only statuses with media attached
-- `with_muted`: include statuses/reactions from muted accounts
-- `exclude_reblogs`: exclude reblogs
-- `exclude_replies`: exclude replies
-- `exclude_visibilities`: exclude visibilities
-
-Endpoints which accept `with_relationships` parameter:
-
-- `/api/v1/accounts/:id`
-- `/api/v1/accounts/:id/followers`
-- `/api/v1/accounts/:id/following`
-- `/api/v1/mutes`
-
-Has these additional fields under the `pleroma` object:
-
-- `ap_id`: nullable URL string, ActivityPub id of the user
-- `background_image`: nullable URL string, background image of the user
-- `tags`: Lists an array of tags for the user
-- `relationship` (object): Includes fields as documented for Mastodon API https://docs.joinmastodon.org/entities/relationship/
-- `is_moderator`: boolean, nullable, true if user is a moderator
-- `is_admin`: boolean, nullable, true if user is an admin
-- `confirmation_pending`: boolean, true if a new user account is waiting on email confirmation to be activated
-- `hide_favorites`: boolean, true when the user has hiding favorites enabled
-- `hide_followers`: boolean, true when the user has follower hiding enabled
-- `hide_follows`: boolean, true when the user has follow hiding enabled
-- `hide_followers_count`: boolean, true when the user has follower stat hiding enabled
-- `hide_follows_count`: boolean, true when the user has follow stat hiding enabled
-- `settings_store`: A generic map of settings for frontends. Opaque to the backend. Only returned in `/api/v1/accounts/verify_credentials` and `/api/v1/accounts/update_credentials`
-- `chat_token`: The token needed for Pleroma shoutbox. Only returned in `/api/v1/accounts/verify_credentials`
-- `deactivated`: boolean, true when the user is deactivated
-- `allow_following_move`: boolean, true when the user allows automatically follow moved following accounts
-- `unread_conversation_count`: The count of unread conversations. Only returned to the account owner.
-- `unread_notifications_count`: The count of unread notifications. Only returned to the account owner.
-- `notification_settings`: object, can be absent. See `/api/v1/pleroma/notification_settings` for the parameters/keys returned.
-- `accepts_chat_messages`: boolean, but can be null if we don't have that information about a user
-- `favicon`: nullable URL string, Favicon image of the user's instance
-- `avatar_description`: string, image description for user avatar, defaults to empty string
-- `header_description`: string, image description for user banner, defaults to empty string
-
-### Source
-
-Has these additional fields under the `pleroma` object:
-
-- `show_role`: boolean, nullable, true when the user wants his role (e.g admin, moderator) to be shown
-- `no_rich_text` - boolean, nullable, true when html tags are stripped from all statuses requested from the API
-- `discoverable`: boolean, true when the user allows external services (search bots) etc. to index / list the account (regardless of this setting, user will still appear in regular search results)
-- `actor_type`: string, the type of this account.
-
-## Conversations
-
-Has an additional field under the `pleroma` object:
-
-- `recipients`: The list of the recipients of this Conversation. These will be addressed when replying to this conversation.
-
-## GET `/api/v1/conversations`
-
-Accepts additional parameters:
-
-- `recipients`: Only return conversations with the given recipients (a list of user ids). Usage example: `GET /api/v1/conversations?recipients[]=1&recipients[]=2`
-
-## Account Search
-
-Behavior has changed:
-
-- `/api/v1/accounts/search`: Does not require authentication
-
-## Search (global)
-
-Unlisted posts are available in search results, they are considered to be public posts that shouldn't be shown in local/federated timeline.
-
-## Notifications
-
-Has these additional fields under the `pleroma` object:
-
-- `is_seen`: true if the notification was read by the user
-
-### Move Notification
-
-The `type` value is `move`. Has an additional field:
-
-- `target`: new account
-
-### EmojiReact Notification
-
-The `type` value is `pleroma:emoji_reaction`. Has these fields:
-
-- `emoji`: The used emoji
-- `account`: The account of the user who reacted
-- `status`: The status that was reacted on
-
-### ChatMention Notification (not default)
-
-This notification has to be requested explicitly.
-
-The `type` value is `pleroma:chat_mention`
-
-- `account`: The account who sent the message
-- `chat_message`: The chat message
-
-### Report Notification (not default)
-
-This notification has to be requested explicitly.
-
-The `type` value is `pleroma:report`
-
-- `account`: The account who reported
-- `report`: The report
-
-## GET `/api/v1/notifications`
-
-Accepts additional parameters:
-
-- `exclude_visibilities`: will exclude the notifications for activities with the given visibilities. The parameter accepts an array of visibility types (`public`, `unlisted`, `private`, `direct`). Usage example: `GET /api/v1/notifications?exclude_visibilities[]=direct&exclude_visibilities[]=private`.
-- `include_types`: will include the notifications for activities with the given types. The parameter accepts an array of types (`mention`, `follow`, `reblog`, `favourite`, `move`, `pleroma:emoji_reaction`, `pleroma:chat_mention`, `pleroma:report`). Usage example: `GET /api/v1/notifications?include_types[]=mention&include_types[]=reblog`.
-
-## DELETE `/api/v1/notifications/destroy_multiple`
-
-An endpoint to delete multiple statuses by IDs.
-
-Required parameters:
-
-- `ids`: array of activity ids
-
-Usage example: `DELETE /api/v1/notifications/destroy_multiple/?ids[]=1&ids[]=2`.
-
-Returns on success: 200 OK `{}`
-
-## POST `/api/v1/statuses`
-
-Additional parameters can be added to the JSON body/Form data:
-
-- `preview`: boolean, if set to `true` the post won't be actually posted, but the status entity would still be rendered back. This could be useful for previewing rich text/custom emoji, for example.
-- `content_type`: string, contain the MIME type of the status, it is transformed into HTML by the backend. You can get the list of the supported MIME types with the nodeinfo endpoint.
-- `to`: A list of nicknames (like `lain@soykaf.club` or `lain` on the local server) that will be used to determine who is going to be addressed by this post. Using this will disable the implicit addressing by mentioned names in the `status` body, only the people in the `to` list will be addressed. The normal rules for post visibility are not affected by this and will still apply.
-- `visibility`: string, besides standard MastoAPI values (`direct`, `private`, `unlisted`, `local` or `public`) it can be used to address a List by setting it to `list:LIST_ID`.
-- `expires_in`: The number of seconds the posted activity should expire in. When a posted activity expires it will be deleted from the server, and a delete request for it will be federated. This needs to be longer than an hour.
-- `in_reply_to_conversation_id`: Will reply to a given conversation, addressing only the people who are part of the recipient set of that conversation. Sets the visibility to `direct`.
-
-## GET `/api/v1/statuses`
-
-An endpoint to get multiple statuses by IDs.
-
-Required parameters:
-
-- `ids`: array of activity ids
-
-Usage example: `GET /api/v1/statuses/?ids[]=1&ids[]=2`.
-
-Returns: array of Status.
-
-The maximum number of statuses is limited to 100 per request.
-
-## PATCH `/api/v1/accounts/update_credentials`
-
-Additional parameters can be added to the JSON body/Form data:
-
-- `no_rich_text` - if true, html tags are stripped from all statuses requested from the API
-- `hide_followers` - if true, user's followers will be hidden
-- `hide_follows` - if true, user's follows will be hidden
-- `hide_followers_count` - if true, user's follower count will be hidden
-- `hide_follows_count` - if true, user's follow count will be hidden
-- `hide_favorites` - if true, user's favorites timeline will be hidden
-- `show_role` - if true, user's role (e.g admin, moderator) will be exposed to anyone in the API
-- `default_scope` - the scope returned under `privacy` key in Source subentity
-- `pleroma_settings_store` - Opaque user settings to be saved on the backend.
-- `skip_thread_containment` - if true, skip filtering out broken threads
-- `allow_following_move` - if true, allows automatically follow moved following accounts
-- `also_known_as` - array of ActivityPub IDs, needed for following move
-- `pleroma_background_image` - sets the background image of the user. Can be set to "" (an empty string) to reset.
-- `discoverable` - if true, external services (search bots) etc. are allowed to index / list the account (regardless of this setting, user will still appear in regular search results).
-- `actor_type` - the type of this account.
-- `accepts_chat_messages` - if false, this account will reject all chat messages.
-- `language` - user's preferred language for receiving emails (digest, confirmation, etc.)
-- `avatar_description` - image description for user avatar
-- `header_description` - image description for user banner
-
-All images (avatar, banner and background) can be reset to the default by sending an empty string ("") instead of a file.
-
-### Pleroma Settings Store
-
-Pleroma has mechanism that allows frontends to save blobs of json for each user on the backend. This can be used to save frontend-specific settings for a user that the backend does not need to know about.
-
-The parameter should have a form of `{frontend_name: {...}}`, with `frontend_name` identifying your type of client, e.g. `pleroma_fe`. It will overwrite everything under this property, but will not overwrite other frontend's settings.
-
-This information is returned in the `/api/v1/accounts/verify_credentials` endpoint.
-
-## Authentication
-
-*Pleroma supports refreshing tokens.*
-
-### POST `/oauth/token`
-
-You can obtain access tokens for a user in a few additional ways.
-
-#### Refreshing a token
-
-To obtain a new access token from a refresh token, pass `grant_type=refresh_token` with the following extra parameters:
-
-- `refresh_token`: The refresh token.
-
-#### Getting a token with a password
-
-To obtain a token from a user's password, pass `grant_type=password` with the following extra parameters:
-
-- `username`: Username to authenticate.
-- `password`: The user's password.
-
-#### Response body
-
-Additional fields are returned in the response:
-
-- `id`: The primary key of this token in Pleroma's database.
-- `me` (user tokens only): The ActivityPub ID of the user who owns the token.
-
-## Account Registration
-
-`POST /api/v1/accounts`
-
-Has these additional parameters (which are the same as in Pleroma-API):
-
-- `fullname`: optional
-- `bio`: optional
-- `captcha_solution`: optional, contains provider-specific captcha solution,
-- `captcha_token`: optional, contains provider-specific captcha token
-- `captcha_answer_data`: optional, contains provider-specific captcha data
-- `token`: invite token required when the registrations aren't public.
-- `language`: optional, user's preferred language for receiving emails (digest, confirmation, etc.), default to the language set in the `userLanguage` cookies or `Accept-Language` header.
-
-## Instance
-
-`GET /api/v1/instance` has additional fields
-
-- `max_toot_chars`: The maximum characters per post
-- `max_media_attachments`: Maximum number of post media attachments
-- `chat_limit`: The maximum characters per chat message
-- `description_limit`: The maximum characters per image description
-- `poll_limits`: The limits of polls
-- `shout_limit`: The maximum characters per Shoutbox message
-- `upload_limit`: The maximum upload file size
-- `avatar_upload_limit`: The same for avatars
-- `background_upload_limit`: The same for backgrounds
-- `banner_upload_limit`: The same for banners
-- `background_image`: A background image that frontends can use
-- `pleroma.metadata.account_activation_required`: Whether users are required to confirm their emails before signing in
-- `pleroma.metadata.birthday_required`: Whether users are required to provide their birth day when signing in
-- `pleroma.metadata.birthday_min_age`: The minimum user age (in days)
-- `pleroma.metadata.features`: A list of supported features
-- `pleroma.metadata.federation`: The federation restrictions of this instance
-- `pleroma.metadata.fields_limits`: A list of values detailing the length and count limitation for various instance-configurable fields.
-- `pleroma.metadata.post_formats`: A list of the allowed post format types
-- `pleroma.stats.mau`: Monthly active user count
-- `pleroma.vapid_public_key`: The public key needed for push messages
-
-In, `GET /api/v2/instance` Pleroma-specific fields are all moved into `pleroma` object. `max_toot_chars`, `poll_limits` and `upload_limit` are replaced with their MastoAPI counterparts.
-
-## Push Subscription
-
-`POST /api/v1/push/subscription`
-`PUT /api/v1/push/subscription`
-
-Permits these additional alert types:
-
-- pleroma:chat_mention
-- pleroma:emoji_reaction
-
-## Markers
-
-Has these additional fields under the `pleroma` object:
-
-- `unread_count`: contains number unread notifications
-
-## Streaming
-
-### Chats
-
-There is an additional `user:pleroma_chat` stream. Incoming chat messages will make the current chat be sent to this `user` stream. The `event` of an incoming chat message is `pleroma:chat_update`. The payload is the updated chat with the incoming chat message in the `last_message` field.
-
-### Remote timelines
-
-For viewing remote server timelines, there are `public:remote` and `public:remote:media` streams. Each of these accept a parameter like `?instance=lain.com`.
-
-### Follow relationships updates
-
-Pleroma streams follow relationships updates as `pleroma:follow_relationships_update` events to the `user` stream.
-
-The message payload consist of:
-
-- `state`: a relationship state, one of `follow_pending`, `follow_accept` or `follow_reject`.
-
-- `follower` and `following` maps with following fields:
-  - `id`: user ID
-  - `follower_count`: follower count
-  - `following_count`: following count
-
-### Authenticating via `sec-websocket-protocol` header
-
-Pleroma allows to authenticate via the `sec-websocket-protocol` header, for example, if your access token is `your-access-token`, you can authenticate using the following:
-
-```
-sec-websocket-protocol: your-access-token
-```
-
-### Authenticating after connection via `pleroma:authenticate` event
-
-Pleroma allows to authenticate after connection is established, via the `pleroma:authenticate` event. For example, if your access token is `your-access-token`, you can send the following after the connection is established:
-
-```
-{"type": "pleroma:authenticate", "token": "your-access-token"}
-```
-
-### Response to client-sent events
-
-Pleroma will respond to client-sent events that it recognizes. Supported event types are:
-
-- `subscribe`
-- `unsubscribe`
-- `pleroma:authenticate`
-
-The reply will be in the following format:
-
-```
-{
-  "event": "pleroma:respond",
-  "payload": "{\"type\": \"<type of the client-sent event>\", \"result\": \"<result of the action>\", \"error\": \"<error code>\"}"
-}
-```
-
-Result of the action can be either `success`, `ignored` or `error`. If it is `error`, the `error` property will contain the error code. Otherwise, the `error` property will not be present. Below are some examples:
-
-```
-{
-  "event": "pleroma:respond",
-  "payload": "{\"type\": \"pleroma:authenticate\", \"result\": \"success\"}"
-}
-
-{
-  "event": "pleroma:respond",
-  "payload": "{\"type\": \"subscribe\", \"result\": \"ignored\"}"
-}
-
-{
-  "event": "pleroma:respond",
-  "payload": "{\"type\": \"unsubscribe\", \"result\": \"error\", \"error\": \"bad_topic\"}"
-}
-```
-
-If the sent event is not of a type that Pleroma supports, it will not reply.
-
-### The `stream` attribute of a server-sent event
-
-Technically, this is in Mastodon, but its documentation does nothing to specify its format.
-
-This attribute appears on every event type except `pleroma:respond` and `delete`. It helps clients determine where they should display the new statuses.
-
-The value of the attribute is an array containing one or two elements. The first element is the type of the stream. The second is the identifier related to that specific stream, if applicable.
-
-For the following stream types, there is a second element in the array:
-
-- `list`: The second element is the id of the list, as a string.
-- `hashtag`: The second element is the name of the hashtag.
-- `public:remote:media` and `public:remote`: The second element is the domain of the corresponding instance.
-
-For all other stream types, there is no second element.
-
-Some examples of valid `stream` values:
-
-- `["list", "1"]`: List of id 1.
-- `["hashtag", "mew"]`: The hashtag #mew.
-- `["user:notifications"]`: Notifications for the current user.
-- `["user"]`: Home timeline.
-- `["public:remote", "mew.moe"]`: Public posts from the instance mew.moe .
-
-### The unified streaming endpoint
-
-If you do not specify a stream to connect to when requesting `/api/v1/streaming`, you will enter a connection that subscribes to no streams. After the connection is established, you can authenticate and then subscribe to different streams.
-
-### List of supported streams
-
-Below is a list of supported streams by Pleroma. To make a single-stream WebSocket connection, append the string specified in "Query style" to the streaming endpoint url.
-To subscribe to a stream after the connection is established, merge the JSON object specified in "Subscribe style" with `{"type": "subscribe"}`. To unsubscribe, merge it with `{"type": "unsubscribe"}`.
-
-For example, to receive updates on the list 1, you can connect to `/api/v1/streaming/?stream=list&list=1`, or send
-
-```
-{"type": "subscribe", "stream": "list", "list": "1"}
-```
-
-upon establishing the websocket connection.
-
-To unsubscribe to list 1, send
-
-```
-{"type": "unsubscribe", "stream": "list", "list": "1"}
-```
-
-Note that if you specify a stream that requires a logged-in user in the query string (for example, `user` or `list`), you have to specify the access token when you are trying to establish the connection, i.e. in the query string or via the `sec-websocket-protocol` header.
-
-- `list`
-  - Query style: `?stream=list&list=<id>`
-  - Subscribe style: `{"stream": "list", "list": "<id>"}`
-- `public`, `public:local`, `public:media`, `public:local:media`, `user`, `user:pleroma_chat`, `user:notifications`, `direct`
-  - Query style: `?stream=<stream name>`
-  - Subscribe style: `{"stream": "<stream name>"}`
-- `hashtag`
-  - Query style: `?stream=hashtag&tag=<name>`
-  - Subscribe style: `{"stream": "hashtag", "tag": "<name>"}`
-- `public:remote`, `public:remote:media`
-  - Query style: `?stream=<stream name>&instance=<instance domain>`
-  - Subscribe style: `{"stream": "<stream name>", "instance": "<instance domain>"}`
-
-## User muting and thread muting
-
-Both user muting and thread muting can be done for only a certain time by adding an `expires_in` parameter to the API calls and giving the expiration time in seconds.
-
-## Not implemented
-
-Pleroma is generally compatible with the Mastodon 2.7.2 API, but some newer features and non-essential features are omitted. These features usually return an HTTP 200 status code, but with an empty response. While they may be added in the future, they are considered low priority.
-
-### Suggestions
-
-*Added in Mastodon 2.4.3*
-
-- `GET /api/v1/suggestions`: Returns an empty array, `[]`
-
-### Trends
-
-*Added in Mastodon 3.0.0*
-
-- `GET /api/v1/trends`: Returns an empty array, `[]`
-
-### Featured tags
-
-*Added in Mastodon 3.0.0*
-
-- `GET /api/v1/featured_tags`: Returns HTTP 404

docs/development/API/nodeinfo.md

@@ -1,347 +0,0 @@
-# Nodeinfo
-
-See also [the Nodeinfo standard](https://nodeinfo.diaspora.software/).
-
-## `/.well-known/nodeinfo`
-### The well-known path
-* Method: `GET`
-* Authentication: not required
-* Params: none
-* Response: JSON
-* Example response:
-```json
-{
-   "links":[
-      {
-         "href":"https://example.com/nodeinfo/2.0.json",
-         "rel":"http://nodeinfo.diaspora.software/ns/schema/2.0"
-      },
-      {
-         "href":"https://example.com/nodeinfo/2.1.json",
-         "rel":"http://nodeinfo.diaspora.software/ns/schema/2.1"
-      }
-   ]
-}
-```
-
-## `/nodeinfo/2.0.json`
-### Nodeinfo 2.0
-* Method: `GET`
-* Authentication: not required
-* Params: none
-* Response: JSON
-* Example response:
-```json
-{
-   "metadata":{
-      "accountActivationRequired":false,
-      "features":[
-         "pleroma_api",
-         "mastodon_api",
-         "mastodon_api_streaming",
-         "polls",
-         "pleroma_explicit_addressing",
-         "shareable_emoji_packs",
-         "multifetch",
-         "pleroma:api/v1/notifications:include_types_filter",
-         "chat",
-         "shout",
-         "relay",
-         "pleroma_emoji_reactions",
-         "pleroma_chat_messages"
-      ],
-      "federation":{
-         "enabled":true,
-         "exclusions":false,
-         "mrf_hashtag":{
-            "federated_timeline_removal":[
-               
-            ],
-            "reject":[
-               
-            ],
-            "sensitive":[
-               "nsfw"
-            ]
-         },
-         "mrf_object_age":{
-            "actions":[
-               "delist",
-               "strip_followers"
-            ],
-            "threshold":604800
-         },
-         "mrf_policies":[
-            "ObjectAgePolicy",
-            "TagPolicy",
-            "HashtagPolicy"
-         ],
-         "quarantined_instances":[
-            
-         ]
-      },
-      "fieldsLimits":{
-         "maxFields":10,
-         "maxRemoteFields":20,
-         "nameLength":512,
-         "valueLength":2048
-      },
-      "invitesEnabled":false,
-      "mailerEnabled":false,
-      "nodeDescription":"Pleroma: An efficient and flexible fediverse server",
-      "nodeName":"Example",
-      "pollLimits":{
-         "max_expiration":31536000,
-         "max_option_chars":200,
-         "max_options":20,
-         "min_expiration":0
-      },
-      "postFormats":[
-         "text/plain",
-         "text/html",
-         "text/markdown",
-         "text/bbcode"
-      ],
-      "private":false,
-      "restrictedNicknames":[
-         ".well-known",
-         "~",
-         "about",
-         "activities",
-         "api",
-         "auth",
-         "check_password",
-         "dev",
-         "friend-requests",
-         "inbox",
-         "internal",
-         "main",
-         "media",
-         "nodeinfo",
-         "notice",
-         "oauth",
-         "objects",
-         "ostatus_subscribe",
-         "pleroma",
-         "proxy",
-         "push",
-         "registration",
-         "relay",
-         "settings",
-         "status",
-         "tag",
-         "user-search",
-         "user_exists",
-         "users",
-         "web",
-         "verify_credentials",
-         "update_credentials",
-         "relationships",
-         "search",
-         "confirmation_resend",
-         "mfa"
-      ],
-      "skipThreadContainment":true,
-      "staffAccounts":[
-         "https://example.com/users/admin",
-         "https://example.com/users/staff"
-      ],
-      "suggestions":{
-         "enabled":false
-      },
-      "uploadLimits":{
-         "avatar":2000000,
-         "background":4000000,
-         "banner":4000000,
-         "general":16000000
-      }
-   },
-   "openRegistrations":true,
-   "protocols":[
-      "activitypub"
-   ],
-   "services":{
-      "inbound":[
-         
-      ],
-      "outbound":[
-         
-      ]
-   },
-   "software":{
-      "name":"pleroma",
-      "version":"2.4.1"
-   },
-   "usage":{
-      "localPosts":27,
-      "users":{
-         "activeHalfyear":129,
-         "activeMonth":70,
-         "total":235
-      }
-   },
-   "version":"2.0"
-}
-```
-
-## `/nodeinfo/2.1.json`
-### Nodeinfo 2.1
-* Method: `GET`
-* Authentication: not required
-* Params: none
-* Response: JSON
-* Example response:
-```json
-{
-   "metadata":{
-      "accountActivationRequired":false,
-      "features":[
-         "pleroma_api",
-         "mastodon_api",
-         "mastodon_api_streaming",
-         "polls",
-         "pleroma_explicit_addressing",
-         "shareable_emoji_packs",
-         "multifetch",
-         "pleroma:api/v1/notifications:include_types_filter",
-         "chat",
-         "shout",
-         "relay",
-         "pleroma_emoji_reactions",
-         "pleroma_chat_messages"
-      ],
-      "federation":{
-         "enabled":true,
-         "exclusions":false,
-         "mrf_hashtag":{
-            "federated_timeline_removal":[
-               
-            ],
-            "reject":[
-               
-            ],
-            "sensitive":[
-               "nsfw"
-            ]
-         },
-         "mrf_object_age":{
-            "actions":[
-               "delist",
-               "strip_followers"
-            ],
-            "threshold":604800
-         },
-         "mrf_policies":[
-            "ObjectAgePolicy",
-            "TagPolicy",
-            "HashtagPolicy"
-         ],
-         "quarantined_instances":[
-            
-         ]
-      },
-      "fieldsLimits":{
-         "maxFields":10,
-         "maxRemoteFields":20,
-         "nameLength":512,
-         "valueLength":2048
-      },
-      "invitesEnabled":false,
-      "mailerEnabled":false,
-      "nodeDescription":"Pleroma: An efficient and flexible fediverse server",
-      "nodeName":"Example",
-      "pollLimits":{
-         "max_expiration":31536000,
-         "max_option_chars":200,
-         "max_options":20,
-         "min_expiration":0
-      },
-      "postFormats":[
-         "text/plain",
-         "text/html",
-         "text/markdown",
-         "text/bbcode"
-      ],
-      "private":false,
-      "restrictedNicknames":[
-         ".well-known",
-         "~",
-         "about",
-         "activities",
-         "api",
-         "auth",
-         "check_password",
-         "dev",
-         "friend-requests",
-         "inbox",
-         "internal",
-         "main",
-         "media",
-         "nodeinfo",
-         "notice",
-         "oauth",
-         "objects",
-         "ostatus_subscribe",
-         "pleroma",
-         "proxy",
-         "push",
-         "registration",
-         "relay",
-         "settings",
-         "status",
-         "tag",
-         "user-search",
-         "user_exists",
-         "users",
-         "web",
-         "verify_credentials",
-         "update_credentials",
-         "relationships",
-         "search",
-         "confirmation_resend",
-         "mfa"
-      ],
-      "skipThreadContainment":true,
-      "staffAccounts":[
-         "https://example.com/users/admin",
-         "https://example.com/users/staff"
-      ],
-      "suggestions":{
-         "enabled":false
-      },
-      "uploadLimits":{
-         "avatar":2000000,
-         "background":4000000,
-         "banner":4000000,
-         "general":16000000
-      }
-   },
-   "openRegistrations":true,
-   "protocols":[
-      "activitypub"
-   ],
-   "services":{
-      "inbound":[
-         
-      ],
-      "outbound":[
-         
-      ]
-   },
-   "software":{
-      "name":"pleroma",
-      "repository":"https://git.pleroma.social/pleroma/pleroma",
-      "version":"2.4.1"
-   },
-   "usage":{
-      "localPosts":27,
-      "users":{
-         "activeHalfyear":129,
-         "activeMonth":70,
-         "total":235
-      }
-   },
-   "version":"2.1"
-}
-```
-

docs/development/API/pleroma_api.md

@@ -1,848 +0,0 @@
-# Pleroma API
-
-Requests that require it can be authenticated with [an OAuth token](https://tools.ietf.org/html/rfc6749), the `_pleroma_key` cookie, or [HTTP Basic Authentication](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Authorization).
-
-Request parameters can be passed via [query strings](https://en.wikipedia.org/wiki/Query_string) or as [form data](https://www.w3.org/TR/html401/interact/forms.html). Files must be uploaded as `multipart/form-data`.
-
-The `/api/v1/pleroma/*` path is backwards compatible with `/api/pleroma/*` (`/api/pleroma/*` will be deprecated in the future).
-
-## `/api/v1/pleroma/emoji`
-### Lists the custom emoji on that server.
-* Method: `GET`
-* Authentication: not required
-* Params: none
-* Response: JSON
-* Example response:
-```json
-{
-  "girlpower": {
-    "tags": [
-      "Finmoji"
-    ],
-    "image_url": "/finmoji/128px/girlpower-128.png"
-  },
-  "education": {
-    "tags": [
-      "Finmoji"
-    ],
-    "image_url": "/finmoji/128px/education-128.png"
-  },
-  "finnishlove": {
-    "tags": [
-      "Finmoji"
-    ],
-    "image_url": "/finmoji/128px/finnishlove-128.png"
-  }
-}
-```
-* Note: Same data as Mastodon API’s `/api/v1/custom_emojis` but in a different format
-
-## `/api/pleroma/follow_import`
-### Imports your follows, for example from a Mastodon CSV file.
-* Method: `POST`
-* Authentication: required
-* Params:
-    * `list`: STRING or FILE containing a whitespace-separated list of accounts to follow
-* Response: HTTP 200 on success, 500 on error
-* Note: Users that can't be followed are silently skipped.
-
-## `/api/pleroma/blocks_import`
-### Imports your blocks.
-* Method: `POST`
-* Authentication: required
-* Params:
-    * `list`: STRING or FILE containing a whitespace-separated list of accounts to block
-* Response: HTTP 200 on success, 500 on error
-
-## `/api/pleroma/mutes_import`
-### Imports your mutes.
-* Method: `POST`
-* Authentication: required
-* Params:
-    * `list`: STRING or FILE containing a whitespace-separated list of accounts to mute
-* Response: HTTP 200 on success, 500 on error
-
-## `/api/v1/pleroma/captcha`
-### Get a new captcha
-* Method: `GET`
-* Authentication: not required
-* Params: none
-* Response: Provider specific JSON, the only guaranteed parameter is `type`
-* Example response: `{"type": "kocaptcha", "token": "whatever", "url": "https://captcha.kotobank.ch/endpoint", "seconds_valid": 300}`
-
-## `/api/pleroma/delete_account`
-### Delete an account
-* Method `POST`
-* Authentication: required
-* Params:
-    * `password`: user's password
-* Response: JSON. Returns `{"status": "success"}` if the deletion was successful, `{"error": "[error message]"}` otherwise
-* Example response: `{"error": "Invalid password."}`
-
-## `/api/pleroma/disable_account`
-### Disable an account
-* Method `POST`
-* Authentication: required
-* Params:
-    * `password`: user's password
-* Response: JSON. Returns `{"status": "success"}` if the account was successfully disabled, `{"error": "[error message]"}` otherwise
-* Example response: `{"error": "Invalid password."}`
-
-## `/api/pleroma/accounts/mfa`
-#### Gets current MFA settings
-* method: `GET`
-* Authentication: required
-* OAuth scope: `read:security`
-* Response: JSON. Returns `{"settings": {"enabled": "false", "totp": false }}`
-* Note: `enabled` is whether multi-factor auth is enabled for the user in general, while `totp` is one type of MFA.
-
-## `/api/pleroma/accounts/mfa/setup/totp`
-#### Pre-setup the MFA/TOTP method
-* method: `GET`
-* Authentication: required
-* OAuth scope: `write:security`
-* Response: JSON. Returns `{"key": [secret_key], "provisioning_uri": "[qr code uri]"  }` when successful, otherwise returns HTTP 422 `{"error": "error_msg"}`
-
-## `/api/pleroma/accounts/mfa/confirm/totp`
-#### Confirms & enables MFA/TOTP support for user account.
-* method: `POST`
-* Authentication: required
-* OAuth scope: `write:security`
-* Params:
-    * `password`: user's password
-    * `code`: token from TOTP App
-* Response: JSON. Returns `{}` if the enable was successful, HTTP 422 `{"error": "[error message]"}` otherwise
-
-
-## `/api/pleroma/accounts/mfa/totp`
-####  Disables MFA/TOTP method for user account.
-* method: `DELETE`
-* Authentication: required
-* OAuth scope: `write:security`
-* Params:
-    * `password`: user's password
-* Response: JSON. Returns `{}` if the disable was successful, HTTP 422 `{"error": "[error message]"}` otherwise
-* Example response: `{"error": "Invalid password."}`
-
-## `/api/pleroma/accounts/mfa/backup_codes`
-####  Generstes backup codes MFA for user account.
-* method: `GET`
-* Authentication: required
-* OAuth scope: `write:security`
-* Response: JSON. Returns `{"codes": codes}` when successful, otherwise HTTP 422 `{"error": "[error message]"}`
-
-## `/api/v1/pleroma/admin/`
-See [Admin-API](admin_api.md)
-
-## `/api/v1/pleroma/notifications/read`
-### Mark notifications as read
-* Method `POST`
-* Authentication: required
-* Params (mutually exclusive):
-    * `id`: a single notification id to read
-    * `max_id`: read all notifications up to this id
-* Response: Notification entity/Array of Notification entities that were read. In case of `max_id`, only the first 80 read notifications will be returned.
-
-## `/api/v1/pleroma/accounts/:id/subscribe`
-### Subscribe to receive notifications for all statuses posted by a user
-
-Deprecated. `notify` parameter in `POST /api/v1/accounts/:id/follow` should be used instead.
-
-* Method `POST`
-* Authentication: required
-* Params:
-    * `id`: account id to subscribe to
-* Response: JSON, returns a mastodon relationship object on success, otherwise returns `{"error": "error_msg"}`
-* Example response:
-```json
-{
-  "id": "abcdefg",
-  "following": true,
-  "followed_by": false,
-  "blocking": false,
-  "muting": false,
-  "muting_notifications": false,
-  "subscribing": true,
-  "notifying": true,
-  "requested": false,
-  "domain_blocking": false,
-  "showing_reblogs": true,
-  "endorsed": false,
-  "note": ""
-}
-```
-
-## `/api/v1/pleroma/accounts/:id/unsubscribe`
-### Unsubscribe to stop receiving notifications from user statuses
-
-Deprecated. `notify` parameter in `POST /api/v1/accounts/:id/follow` should be used instead.
-
-* Method `POST`
-* Authentication: required
-* Params:
-    * `id`: account id to unsubscribe from
-* Response: JSON, returns a mastodon relationship object on success, otherwise returns `{"error": "error_msg"}`
-* Example response:
-```json
-{
-  "id": "abcdefg",
-  "following": true,
-  "followed_by": false,
-  "blocking": false,
-  "muting": false,
-  "muting_notifications": false,
-  "subscribing": false,
-  "notifying": false,
-  "requested": false,
-  "domain_blocking": false,
-  "showing_reblogs": true,
-  "endorsed": false,
-  "note": ""
-}
-```
-
-## `/api/v1/pleroma/accounts/:id/favourites`
-### Returns favorites timeline of any user
-* Method `GET`
-* Authentication: not required
-* Params:
-    * `id`: the id of the account for whom to return results
-    * `limit`: optional, the number of records to retrieve
-    * `since_id`: optional, returns results that are more recent than the specified id
-    * `max_id`: optional, returns results that are older than the specified id
-* Response: JSON, returns a list of Mastodon Status entities on success, otherwise returns `{"error": "error_msg"}`
-* Example response:
-```json
-[
-  {
-    "account": {
-      "id": "9hptFmUF3ztxYh3Svg",
-      "url": "https://pleroma.example.org/users/nick2",
-      "username": "nick2",
-      ...
-    },
-    "application": {"name": "Web", "website": null},
-    "bookmarked": false,
-    "card": null,
-    "content": "This is :moominmamma: note 0",
-    "created_at": "2019-04-15T15:42:15.000Z",
-    "emojis": [],
-    "favourited": false,
-    "favourites_count": 1,
-    "id": "9hptFmVJ02khbzYJaS",
-    "in_reply_to_account_id": null,
-    "in_reply_to_id": null,
-    "language": null,
-    "media_attachments": [],
-    "mentions": [],
-    "muted": false,
-    "pinned": false,
-    "pleroma": {
-      "content": {"text/plain": "This is :moominmamma: note 0"},
-      "conversation_id": 13679,
-      "local": true,
-      "spoiler_text": {"text/plain": "2hu"}
-    },
-    "reblog": null,
-    "reblogged": false,
-    "reblogs_count": 0,
-    "replies_count": 0,
-    "sensitive": false,
-    "spoiler_text": "2hu",
-    "tags": [{"name": "2hu", "url": "/tag/2hu"}],
-    "uri": "https://pleroma.example.org/objects/198ed2a1-7912-4482-b559-244a0369e984",
-    "url": "https://pleroma.example.org/notice/9hptFmVJ02khbzYJaS",
-    "visibility": "public"
-  }
-]
-```
-
-
-## `/api/v1/pleroma/accounts/:id/endorsements`
-### Returns users endorsed by a user
-* Method `GET`
-* Authentication: not required
-* Params:
-    * `id`: the id of the account for whom to return results
-* Response: JSON, returns a list of Mastodon Account entities
-
-## `/api/v1/pleroma/accounts/update_*`
-### Set and clear account avatar, banner, and background
-
-- PATCH `/api/v1/pleroma/accounts/update_avatar`: Set/clear user avatar image
-- PATCH `/api/v1/pleroma/accounts/update_banner`: Set/clear user banner image
-- PATCH `/api/v1/pleroma/accounts/update_background`: Set/clear user background image
-
-## `/api/v1/pleroma/accounts/confirmation_resend`
-### Resend confirmation email
-* Method `POST`
-* Params:
-    * `email`: email of that needs to be verified
-* Authentication: not required
-* Response: 204 No Content
-
-## `/api/v1/pleroma/statuses/:id/quotes`
-### Gets quotes for a given status
-* Method `GET`
-* Authentication: not required
-* Params:
-    * `id`: the id of the status
-* Response: JSON, returns a list of Mastodon Status entities
-
-## `GET /api/v1/pleroma/bookmark_folders`
-### Gets user bookmark folders
-* Authentication: required
-
-* Response: JSON. Returns a list of bookmark folders.
-* Example response:
-```json
-[
-    {
-        "id": "9umDrYheeY451cQnEe",
-        "name": "Read later",
-        "emoji": "🕓",
-        "emoji_url": null
-    }
-]
-```
-
-## `POST /api/v1/pleroma/bookmark_folders`
-### Creates a bookmark folder
-* Authentication: required
-
-* Params:
-    * `name`: folder name
-    * `emoji`: folder emoji (optional)
-* Response: JSON. Returns a single bookmark folder.
-
-## `PATCH /api/v1/pleroma/bookmark_folders/:id`
-### Updates a bookmark folder
-* Authentication: required
-
-* Params:
-    * `id`: folder id
-    * `name`: folder name (optional)
-    * `emoji`: folder emoji (optional)
-* Response: JSON. Returns a single bookmark folder.
-
-## `DELETE /api/v1/pleroma/bookmark_folders/:id`
-### Deletes a bookmark folder
-* Authentication: required
-
-* Params:
-    * `id`: folder id
-* Response: JSON. Returns a single bookmark folder.
-
-## `/api/v1/pleroma/mascot`
-### Gets user mascot image
-* Method `GET`
-* Authentication: required
-
-* Response: JSON. Returns a mastodon media attachment entity.
-* Example response:
-```json
-{
-    "id": "abcdefg",
-    "url": "https://pleroma.example.org/media/abcdefg.png",
-    "type": "image",
-    "pleroma": {
-        "mime_type": "image/png"
-    }
-}
-```
-
-### Updates user mascot image
-* Method `PUT`
-* Authentication: required
-* Params:
-    * `file`: Multipart image
-* Response: JSON. Returns a mastodon media attachment entity
-  when successful, otherwise returns HTTP 415 `{"error": "error_msg"}`
-* Example response:
-```json
-{
-    "id": "abcdefg",
-    "url": "https://pleroma.example.org/media/abcdefg.png",
-    "type": "image",
-    "pleroma": {
-        "mime_type": "image/png"
-    }
-}
-```
-* Note: Behaves exactly the same as `POST /api/v1/upload`.
-  Can only accept images - any attempt to upload non-image files will be met with `HTTP 415 Unsupported Media Type`.
-
-## `/api/pleroma/notification_settings`
-### Updates user notification settings
-* Method `PUT`
-* Authentication: required
-* Params:
-    * `block_from_strangers`: BOOLEAN field, blocks notifications from accounts you do not follow
-    * `hide_notification_contents`: BOOLEAN field. When set to true, it removes the contents of a message from the push notification.
-* Response: JSON. Returns `{"status": "success"}` if the update was successful, otherwise returns `{"error": "error_msg"}`
-
-## `/api/v1/pleroma/healthcheck`
-### Healthcheck endpoint with additional system data.
-* Method `GET`
-* Authentication: not required
-* Params: none
-* Response: JSON, statuses (200 - healthy, 503 unhealthy).
-* Example response:
-```json
-{
-  "pool_size": 0, # database connection pool
-  "active": 0, # active processes
-  "idle": 0, # idle processes
-  "memory_used": 0.00, # Memory used
-  "healthy": true, # Instance state
-  "job_queue_stats": {} # Job queue stats
-}
-```
-
-## `/api/pleroma/change_email`
-### Change account email
-* Method `POST`
-* Authentication: required
-* Params:
-    * `password`: user's password
-    * `email`: new email
-* Response: JSON. Returns `{"status": "success"}` if the change was successful, `{"error": "[error message]"}` otherwise
-* Note: Currently, Mastodon has no API for changing email. If they add it in future it might be incompatible with Pleroma.
-
-## `/api/pleroma/move_account`
-### Move account
-* Method `POST`
-* Authentication: required
-* Params:
-    * `password`: user's password
-    * `target_account`: the nickname of the target account (e.g. `foo@example.org`)
-* Response: JSON. Returns `{"status": "success"}` if the change was successful, `{"error": "[error message]"}` otherwise
-* Note: This endpoint emits a `Move` activity to all followers of the current account. Some remote servers will automatically unfollow the current account and follow the target account upon seeing this, but this depends on the remote server implementation and cannot be guaranteed. For local followers , they will automatically unfollow and follow if and only if they have set the `allow_following_move` preference ("Allow auto-follow when following account moves").
-
-## `/api/pleroma/aliases`
-### Get aliases of the current account
-* Method `GET`
-* Authentication: required
-* Response: JSON. Returns `{"aliases": [alias, ...]}`, where `alias` is the nickname of an alias, e.g. `foo@example.org`.
-
-### Add alias to the current account
-* Method `PUT`
-* Authentication: required
-* Params:
-    * `alias`: the nickname of the alias to add, e.g. `foo@example.org`.
-* Response: JSON. Returns `{"status": "success"}` if the change was successful, `{"error": "[error message]"}` otherwise
-
-### Delete alias from the current account
-* Method `DELETE`
-* Authentication: required
-* Params:
-    * `alias`: the nickname of the alias to delete, e.g. `foo@example.org`.
-* Response: JSON. Returns `{"status": "success"}` if the change was successful, `{"error": "[error message]"}` otherwise
-
-## `/api/v1/pleroma/remote_interaction`
-## Interact with profile or status from remote account
-* Metod `POST`
-* Authentication: not required
-* Params:
-    * `ap_id`: Profile or status ActivityPub ID
-    * `profile`: Remote profile webfinger
-* Response: JSON. Returns `{"url": "[redirect url]"}` on success, `{"error": "[error message]"}` otherwise
-
-# Pleroma Conversations
-
-Pleroma Conversations have the same general structure that Mastodon Conversations have. The behavior differs in the following ways when using these endpoints:
-
-1. Pleroma Conversations never add or remove recipients, unless explicitly changed by the user.
-2. Pleroma Conversations statuses can be requested by Conversation id.
-3. Pleroma Conversations can be replied to.
-
-Conversations have the additional field `recipients` under the `pleroma` key. This holds a list of all the accounts that will receive a message in this conversation.
-
-The status posting endpoint takes an additional parameter, `in_reply_to_conversation_id`, which, when set, will set the visibility to direct and address only the people who are the recipients of that Conversation.
-
-⚠ Conversation IDs can be found in direct messages with the `pleroma.direct_conversation_id` key, do not confuse it with `pleroma.conversation_id`.
-
-## `GET /api/v1/pleroma/conversations/:id/statuses`
-### Timeline for a given conversation
-* Method `GET`
-* Authentication: required
-* Params: Like other timelines
-* Response: JSON, statuses (200 - healthy, 503 unhealthy).
-
-## `GET /api/v1/pleroma/conversations/:id`
-### The conversation with the given ID.
-* Method `GET`
-* Authentication: required
-* Params: None
-* Response: JSON, statuses (200 - healthy, 503 unhealthy).
-
-## `PATCH /api/v1/pleroma/conversations/:id`
-### Update a conversation. Used to change the set of recipients.
-* Method `PATCH`
-* Authentication: required
-* Params:
-    * `recipients`: A list of ids of users that should receive posts to this conversation. This will replace the current list of recipients, so submit the full list. The owner of owner of the conversation will always be part of the set of recipients, though.
-* Response: JSON, statuses (200 - healthy, 503 unhealthy)
-
-## `POST /api/v1/pleroma/conversations/read`
-### Marks all user's conversations as read.
-* Method `POST`
-* Authentication: required
-* Params: None
-* Response: JSON, returns a list of Mastodon Conversation entities that were marked as read (200 - healthy, 503 unhealthy).
-
-## `GET /api/v1/pleroma/emoji/pack?name=:name`
-
-### Get pack.json for the pack
-
-* Method `GET`
-* Authentication: not required
-* Params:
-  * `page`: page number for files (default 1)
-  * `page_size`: page size for files (default 30)
-* Response: JSON, pack json with `files`, `files_count` and `pack` keys with 200 status or 404 if the pack does not exist.
-
-```json
-{
-  "files": {...},
-  "files_count": 0, // emoji count in pack
-  "pack": {...}
-}
-```
-
-## `POST /api/v1/pleroma/emoji/pack?name=:name`
-
-### Creates an empty pack
-
-* Method `POST`
-* Authentication: required (admin)
-* Params:
-  * `name`: pack name
-* Response: JSON, "ok" and 200 status or 409 if the pack with that name already exists
-
-## `PATCH /api/v1/pleroma/emoji/pack?name=:name`
-
-### Updates (replaces) pack metadata
-
-* Method `PATCH`
-* Authentication: required (admin)
-* Params:
-  * `name`: pack name
-  * `metadata`: metadata to replace the old one
-    * `license`: Pack license
-    * `homepage`: Pack home page url
-    * `description`: Pack description
-    * `fallback-src`: Fallback url to download pack from
-    * `fallback-src-sha256`: SHA256 encoded for fallback pack archive
-    * `share-files`: is pack allowed for sharing (boolean)
-* Response: JSON, updated "metadata" section of the pack and 200 status or 400 if there was a
-  problem with the new metadata (the error is specified in the "error" part of the response JSON)
-
-## `DELETE /api/v1/pleroma/emoji/pack?name=:name`
-
-### Delete a custom emoji pack
-
-* Method `DELETE`
-* Authentication: required (admin)
-* Params:
-  * `name`: pack name
-* Response: JSON, "ok" and 200 status or 500 if there was an error deleting the pack
-
-## `GET /api/v1/pleroma/emoji/packs/import`
-
-### Imports packs from filesystem
-
-* Method `GET`
-* Authentication: required (admin)
-* Params: None
-* Response: JSON, returns a list of imported packs.
-
-## `GET /api/v1/pleroma/emoji/packs/remote`
-
-### Make request to another instance for packs list
-
-* Method `GET`
-* Authentication: required (admin)
-* Params:
-  * `url`: url of the instance to get packs from
-  * `page`: page number for packs (default 1)
-  * `page_size`: page size for packs (default 50)
-* Response: JSON with the pack list, hashmap with pack name and pack contents
-
-## `POST /api/v1/pleroma/emoji/packs/download`
-
-### Download pack from another instance
-
-* Method `POST`
-* Authentication: required (admin)
-* Params:
-  * `url`: url of the instance to download from
-  * `name`: pack to download from that instance
-  * `as`: (*optional*) name how to save pack
-* Response: JSON, "ok" with 200 status if the pack was downloaded, or 500 if there were
-  errors downloading the pack
-
-## `POST /api/v1/pleroma/emoji/packs/files?name=:name`
-
-### Add new file to the pack
-
-* Method `POST`
-* Authentication: required (admin)
-* Params:
-  * `name`: pack name
-  * `file`: file needs to be uploaded with the multipart request or link to remote file.
-  * `shortcode`: (*optional*) shortcode for new emoji, must be unique for all emoji. If not sended, shortcode will be taken from original filename.
-  * `filename`: (*optional*) new emoji file name. If not specified will be taken from original filename.
-* Response: JSON, list of files for updated pack (hashmap -> shortcode => filename) with status 200, either error status with error message.
-
-## `PATCH /api/v1/pleroma/emoji/packs/files?name=:name`
-
-### Update emoji file from pack
-
-* Method `PATCH`
-* Authentication: required (admin)
-* Params:
-  * `name`: pack name
-  * `shortcode`: emoji file shortcode
-  * `new_shortcode`: new emoji file shortcode
-  * `new_filename`: new filename for emoji file
-  * `force`: (*optional*) with true value to overwrite existing emoji with new shortcode
-* Response: JSON, list with updated files for updated pack (hashmap -> shortcode => filename) with status 200, either error status with error message.
-
-## `DELETE /api/v1/pleroma/emoji/packs/files?name=:name`
-
-### Delete emoji file from pack
-
-* Method `DELETE`
-* Authentication: required (admin)
-* Params:
-  * `name`: pack name
-  * `shortcode`: emoji file shortcode
-* Response: JSON, list with updated files for updated pack (hashmap -> shortcode => filename) with status 200, either error status with error message.
-
-## `GET /api/v1/pleroma/emoji/packs`
-
-### Lists local custom emoji packs
-
-* Method `GET`
-* Authentication: not required
-* Params:
-  * `page`: page number for packs (default 1)
-  * `page_size`: page size for packs (default 50)
-* Response: `packs` key with JSON hashmap of pack name to pack contents and `count` key for count of packs.
-
-```json
-{
-  "packs": {
-    "pack_name": {...}, // pack contents
-    ...
-  },
-  "count": 0 // packs count
-}
-```
-
-## `GET /api/v1/pleroma/emoji/packs/archive?name=:name`
-
-### Requests a local pack archive from the instance
-
-* Method `GET`
-* Authentication: not required
-* Params:
-  * `name`: pack name
-* Response: the archive of the pack with a 200 status code, 403 if the pack is not set as shared,
-  404 if the pack does not exist
-
-## `GET /api/v1/pleroma/accounts/:id/scrobbles`
-
-Audio scrobbling in Pleroma is **deprecated**.
-
-### Requests a list of current and recent Listen activities for an account
-* Method `GET`
-* Authentication: not required
-* Params: None
-* Response: An array of media metadata entities.
-* Example response:
-```json
-[
-   {
-       "account": {...},
-       "id": "1234",
-       "title": "Some Title",
-       "artist": "Some Artist",
-       "album": "Some Album",
-       "length": 180000,
-       "created_at": "2019-09-28T12:40:45.000Z"
-   }
-]
-```
-
-## `POST /api/v1/pleroma/scrobble`
-
-Audio scrobbling in Pleroma is **deprecated**.
-
-### Creates a new Listen activity for an account
-* Method `POST`
-* Authentication: required
-* Params:
-  * `title`: the title of the media playing
-  * `album`: the album of the media playing [optional]
-  * `artist`: the artist of the media playing [optional]
-  * `length`: the length of the media playing [optional]
-* Response: the newly created media metadata entity representing the Listen activity
-
-# Emoji Reactions
-
-Emoji reactions work a lot like favourites do. They make it possible to react to a post with a single emoji character. To detect the presence of this feature, you can check `pleroma_emoji_reactions` entry in the features list of nodeinfo.
-
-## `PUT /api/v1/pleroma/statuses/:id/reactions/:emoji`
-### React to a post with a unicode emoji
-* Method: `PUT`
-* Authentication: required
-* Params: `emoji`: A unicode RGI emoji or a regional indicator
-* Response: JSON, the status.
-
-## `DELETE /api/v1/pleroma/statuses/:id/reactions/:emoji`
-### Remove a reaction to a post with a unicode emoji
-* Method: `DELETE`
-* Authentication: required
-* Params: `emoji`: A unicode RGI emoji or a regional indicator
-* Response: JSON, the status.
-
-## `GET /api/v1/pleroma/statuses/:id/reactions`
-### Get an object of emoji to account mappings with accounts that reacted to the post
-* Method: `GET`
-* Authentication: optional
-* Params: None
-* Response: JSON, a list of emoji/account list tuples, sorted by emoji insertion date, in ascending order, e.g, the first emoji in the list is the oldest.
-* Example Response:
-```json
-[
-  {"name": "😀", "count": 2, "me": true, "accounts": [{"id" => "xyz.."...}, {"id" => "zyx..."}]},
-  {"name": "☕", "count": 1, "me": false, "accounts": [{"id" => "abc..."}]}
-]
-```
-
-## `GET /api/v1/pleroma/statuses/:id/reactions/:emoji`
-### Get an object of emoji to account mappings with accounts that reacted to the post for a specific emoji
-* Method: `GET`
-* Authentication: optional
-* Params: None
-* Response: JSON, a list of emoji/account list tuples
-* Example Response:
-```json
-[
-  {"name": "😀", "count": 2, "me": true, "accounts": [{"id" => "xyz.."...}, {"id" => "zyx..."}]}
-]
-```
-
-## `POST /api/v1/pleroma/backups`
-### Create a user backup archive
-
-* Method: `POST`
-* Authentication: required
-* Params: none
-* Response: JSON
-* Example response:
-
-```json
-[{
-    "content_type": "application/zip",
-    "file_size": 0,
-    "inserted_at": "2020-09-10T16:18:03.000Z",
-    "processed": false,
-    "url": "https://example.com/media/backups/archive-foobar-20200910T161803-QUhx6VYDRQ2wfV0SdA2Pfj_2CLM_ATUlw-D5l5TJf4Q.zip"
-}]
-```
-
-## `GET /api/v1/pleroma/backups`
-### Lists user backups
-
-* Method: `GET`
-* Authentication: not required
-* Params: none
-* Response: JSON
-* Example response:
-
-```json
-[{
-    "content_type": "application/zip",
-    "file_size": 55457,
-    "inserted_at": "2020-09-10T16:18:03.000Z",
-    "processed": true,
-    "url": "https://example.com/media/backups/archive-foobar-20200910T161803-QUhx6VYDRQ2wfV0SdA2Pfj_2CLM_ATUlw-D5l5TJf4Q.zip"
-}]
-```
-
-## `GET /api/oauth_tokens`
-### Retrieve a list of active sessions for the user
-* Method: `GET`
-* Authentication: required
-* Params: none
-* Response: JSON
-* Example response:
-
-```json
-[
-  {
-    "app_name": "Pleroma FE",
-    "id": 9275,
-    "valid_until": "2121-11-24T15:51:08.234234"
-  },
-  {
-    "app_name": "Patron",
-    "id": 8805,
-    "valid_until": "2121-10-26T18:09:59.857150"
-  },
-  {
-    "app_name": "Soapbox FE",
-    "id": 9727,
-    "valid_until": "2121-12-25T16:52:39.692877"
-  }
-]
-```
-
-## `DELETE /api/oauth_tokens/:id`
-### Revoke a user session by its ID
-* Method: `DELETE`
-* Authentication: required
-* Params: none
-* Response: HTTP 200 on success, 500 on error
-
-## `/api/v1/pleroma/settings/:app`
-### Gets settings for some application
-* Method `GET`
-* Authentication: `read:accounts`
-
-* Response: JSON. The settings for that application, or empty object if there is none.
-* Example response:
-```json
-{
-  "some key": "some value"
-}
-```
-
-### Updates settings for some application
-* Method `PATCH`
-* Authentication: `write:accounts`
-* Request body: JSON object. The object will be merged recursively with old settings. If some field is set to null, it is removed.
-* Example request:
-```json
-{
-  "some key": "some value",
-  "key to remove": null,
-  "nested field": {
-    "some key": "some value",
-    "key to remove": null
-  }
-}
-```
-* Response: JSON. Updated (merged) settings for that application.
-* Example response:
-```json
-{
-  "some key": "some value",
-  "nested field": {
-    "some key": "some value",
-  }
-}
-```

docs/development/API/prometheus.md

@@ -1,47 +0,0 @@
-# Prometheus / OpenTelemetry Metrics
-
-Pleroma includes support for exporting metrics via the [prom_ex](https://github.com/akoutmos/prom_ex) library.
-The metrics are exposed by a dedicated webserver/port to improve privacy and security.
-
-Config example:
-
-```
-config :pleroma, Pleroma.PromEx,
-  disabled: false,
-  manual_metrics_start_delay: :no_delay,
-  drop_metrics_groups: [],
-  grafana: [
-    host: System.get_env("GRAFANA_HOST", "http://localhost:3000"),
-    auth_token: System.get_env("GRAFANA_TOKEN"),
-    upload_dashboards_on_start: false,
-    folder_name: "BEAM",
-    annotate_app_lifecycle: true
-  ],
-  metrics_server: [
-    port: 4021,
-    path: "/metrics",
-    protocol: :http,
-    pool_size: 5,
-    cowboy_opts: [],
-    auth_strategy: :none
-  ],
-  datasource: "Prometheus"
-
-```
-
-PromEx supports the ability to automatically publish dashboards to your Grafana server as well as register Annotations. If you do not wish to configure this capability you must generate the dashboard JSON files and import them directly. You can find the mix commands in the upstream [documentation](https://hexdocs.pm/prom_ex/Mix.Tasks.PromEx.Dashboard.Export.html). You can find the list of modules enabled in Pleroma for which you should generate dashboards for by examining the contents of the `lib/pleroma/prom_ex.ex` module.
-
-## prometheus.yml
-
-The following is a bare minimum config example to use with [Prometheus](https://prometheus.io) or Prometheus-compatible software like [VictoriaMetrics](https://victoriametrics.com).
-
-```
-global:
-  scrape_interval: 15s
-
-scrape_configs:
-  - job_name: 'pleroma'
-    scheme: http
-    static_configs:
-    - targets: ['pleroma.soykaf.com:4021']
-```

docs/development/ap_extensions.md

@@ -1,65 +0,0 @@
-# AP Extensions
-## Actor endpoints
-
-The following endpoints are additionally present into our actors.
-
-- `oauthRegistrationEndpoint` (`http://litepub.social/ns#oauthRegistrationEndpoint`)
-- `uploadMedia` (`https://www.w3.org/ns/activitystreams#uploadMedia`)
-
-### oauthRegistrationEndpoint
-
-Points to MastodonAPI `/api/v1/apps` for now.
-
-See <https://docs.joinmastodon.org/methods/apps/>
-
-### uploadMedia
-
-Inspired by <https://www.w3.org/wiki/SocialCG/ActivityPub/MediaUpload>, it is part of the ActivityStreams namespace because it used to be part of the ActivityPub specification and got removed from it.
-
-Content-Type: multipart/form-data
-
-Parameters:
-- (required) `file`: The file being uploaded
-- (optional) `description`: A plain-text description of the media, for accessibility purposes.
-
-Response: HTTP 201 Created with the object into the body, no `Location` header provided as it doesn't have an `id`
-
-The object given in the response should then be inserted into an Object's `attachment` field.
-
-## ChatMessages
-
-`ChatMessage`s are the messages sent in 1-on-1 chats. They are similar to
-`Note`s, but the addressing is done by having a single AP actor in the `to`
-field. Addressing multiple actors is not allowed. These messages are always
-private, there is no public version of them. They are created with a `Create`
-activity.
-
-They are part of the `litepub` namespace as `http://litepub.social/ns#ChatMessage`.
-
-Example:
-
-```json
-{
-  "actor": "http://2hu.gensokyo/users/raymoo",
-  "id": "http://2hu.gensokyo/objects/1",
-  "object": {
-    "attributedTo": "http://2hu.gensokyo/users/raymoo",
-    "content": "You expected a cute girl? Too bad.",
-    "id": "http://2hu.gensokyo/objects/2",
-    "published": "2020-02-12T14:08:20Z",
-    "to": [
-      "http://2hu.gensokyo/users/marisa"
-    ],
-    "type": "ChatMessage"
-  },
-  "published": "2018-02-12T14:08:20Z",
-  "to": [
-    "http://2hu.gensokyo/users/marisa"
-  ],
-  "type": "Create"
-}
-```
-
-This setup does not prevent multi-user chats, but these will have to go through
-a `Group`, which will be the recipient of the messages and then `Announce` them
-to the users in the `Group`.

docs/development/authentication_authorization.md

@@ -1,21 +0,0 @@
-# Authentication & Authorization
-
-## OAuth token-based authentication & authorization
-
-* Pleroma supports hierarchical OAuth scopes, just like Mastodon but with added granularity of admin scopes. For a reference, see [Mastodon OAuth scopes](https://docs.joinmastodon.org/api/oauth-scopes/).
-
-* It is important to either define OAuth scope restrictions or explicitly mark OAuth scope check as skipped, for every controller action. To define scopes, call `plug(Pleroma.Web.Plugs.OAuthScopesPlug, %{scopes: [...]})`. To explicitly set OAuth scopes check skipped, call `plug(:skip_plug, Pleroma.Web.Plugs.OAuthScopesPlug <when ...>)`.
-
-* In controllers, `use Pleroma.Web, :controller` will result in `action/2` (see `Pleroma.Web.controller/0` for definition) be called prior to actual controller action, and it'll perform security / privacy checks before passing control to actual controller action.
-
-  For routes with `:authenticated_api` pipeline, authentication & authorization are expected, thus `OAuthScopesPlug` will be run unless explicitly skipped (also `EnsureAuthenticatedPlug` will be executed immediately before action even if there was an early run to give an early error, since `OAuthScopesPlug` supports `:proceed_unauthenticated` option, and other plugs may support similar options as well).
-
-  For `:api` pipeline routes, it'll be verified whether `OAuthScopesPlug` was called or explicitly skipped, and if it was not then auth information will be dropped for request. Then `EnsurePublicOrAuthenticatedPlug` will be called to ensure that either the instance is not private or user is authenticated (unless explicitly skipped). Such automated checks help to prevent human errors and result in higher security / privacy for users.
-
-## Non-OAuth authentication
-
-* With non-OAuth authentication ([HTTP Basic Authentication](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Authorization) or HTTP header- or params-provided auth), OAuth scopes check is _not_ performed for any action (since password is provided during the auth, requester is able to obtain a token with full permissions anyways); auth plugs invoke `Pleroma.Helpers.AuthHelper.skip_oauth(conn)` in this case.
-
-## Auth-related configuration, OAuth consumer mode etc.
-
-See `Authentication` section of [the configuration cheatsheet](../configuration/cheatsheet.md#authentication).

docs/development/index.md

@@ -1,7 +0,0 @@
-This section contains notes and guidelines for developers.
-
-- [Setting up a Pleroma development environment](setting_up_pleroma_dev.md)
-- [Setting up a Gitlab Runner](setting_up_a_gitlab_runner.md)
-- [Authentication & Authorization](authentication_authorization.md)
-- [ActivityPub Extensions](ap_extensions.md)
-- [Mox Testing Guide](mox_testing.md)

docs/development/mox_testing.md

@@ -1,485 +0,0 @@
-# Using Mox for Testing in Pleroma
-
-## Introduction
-
-This guide explains how to use [Mox](https://hexdocs.pm/mox/Mox.html) for testing in Pleroma and how to migrate existing tests from Mock/meck to Mox. Mox is a library for defining concurrent mocks in Elixir that offers several key advantages:
-
-- **Async-safe testing**: Mox supports concurrent testing with `async: true`
-- **Explicit contract through behaviors**: Enforces implementation of behavior callbacks
-- **No module redefinition**: Avoids runtime issues caused by redefining modules
-- **Expectations scoped to the current process**: Prevents test state from leaking between tests
-
-## Why Migrate from Mock/meck to Mox?
-
-### Problems with Mock/meck
-
-1. **Not async-safe**: Tests using Mock/meck cannot safely run with `async: true`, which slows down the test suite
-2. **Global state**: Mocked functions are global, leading to potential cross-test contamination
-3. **No explicit contract**: No guarantee that mocked functions match the actual implementation
-4. **Module redefinition**: Can lead to hard-to-debug runtime issues
-
-### Benefits of Mox
-
-1. **Async-safe testing**: Tests can run concurrently with `async: true`, significantly speeding up the test suite
-2. **Process isolation**: Expectations are set per process, preventing leakage between tests
-3. **Explicit contracts via behaviors**: Ensures mocks implement all required functions
-4. **Compile-time checks**: Prevents mocking non-existent functions
-5. **No module redefinition**: Mocks are defined at compile time, not runtime
-
-## Existing Mox Setup in Pleroma
-
-Pleroma already has a basic Mox setup in the `Pleroma.DataCase` module, which handles some common mocking scenarios automatically. Here's what's included:
-
-### Default Mox Configuration
-
-The `setup` function in `DataCase` does the following:
-
-1. Sets up Mox for either async or non-async tests
-2. Verifies all mock expectations on test exit
-3. Stubs common dependencies with their real implementations
-
-```elixir
-# From test/support/data_case.ex
-setup tags do
-  setup_multi_process_mode(tags)
-  setup_streamer(tags)
-  stub_pipeline()
-
-  Mox.verify_on_exit!()
-
-  :ok
-end
-```
-
-### Async vs. Non-Async Test Setup
-
-Pleroma configures Mox differently depending on whether your test is async or not:
-
-```elixir
-def setup_multi_process_mode(tags) do
-  :ok = Ecto.Adapters.SQL.Sandbox.checkout(Pleroma.Repo)
-
-  if tags[:async] do
-    # For async tests, use process-specific mocks and stub CachexMock with NullCache
-    Mox.stub_with(Pleroma.CachexMock, Pleroma.NullCache)
-    Mox.set_mox_private()
-  else
-    # For non-async tests, use global mocks and stub CachexMock with CachexProxy
-    Ecto.Adapters.SQL.Sandbox.mode(Pleroma.Repo, {:shared, self()})
-
-    Mox.set_mox_global()
-    Mox.stub_with(Pleroma.CachexMock, Pleroma.CachexProxy)
-    clear_cachex()
-  end
-
-  :ok
-end
-```
-
-### Default Pipeline Stubs
-
-Pleroma automatically stubs several core components with their real implementations:
-
-```elixir
-def stub_pipeline do
-  Mox.stub_with(Pleroma.Web.ActivityPub.SideEffectsMock, Pleroma.Web.ActivityPub.SideEffects)
-  Mox.stub_with(Pleroma.Web.ActivityPub.ObjectValidatorMock, Pleroma.Web.ActivityPub.ObjectValidator)
-  Mox.stub_with(Pleroma.Web.ActivityPub.MRFMock, Pleroma.Web.ActivityPub.MRF)
-  Mox.stub_with(Pleroma.Web.ActivityPub.ActivityPubMock, Pleroma.Web.ActivityPub.ActivityPub)
-  Mox.stub_with(Pleroma.Web.FederatorMock, Pleroma.Web.Federator)
-  Mox.stub_with(Pleroma.ConfigMock, Pleroma.Config)
-  Mox.stub_with(Pleroma.StaticStubbedConfigMock, Pleroma.Test.StaticConfig)
-  Mox.stub_with(Pleroma.StubbedHTTPSignaturesMock, Pleroma.Test.HTTPSignaturesProxy)
-end
-```
-
-This means that by default, these mocks will behave like their real implementations unless you explicitly override them with expectations in your tests.
-
-### Understanding Config Mock Types
-
-Pleroma has three different Config mock implementations, each with a specific purpose and different characteristics regarding async test safety:
-
-#### 1. ConfigMock
-
-- Defined in `test/support/mocks.ex` as `Mox.defmock(Pleroma.ConfigMock, for: Pleroma.Config.Getting)`
-- It's stubbed with the real `Pleroma.Config` by default in `DataCase`: `Mox.stub_with(Pleroma.ConfigMock, Pleroma.Config)`
-- This means it falls back to the normal configuration behavior unless explicitly overridden
-- Used for general mocking of configuration in tests where you want most config to behave normally
-- ⚠️ **NOT ASYNC-SAFE**: Since it's stubbed with the real `Pleroma.Config`, it modifies global application state
-- Can not be used in tests with `async: true`
-
-#### 2. StaticStubbedConfigMock
-
-- Defined in `test/support/mocks.ex` as `Mox.defmock(Pleroma.StaticStubbedConfigMock, for: Pleroma.Config.Getting)`
-- It's stubbed with `Pleroma.Test.StaticConfig` (defined in `test/test_helper.exs`)
-- `Pleroma.Test.StaticConfig` creates a completely static configuration snapshot at the start of the test run:
-  ```elixir
-  defmodule Pleroma.Test.StaticConfig do
-    @moduledoc """
-    This module provides a Config that is completely static, built at startup time from the environment. 
-    It's safe to use in testing as it will not modify any state.
-    """
-
-    @behaviour Pleroma.Config.Getting
-    @config Application.get_all_env(:pleroma)
-
-    def get(path, default \\ nil) do
-      get_in(@config, path) || default
-    end
-  end
-  ```
-- Configuration is frozen at startup time and doesn't change during the test run
-- ✅ **ASYNC-SAFE**: Never modifies global state since it uses a frozen snapshot of the configuration
-
-#### 3. UnstubbedConfigMock
-
-- Defined in `test/support/mocks.ex` as `Mox.defmock(Pleroma.UnstubbedConfigMock, for: Pleroma.Config.Getting)`
-- Unlike the other two mocks, it's not automatically stubbed with any implementation in `DataCase`
-- Starts completely "unstubbed" and requires tests to explicitly set expectations or stub it
-- The most commonly used configuration mock in the test suite
-- Often aliased as `ConfigMock` in individual test files: `alias Pleroma.UnstubbedConfigMock, as: ConfigMock`
-- Set as the default config implementation in `config/test.exs`: `config :pleroma, :config_impl, Pleroma.UnstubbedConfigMock`
-- Offers maximum flexibility for tests that need precise control over configuration values
-- ✅ **ASYNC-SAFE**: Safe if used with `expect()` to set up test-specific expectations (since expectations are process-scoped)
-
-#### Configuring Components to Use Specific Mocks
-
-In `config/test.exs`, different components can be configured to use different configuration mocks:
-
-```elixir
-# Components using UnstubbedConfigMock
-config :pleroma, Pleroma.Upload, config_impl: Pleroma.UnstubbedConfigMock
-config :pleroma, Pleroma.User.Backup, config_impl: Pleroma.UnstubbedConfigMock
-config :pleroma, Pleroma.Uploaders.S3, config_impl: Pleroma.UnstubbedConfigMock
-
-# Components using StaticStubbedConfigMock (async-safe)
-config :pleroma, Pleroma.Language.LanguageDetector, config_impl: Pleroma.StaticStubbedConfigMock
-config :pleroma, Pleroma.Web.RichMedia.Helpers, config_impl: Pleroma.StaticStubbedConfigMock
-config :pleroma, Pleroma.Web.Plugs.HTTPSecurityPlug, config_impl: Pleroma.StaticStubbedConfigMock
-```
-
-This allows different parts of the application to use the most appropriate configuration mocking strategy based on their specific needs.
-
-#### When to Use Each Config Mock Type
-
-- **ConfigMock**: ⚠️ For non-async tests only, when you want most configuration to behave normally with occasional overrides
-- **StaticStubbedConfigMock**: ✅ For async tests where modifying global state would be problematic and a static configuration is sufficient
-- **UnstubbedConfigMock**: ⚠️ Use carefully in async tests; set specific expectations rather than stubbing with implementations that modify global state
-
-#### Summary of Async Safety
-
-| Mock Type | Async-Safe? | Best Use Case |
-|-----------|-------------|--------------|
-| ConfigMock | ❌ No | Non-async tests that need minimal configuration overrides |
-| StaticStubbedConfigMock | ✅ Yes | Async tests that need configuration values without modification |
-| UnstubbedConfigMock | ⚠️ Depends | Any test with careful usage; set expectations rather than stubbing |
-
-## Configuration in Async Tests
-
-### Understanding `clear_config` Limitations
-
-The `clear_config` helper is commonly used in Pleroma tests to modify configuration for specific tests. However, it's important to understand that **`clear_config` is not async-safe** and should not be used in tests with `async: true`.
-
-Here's why:
-
-```elixir
-# Implementation of clear_config in test/support/helpers.ex
-defmacro clear_config(config_path, temp_setting) do
-  quote do
-    clear_config(unquote(config_path)) do
-      Config.put(unquote(config_path), unquote(temp_setting))
-    end
-  end
-end
-
-defmacro clear_config(config_path, do: yield) do
-  quote do
-    initial_setting = Config.fetch(unquote(config_path))
-
-    unquote(yield)
-
-    on_exit(fn ->
-      case initial_setting do
-        :error ->
-          Config.delete(unquote(config_path))
-
-        {:ok, value} ->
-          Config.put(unquote(config_path), value)
-      end
-    end)
-
-    :ok
-  end
-end
-```
-
-The issue is that `clear_config`:
-1. Modifies the global application environment
-2. Uses `on_exit` to restore the original value after the test
-3. Can lead to race conditions when multiple async tests modify the same configuration
-
-### Async-Safe Configuration Approaches
-
-When writing async tests with Mox, use these approaches instead of `clear_config`:
-
-1. **Dependency Injection with Module Attributes**:
-   ```elixir
-   # In your module
-   @config_impl Application.compile_env(:pleroma, [__MODULE__, :config_impl], Pleroma.Config)
-   
-   def some_function do
-     value = @config_impl.get([:some, :config])
-     # ...
-   end
-   ```
-
-2. **Mock the Config Module**:
-   ```elixir
-   # In your test
-   Pleroma.ConfigMock
-   |> expect(:get, fn [:some, :config] -> "test_value" end)
-   ```
-
-3. **Use Test-Specific Implementations**:
-   ```elixir
-   # Define a test-specific implementation
-   defmodule TestConfig do
-     def get([:some, :config]), do: "test_value"
-     def get(_), do: nil
-   end
-   
-   # In your test
-   Mox.stub_with(Pleroma.ConfigMock, TestConfig)
-   ```
-
-4. **Pass Configuration as Arguments**:
-   ```elixir
-   # Refactor functions to accept configuration as arguments
-   def some_function(config \\ nil) do
-     config = config || Pleroma.Config.get([:some, :config])
-     # ...
-   end
-   
-   # In your test
-   some_function("test_value")
-   ```
-
-By using these approaches, you can safely run tests with `async: true` without worrying about configuration conflicts.
-
-## Setting Up Mox in Pleroma
-
-### Step 1: Define a Behavior
-
-Start by defining a behavior for the module you want to mock. This specifies the contract that both the real implementation and mocks must follow.
-
-```elixir
-# In your implementation module (e.g., lib/pleroma/uploaders/s3.ex)
-defmodule Pleroma.Uploaders.S3.ExAwsAPI do
-  @callback request(op :: ExAws.Operation.t()) :: {:ok, ExAws.Operation.t()} | {:error, term()}
-end
-```
-
-### Step 2: Make Your Implementation Configurable
-
-Modify your module to use a configurable implementation. This allows for dependency injection and easier testing.
-
-```elixir
-# In your implementation module
-@ex_aws_impl Application.compile_env(:pleroma, [__MODULE__, :ex_aws_impl], ExAws)
-@config_impl Application.compile_env(:pleroma, [__MODULE__, :config_impl], Pleroma.Config)
-
-def put_file(%Pleroma.Upload{} = upload) do
-  # Use @ex_aws_impl instead of ExAws directly
-  case @ex_aws_impl.request(op) do
-    {:ok, _} ->
-      {:ok, {:file, s3_name}}
-
-    error ->
-      Logger.error("#{__MODULE__}: #{inspect(error)}")
-      error
-  end
-end
-```
-
-### Step 3: Define the Mock in test/support/mocks.ex
-
-Add your mock definition in the central mocks file:
-
-```elixir
-# In test/support/mocks.ex
-Mox.defmock(Pleroma.Uploaders.S3.ExAwsMock, for: Pleroma.Uploaders.S3.ExAwsAPI)
-```
-
-### Step 4: Configure the Mock in Test Environment
-
-In your test configuration (e.g., `config/test.exs`), specify which mock implementation to use:
-
-```elixir
-config :pleroma, Pleroma.Uploaders.S3, ex_aws_impl: Pleroma.Uploaders.S3.ExAwsMock
-config :pleroma, Pleroma.Uploaders.S3, config_impl: Pleroma.UnstubbedConfigMock
-```
-
-## Writing Tests with Mox
-
-### Setting Up Your Test
-
-```elixir
-defmodule Pleroma.Uploaders.S3Test do
-  use Pleroma.DataCase, async: true  # Note: async: true is now possible!
-
-  alias Pleroma.Uploaders.S3
-  alias Pleroma.Uploaders.S3.ExAwsMock
-  alias Pleroma.UnstubbedConfigMock, as: ConfigMock
-
-  import Mox  # Import Mox functions
-  
-  # Note: verify_on_exit! is already called in DataCase setup
-  # so you don't need to add it explicitly in your test module
-end
-```
-
-### Setting Expectations with Mox
-
-Mox uses an explicit expectation system. Here's how to use it:
-
-```elixir
-# Basic expectation for a function call
-ExAwsMock
-|> expect(:request, fn _req -> {:ok, %{status_code: 200}} end)
-
-# Expectation for multiple calls with same response
-ExAwsMock
-|> expect(:request, 3, fn _req -> {:ok, %{status_code: 200}} end)
-
-# Expectation with specific arguments
-ExAwsMock
-|> expect(:request, fn %{bucket: "test_bucket"} -> {:ok, %{status_code: 200}} end)
-
-# Complex configuration mocking
-ConfigMock
-|> expect(:get, fn key ->
-  [
-    {Pleroma.Upload, [uploader: Pleroma.Uploaders.S3, base_url: "https://s3.amazonaws.com"]},
-    {Pleroma.Uploaders.S3, [bucket: "test_bucket"]}
-  ]
-  |> get_in(key)
-end)
-```
-
-### Understanding Mox Modes in Pleroma
-
-Pleroma's DataCase automatically configures Mox differently based on whether your test is async or not:
-
-1. **Async tests** (`async: true`):
-   - Uses `Mox.set_mox_private()` - expectations are scoped to the current process
-   - Stubs `Pleroma.CachexMock` with `Pleroma.NullCache`
-   - Each test process has its own isolated mock expectations
-
-2. **Non-async tests** (`async: false`):
-   - Uses `Mox.set_mox_global()` - expectations are shared across processes
-   - Stubs `Pleroma.CachexMock` with `Pleroma.CachexProxy`
-   - Mock expectations can be set in one process and called from another
-
-Choose the appropriate mode based on your test requirements. For most tests, async mode is preferred for better performance.
-
-## Migrating from Mock/meck to Mox
-
-Here's a step-by-step guide for migrating existing tests from Mock/meck to Mox:
-
-### 1. Identify the Module to Mock
-
-Look for `with_mock` or `test_with_mock` calls in your tests:
-
-```elixir
-# Old approach with Mock
-with_mock ExAws, request: fn _ -> {:ok, :ok} end do
-  assert S3.put_file(file_upload) == {:ok, {:file, "test_folder/image-tet.jpg"}}
-end
-```
-
-### 2. Define a Behavior for the Module
-
-Create a behavior that defines the functions you want to mock:
-
-```elixir
-defmodule Pleroma.Uploaders.S3.ExAwsAPI do
-  @callback request(op :: ExAws.Operation.t()) :: {:ok, ExAws.Operation.t()} | {:error, term()}
-end
-```
-
-### 3. Update Your Implementation to Use a Configurable Dependency
-
-```elixir
-# Old
-def put_file(%Pleroma.Upload{} = upload) do
-  case ExAws.request(op) do
-    # ...
-  end
-end
-
-# New
-@ex_aws_impl Application.compile_env(:pleroma, [__MODULE__, :ex_aws_impl], ExAws)
-
-def put_file(%Pleroma.Upload{} = upload) do
-  case @ex_aws_impl.request(op) do
-    # ...
-  end
-end
-```
-
-### 4. Define the Mock in mocks.ex
-
-```elixir
-Mox.defmock(Pleroma.Uploaders.S3.ExAwsMock, for: Pleroma.Uploaders.S3.ExAwsAPI)
-```
-
-### 5. Configure the Test Environment
-
-```elixir
-config :pleroma, Pleroma.Uploaders.S3, ex_aws_impl: Pleroma.Uploaders.S3.ExAwsMock
-```
-
-### 6. Update Your Tests to Use Mox
-
-```elixir
-# Old (with Mock)
-test_with_mock "save file", ExAws, request: fn _ -> {:ok, :ok} end do
-  assert S3.put_file(file_upload) == {:ok, {:file, "test_folder/image-tet.jpg"}}
-  assert_called(ExAws.request(:_))
-end
-
-# New (with Mox)
-test "save file" do
-  ExAwsMock
-  |> expect(:request, fn _req -> {:ok, %{status_code: 200}} end)
-
-  assert S3.put_file(file_upload) == {:ok, {:file, "test_folder/image-tet.jpg"}}
-end
-```
-
-### 7. Enable Async Testing
-
-Now you can safely enable `async: true` in your test module:
-
-```elixir
-use Pleroma.DataCase, async: true
-```
-
-## Best Practices
-
-1. **Always define behaviors**: They serve as contracts and documentation
-2. **Keep mocks in a central location**: Use test/support/mocks.ex for all mock definitions
-3. **Use verify_on_exit!**: This is already set up in DataCase, ensuring all expected calls were made
-4. **Use specific expectations**: Be as specific as possible with your expectations
-5. **Enable async: true**: Take advantage of Mox's concurrent testing capability
-6. **Don't over-mock**: Only mock external dependencies that are difficult to test directly
-7. **Leverage existing stubs**: Use the default stubs provided by DataCase when possible
-8. **Avoid clear_config in async tests**: Use dependency injection and mocking instead
-
-## Example: Complete Migration
-
-For a complete example of migrating a test from Mock/meck to Mox, you can refer to commit `90a47ca050c5839e8b4dc3bac315dc436d49152d` in the Pleroma repository, which shows how the S3 uploader tests were migrated.
-
-## Conclusion
-
-Migrating tests from Mock/meck to Mox provides significant benefits for the Pleroma test suite, including faster test execution through async testing, better isolation between tests, and more robust mocking through explicit contracts. By following this guide, you can successfully migrate existing tests and write new tests using Mox.