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?

Simon
link
fedilink
English
51Y

The webfinger includes the subdomain. So the webfinger would be either @user@mastodon.domain.com or @user@pixelfed.domain.com, given your example.

@thisisawayoflife@lemmy.world
creator
link
fedilink
English
11Y

deleted by creator

@thisisawayoflife@lemmy.world
creator
link
fedilink
English
31Y

Does it still work that way when using the web_domain setting?

https://docs.joinmastodon.org/admin/config/#web_domain

stown
link
fedilink
English
21Y

I’ve thought that if some dev created a webfinger reverse proxy they would be the hero of the fediverse.

Can you eli5?

I don’t think I understand what you mean.

What would the reverse proxy do in this situation?

@thisisawayoflife@lemmy.world
creator
link
fedilink
English
11Y

I think what they mean is a service to provide the webfinger response in a customizable manner. I know for me right now, I’m just using wildcards in nginx to handle it for the ActivityPub path, but it’s not really ideal because it won’t work for other activitypub services as far as I can tell.

@thisisawayoflife@lemmy.world
creator
link
fedilink
English
21Y

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.

@festus@lemmy.ca
link
fedilink
English
31Y

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.

@thisisawayoflife@lemmy.world
creator
link
fedilink
English
11Y

Yes, they use a webfinger on the .well-known path.

Create a post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

  • 1 user online
  • 126 users / day
  • 421 users / week
  • 1.16K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.68K Posts
  • 74.2K Comments
  • Modlog