How does this work? How do you host pixelfed.domain.com and mastodon.domain.com together in the same domain, with queries for “@user@domain.com” to the webfinger host path?
I’m other words, how does the querying application know which resource it needs? How do you know that a pixelfed instance will get the pixelfed resource versus the mastodon resource?
The webfinger includes the subdomain. So the webfinger would be either @user@mastodon.domain.com or @user@pixelfed.domain.com, given your example.
Does it still work that way when using the web_domain setting?
deleted by creator
I’ve thought that if some dev created a webfinger reverse proxy they would be the hero of the fediverse.
I’ve thought about doing this. It seems simple enough, though it would need a front end to be user friendly. I could build the rest api pretty quickly.
I can’t speak for those two services in particular, but I know that Matrix will check https://domain.com/.well-known/matrix/server to see what (sub)domain is responsible for domain.com. I suspect other services also use .well-known too.
Yes, they use a webfinger on the .well-known path.
