I can install and run pixelfed on a subdomain, for example, pixelfed.example.com. However, I also run 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 user@domain.tld, not specific to the mastodon subdomain, but specific to my user email identity. My mastodon domain would be sometime like mastodon.domain.com, which would normally make my user user@mastodon.domain.com.
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
So here is the issue on github:
https://github.com/pixelfed/pixelfed/issues/3563
If folks have GitHub accounts, could you please bump this/thumbs up?
Here’s a link to a better description of what someone is trying to do with webfinger. It’s critical to federation, and services piggybacking on mastodons configuration sort of break that - eg a pixelfed instance querying for user@domain.tld (trying to follow the pixelfed user for that user) would end up returning the mastodon profile. And while that works, and the third party pixelfed instance will follow the mastodon user, the pixelfed user won’t get that follow. Federation will end up being broken on pixelfed, IIRC.
https://www.hanselman.com/blog/use-your-own-user-domain-for-mastodon-discoverability-with-the-webfinger-protocol-without-hosting-a-server