From 01c5d5a29cab6c2fb7a0464d52e264f3648508e6 Mon Sep 17 00:00:00 2001 From: ThibG Date: Wed, 3 May 2017 09:32:18 +0200 Subject: [PATCH] Add note on PuSH issue with Mastodon v1.3.2 --- Running-Mastodon/Serving_a_different_domain.md | 1 + 1 file changed, 1 insertion(+) diff --git a/Running-Mastodon/Serving_a_different_domain.md b/Running-Mastodon/Serving_a_different_domain.md index 46a4704..b1b9a34 100644 --- a/Running-Mastodon/Serving_a_different_domain.md +++ b/Running-Mastodon/Serving_a_different_domain.md @@ -83,3 +83,4 @@ There are a few known issues with Mastodon: Fortunately, since v1.3.0, Mastodon will reply to `acct:user@WEB_DOMAIN` queries with the account informations for `acct:user@LOCAL_DOMAIN`, effectively working around this issue at the cost of an extra webfinger discovery per interaction. - Mastodon does not actually use `WEB_DOMAIN` everywhere it should and will instead use whatever host it was accessed with. For this reason, your Mastodon instance should only be reachable on `WEB_DOMAIN` and not `LOCAL_DOMAIN` (HTTP redirects are fine, but avoid proxying from `LOCAL_DOMAIN` to `WEB_DOMAIN`) +- Remote Mastodon instances on v1.3.0, v1.3.1 or v1.3.2 from which you are following people won't PuSH new messages to your instance. This is a known bug, see [#2672](https://github.com/tootsuite/mastodon/issues/2672)