From 7baa240841ef8830a8cb3f07fc80edfcad371c61 Mon Sep 17 00:00:00 2001 From: Alexander Tumin Date: Sat, 29 Jan 2022 23:17:06 +0300 Subject: [PATCH] WebFinger documentation clarifications --- .../how_to_serve_another_domain_for_webfinger.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/configuration/how_to_serve_another_domain_for_webfinger.md b/docs/configuration/how_to_serve_another_domain_for_webfinger.md index b6e699e59..d544f8b94 100644 --- a/docs/configuration/how_to_serve_another_domain_for_webfinger.md +++ b/docs/configuration/how_to_serve_another_domain_for_webfinger.md @@ -52,5 +52,8 @@ Some BEs and FEs may still use AP id instead of account subject to present user ### Warnings -Change `host` in `Pleroma.Web.Endpoint` with caution, it may result in local accounts being duplicated on remote instances, -which will affect federation. +Change `host` in `Pleroma.Web.Endpoint` and `domain` in `Pleroma.Web.WebFinger` with caution, it will likely result in +local accounts being duplicated on remote instances, which will affect federation and users reachability. + +Webfinger results are generally cached by server implementations and may only be requested once (on first account encounter) +or with set rate limit depending on the implementation.