I can install and run pixelfed on a subdomain, for example, pixelfed.example.com
[http://pixelfed.example.com]. However, I also run mastodon.example.com
[http://mastodon.example.com]. My webfinger points at mastodon. How do I
configure a webfinger for both pixelfed and mastodon? How do you all have your
webfingers setup when you run multiple activitypub-based services? Edit: I
should also add that I’m trying to tie my mastodon account to
[email protected],
not specific to the mastodon subdomain, but specific to my user email identity.
My mastodon domain would be sometime like mastodon.domain.com
[http://mastodon.domain.com], which would normally make my user
[email protected] [
[email protected]]. I do see this as a
potential solution - I could route the specific service based on user agent to
the correct webfinger:
https://serverfault.com/questions/775463/nginx-redirect-based-on-user-agent#825725
[https://serverfault.com/questions/775463/nginx-redirect-based-on-user-agent#825725]
So here is the issue on github: https://github.com/pixelfed/pixelfed/issues/3563
[https://github.com/pixelfed/pixelfed/issues/3563] If folks have GitHub
accounts, could you please bump this/thumbs up?
How do you run two AP services on the same domain?
Exactly… But as I wrote it might be possible with some nginx multiplexing hack.
I’m not sure I understand why hacks are needed. In order to run two AP services you either need two different [sub]domains, or two different URLs on the same domain. In both cases the webfinger URL will be specific to the AP [sub]domain or URL. So the problem is already solved.
How would this “multiplexed” webfinger URL even look?
The webfinger would be the same, but once the server gets contacted it would need to multiplex requests on some sort of identifier.