host/domain webfinger cfg ignored; workaround
As mentioned in #2985 (closed) , the current stable version ignores the host/domain config that would let a server masquerade its users as belonging to a domain rather than being attached to a hostname (@user@domain instead of @user@server.domain). But that issue's closed and I don't know the social conventions around commenting on closed issues. :-)
I was told on !3361 (merged) that this is fixed for the upcoming 2.5 release, but that's not scheduled yet and my employer is ready to migrate and really wants this feature so I've come up with a workaround that fools remote Mastodon instances but for some reason not Pleroma instances.
i.e. if you look me up as "@robin@pch.net" Mastodon instances find me and refer to me as that, but Pleroma instances find me and refer to me as "@robin@pleroma.pch.net".
Pleroma must be constructing it's idea of what a remote user is called from something other than the acct: response?
Here's how I've implemented a workaround (beyond setting up the redirect on the web server as described in the docs)); can someone please tell me why it works on remote Mastodon instances but not Pleroma ones?
(This is running on our instance at pleroma.pch.net, if you want to see it live.)
see comments for updated workaround; it got more complicated :-)
(This is very much a stone tools and ignorance workaround, and it will absolutely not scale, but this will only ever be a small instance and I can drop the workaround when 2.5 releases.)